Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Posted by Mark Levison on Jan 21, 2008
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.
Learning to be a Good Product Owner: Foundation Skills
Design in Agile, Software Craftsmanship, Product Development, Testing @ QCon London in March
Regaining control of the data centre
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.
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
Good to hear.
My comments were based on the the 2.5 press release so it might need updating.
Cheers
Mark
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
>>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.
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.
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
6 comments
Watch Thread Reply