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…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Five Simple Questions To Determine If You Have the Agile Mindset

My company has started a top-down transition to Scrum and Kanban. Will that make us an Agile company? About 2 years ago, I attended a conference hosted by the Swiss Association for Quality on the topic of Agility. As a warm-up exercise, the participants were given the 4 values of the Agile Manifesto, then asked to arrange themselves in space. How Agile is your company? How Agile do you think it should be? Very Agile on left, very traditional on the right. There was a cluster of people standing well to the right of center. “Why are you standing on the right?” It turns out that they were all from the railway. “Our job is to run the trains on time.” They were uncertain whether this agility thing was really aligned with their purpose.
Is Agility limited to software? Steve Denning has collected the evidence and laid out the case that Agile is not limited to software, nor is it merely a process, nor is it something you can do with part of your time, nor is it something you can have your …