Untitled Document
Agile methods need only the most important metrics: the ones that tell the
whole story about the project. Metrics measure the health of a project and are
by far the most objective ways by which a project manager enables all project
sponsors and delivery teams to see where resources are needed or spent, or which
areas of a project need more focus.
Among agile project teams, consolidation of metrics differs significantly,
in a way that only the most meaningful metrics should be maintained. In other
words, there are certain metrics that agile project teams keep to summarize
their progress most effectively, supported by prose-style summaries from managers
about the impact of iteration to the overall project health.
Wondering how BPM, BAM, and B2B capabilities can be "plugged into" the bus? Find out here.
But how do agile teams determine the most important metrics? What makes the
most sense to project sponsors, clients, and management? According to Jochen
Krebs, author of Agile Portfolio Management, there are primarily three
metrics that provide the best measure of the state of an agile project: progress,
quality, and team morale.
Progress is a function of converting requirements into a working version of
software. It starts with a plan, which is the estimated effort for working on
a requirement and the actual value, which is the actual development work. Comparing
plans and efforts allow project teams to adjust their metrics for the next round
of requirements and iterations.
Tracking the progress of a project is especially useful when the estimation
method used is based on story points, which are assigned values to all documented
requirements. These points do not come from estimated working hours and assigned
dollar values which do not reflect real-world productivity scenarios. Instead,
these are all estimates done by delivery teams according to the level difficulty
of the work involved, as well as their own measure of personal productivity
or expertise. After each iteration, project teams can go over their story points
and make necessary adjustments as they work towards the next iteration of the
software.
-1-