Project Management

Please login or join to subscribe to this thread

Agile Metrics

linkedin twitter facebook  
avatar
Khushboo Singh Project Manager| Envestnet|Yodlee Bangalore, Karnataka, India
Which metrics should be considered for Agile projects?
I have read in few blogs that Productivity should not be considered for Agile projects; instead we should measure quality and team productivity.
What metrics should I consider and what methodologies should be used to measure those?
What should be the frequency?
Does metrics vary depending on the size and complexity of the project?
Should the same metrics be applicable to all the projects?
Sort By:
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
This is a tough question. An agile purist might tell you the only metrics are velocity and the burndown chart, and the frequency is at the end of every sprint. Others have tried to impose traditional metrics on agile. Here is one example:

https://www.scrumalliance.org/community/ar...ing-and-metrics

It doesn't always work.

In my opinion, the question to ask is what information do you need? Do you need to make decisions about budget or product launches? Avoid becoming so obsessed with data that you are collecting data that will never be used.
avatar
Heidi chan Sydney, Nsw, Australia
I provide sprint burn down and release burn down. Ultimately PO and stakeholders want to know what you've completed and whether your tracking to a release. I (should) do this after every sprint. I do apply to every project - however I don't necessarily provide every sprint eg. Might not provide release burndown during production readiness sprints.
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
Given that the whole philosophy of agile is to deliver value sooner and cheaper, should that not be what we measure?

Of course, it begs the question: how do you measure value? You probably have to go back to your features delivered. You would then measure how many features you deliver per units of money or units of time.
avatar
Faisal Patel SVP; Strategy/Solution Manager; Accessibility Champion| Bank of America West Hills, Ca, United States
There are a few ways to get the message out -

1. Burndown Chart - shows team progress on deliverying the scope for the sprint. Important for stakeholders to stay on top

2. Team velocity - the trend should be a gradual uptick which marks the team's ability to perform more and better within the set 2 weeks window

3. Release Burnup - work delivered in the release and readiness for timely delivery

These can be rolled up from component teams all the way up to the Train level.
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
Just watched Scaling Agile Metrics - Tracking Metrics that Matter! from the IIL's IPM Day 2016 conference.

Some of the highlights from the video:

  • Three organizational layers: team, program and portfolio. (Notice there is no project layer.)

  • Team Health qualitative metrics: for each team and rolled-up (clarity, performance, leadership, cuture, foundation) - check AgilityHealthRadar.com

  • Velocity Predictability quantitative metrics:for each team and program roll-up (variance from target to actual)

  • Escaped Defects: by team and program roll-up

  • Impediments: count and lead time

  • Release Health metrics: number of releases, points per release, defects, timelinesss, cost, value delivered

  • Cost: per team and cost per release train

Please login or join to reply

Content ID:
ADVERTISEMENTS

"If I were two-faced, would I be wearing this one?"

- Abraham Lincoln

ADVERTISEMENT

Sponsors