Skip to main content

New Course: Agile Project Management with Target Process

When I took over the WLC Project, we were using the Wiki and Excel to manage our many to do lists. Soon we reached the limits of Excel and needed a proper tool to effectively manage the many stories, make the information available at multiple locations, and keep track of our progress. After an evaluation, we chose Target Process, and have been happily using it ever since.

So now that I am independent, I checked out TP and discovered that they don't offer any courses yet, a need which I have set out to fill.
Agile Project Management with Target Process

How to plan, manage and control agile software development projects using Target Process. A hands on introduction to the concepts needed by and tasks performed by the agile Project Manager (Scrum Master), Customer or Program Manager (“Product Owner”).

Focused on the key performance indicators, Scope, Time, Quality and Price, the participant gets a step by step introduction to using Target Process to achieve the key goals of managing, controlling and successfully completing software development projects.

Objectives
After completing this course, the project or program manager will be able to successfully plan, manage and control software development projects using Target Process.

Audience
Program Managers, Project Managers, Scrum Masters, Product Owners and Developers

Location
Date: May 21 & 22, 2008
Time: 9.00 to 17.00
Location: namics ag, konradstrasse 12/14, 8005 Zürich Switzerland
Participants must bring their own laptop to access the practice environment.

Cost
Early Bird Registration (payment received by April 15) CHF 1'296.--
Regular Registration CHF 1'496.--
Prices include 7.6% VAT.
Full information about the course is available online. And of course you can register online.

BTW - TargetProcess is supporting this effort Marketing Director Andrey Mihailenko and CTO Michael Dubakov will be present. The number of participants to this first edition is limited to 12.

Comments

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…