InfoQ

News

Target Process 2.7: Agile Project Management tool for Distributed Teams

Posted by Mark Levison on Jan 21, 2008 09:00 AM

Community
Agile
Topics
Artifacts & Tools
Tags
Management,
Distributed Teams,
Planning,
Releases,
TargetProcess

Target Process 2.7 has been released, the tool has been mentioned here previously for its 2.0 and 2.3 releases. Target Process is an Agile Process Management tool that automates many of the tasks associated with an agile project. It helps simplify planning, tracking and QA. It provides real time reports, historical data and allows upper management to see the status of several projects at a glance. A number of new features have been added since we last wrote about it, including Visual Iteration Planning and Program Level Release Planning.

Visual Iteration Planning

This clever feature displays a large box that shows you much "room" is left in your iteration (based on your previous iterations velocity). Inside the box are the stories that the team has committed to for the iteration, each with its estimated size.

In addition, bugs are marked with a red bar and a small icon. This seems like a very elegant way of planning

Program Level Release Planning

Have a large product with several teams? This new feature makes it easier to track a number of projects within a single program. It makes it possible to see how releases will line up.

Their site includes a Quick Tour and an option to try for 30 days. Target Process is available as either an hosted service or an application installed in your webserver.

Many Agile coaches recommend that co-located teams start off using index cards and a task board because holding the daily scrum in front of the task board will help the team interact more. Electronic tools are normally recommended only when the team is distributed around a number of locations.

In release 2.5 an Individual Velocity Report was introduced. Some caution is required when using this feature. In the past some companies have used similar measures to track and reward individuals to the detriment of the team's performance. Agile methods are predicated on the belief that the value created by the team is greater than the sum of the individuals. A focus on the performance and reward of individuals can motivate team members to look out for themselves and not the team. This might manifest itself with some team members refusing to coach or avoiding parts of the project that might not make them look good.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

6 comments

Reply

We've removed Individual Velocity Report in fact :) by Michael Dubakov Posted Jan 21, 2008 9:15 AM
Re: We've removed Individual Velocity Report in fact :) by Deborah Hartmann Posted Jan 21, 2008 11:14 AM
Re: We've removed Individual Velocity Report in fact :) by Mark Levison Posted Jan 21, 2008 12:34 PM
Open Source Agile planning that is Open by Tim Ferguson Posted Jan 22, 2008 9:45 PM
Re: Open Source Agile planning that is Open by Michael Dubakov Posted Jan 23, 2008 6:57 AM
Re: Open Source Agile planning that is Open by Deborah Hartmann Posted Jan 23, 2008 11:23 PM
  1. Back to top

    We've removed Individual Velocity Report in fact :)

    Jan 21, 2008 9:15 AM by Michael Dubakov

    http://www.targetprocess.com/blog/2007/12/should-you-measure-individual-velocity.html

  2. Back to top

    Re: We've removed Individual Velocity Report in fact :)

    Jan 21, 2008 11:14 AM by Deborah Hartmann

    I'm happy to hear that, Michael :-) I created one once, too. But outside the context of a very trusting and trusted team, it's a bad idea. Now, I remove it before I share that spreadsheet with others. Keep up the good work! deb

  3. Good to hear. My comments were based on the the 2.5 press release so it might need updating. Cheers Mark

  4. Back to top

    Open Source Agile planning that is Open

    Jan 22, 2008 9:45 PM by Tim Ferguson

    This looks like a nice product with some well thought out features. One of the issues we have as an Open Source project is that we would like to be completely open with our Agile process as well. What we need is a web based product that allows anyone to see our information but not necessarily change it. We would only want the contributors in the iteration to change things. We also would have no idea how many people would want to just view our planning. Has anyone else come across these needs, does this product fulfill that need? -Tim Ferguson, xaware.org

  5. Back to top

    Re: Open Source Agile planning that is Open

    Jan 23, 2008 6:57 AM by Michael Dubakov

    >>We would only want the contributors in the iteration to change things. We also would have no idea how many people would want to just view our planning. Has anyone else come across these needs, does this product fulfill that need? That is possible at least as a workaround. You may create role named Observer for example and disable all Add/Edit/Delete permissions to this user role. Then you may create a user with login and password observer/observer and put this information somewhere in public place. Then all people will be able to login as observer and view all information, but will not be able to change it.

  6. Back to top

    Re: Open Source Agile planning that is Open

    Jan 23, 2008 11:23 PM by Deborah Hartmann

    Definitely, this is an important role to provide for. Tools that limit "view only" usersd (or charge for them) are missing a major point of Agile, imo.

Exclusive Content

Agile Project Management: Lessons Learned at Google

In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.

AtomServer – The Power of Publishing for Data Distribution

In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.

An Introduction to Virtualization

It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.

REST Anti-Patterns

In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.

Choosing between Routing and Orchestration in an ESB

In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.

Enterprise Batch Processing with Spring

Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.

User Story Estimation Techniques

Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.

Security (CAS and OpenID) with Ruby

In this talk from QCon SF 2007, Justin Gehtland explains two open solutions to distributed identity and their Rails integration components: OpenID (using ruby-openid) and CAS (using rubycas-client).