Going Agile? Process First, Then Tool...
From the Project Management 2.0 Blog
by Dave Garrett
New technologies, concepts, and Web 2.0 tools are popping up everywhere. How can you use them to help your project team collaborate, communicate - or just give your project an extra boost? [Contact Dave]
Recent Posts
Are You Prepping For The PMP 24/7?
Are You Just Too Darn Busy?
Eliciting Requirements... Creatively!
What To Expect When Your Stakeholders Are Expecting
8 More Templates to Save You Time
Categories
Advice,
Certification,
Collaboration Tools,
Decision Making,
Estimating,
Interviews,
Learning,
Management Approaches,
New Templates,
Personal Productivity,
PM Software,
PPM Software,
Presentation Tools,
Reporting Tools,
Requirements Management,
Research,
Risk Management,
Scheduling Software,
Security,
shameless self promotion,
Techie Tools,
Time Killers,
Time Tracking Software,
Training,
Virtual Team Tools,
Web-based Tools,
workshops
Date
Situation: You're Shopping for Agile PM Tools...
TargetProcess offers an Agile Project Management software package called TP v.2 . Version 1.7 won the 16th annual Jolt Productivity Award. Software to manage Agile projects tends to focus more on results and less on time and tasks. We recently spoke with Michael Dubakov, the Founder of TargetProcess, who gave us a little more insight into what makes TP v.2 special. Here are his responses to our questions.
Q. Do your naming conventions and tool functions align with any particular flavor of Agile? How important is the concept of "stories" within the tool?
TargetProcess terminology is primarily Extreme Programming based, however in the upcoming release (early May) we will add custom terms. It will be possible to create your own terminology in TargetProcess to support any in-house agile process. Moreover, it will be possible to create unique terminology for each department inside the company if required. TargetProcess is agile-focused for sure. It may be used with almost any agile process, but will not work perfectly with waterfall. It is designed to solve exact problems in agile environment and not follow a one-process-fits-all approach.
A User Story translates to “Requirement” in traditional PM language. There are two types of requirements in TP: Feature and User Story. A feature is conceptually larger and it may consist of several user stories. A User story is a key thing in TargetProcess as well as in real life. In fact user stories are an attempt to describe “people needs”, and those needs are why software is created. They are the most important thing in any project regardless project type, size or methodology.
Q. Can you describe the process of scope management using TP v.2?
We manage scope using the Release Planning / Iteration Planning areas. The release planning area allows you to create a product roadmap and balance effort for all releases, while the iteration planning area powers the creation and balancing of iterations. The Release Burn Down chart show how is the release going. It provides insight into whether it is possible to add more stories/features in the release or if there is a need to reduce release scope and drop some stories to meet the deadline.
Q. Is TP v.2 particularly good for projects of any particular size, industry, or type? What makes it unique among Agile PM software packages?
In general TP works best for very experienced agile teams. We feel it works perfectly for distributed teams as well. "We do not recommend using ANY agile PM tool when changing your overall development approach from waterfall to agile, since it may shift focus from people and process to tool itself. The process change should be made first. Then the a tool can be introduced to make that process work more effectively." If team feels the need for a replacement for manual tools (whiteboards/excel/cards/etc.), then TargetProcess may be a perfect choice.
TargetProcess is used in small companies with several developers and in quite large departments with up to 300 people. Project fit is a matter of agile process, not a tool. Any agile focused team may use TargetProcess. Teams using waterfall approaches likely will not benefit from TP usage.
Simplicity, integrity and productivity are what make Target Process unique. TP is simple in comparison with other APM tools. The user interface is AJAX based and very responsive. It provides many productivity tools like screenshot capture, a bug submission utility or integration with Subversion that saves a lot of time from the developer’s perspective. (TP automatically changes the state of user stories or bugs, add comments and spent time from a single commit message). Our customers love the interface. Most are happy with the tool and that is the best indicator that we’re headed in the right direction.
Posted on: April 09, 2007 04:21 PM |
Permalink
Comments (1)
Please login or join to subscribe to this item
Thanks Dave, great article!
Please Login/Register to leave a comment.
|
"In the fight between you and the world, back the world."
- Kafka
|