Metrics for Agile projets
Agile I deas /  Concepts + Product Mgr Release Mgt Team Product Backlog Release Backlog Iteration – Story Backlog Release ...
The Agile Package <ul><li>Iterative development </li></ul><ul><li>Common coding standards </li></ul><ul><li>Continuous int...
Feature v/s Story Feature Feature is something about the product which may be sold to the end user; it may have a license ...
<ul><li>A   metric   is a standard for measuring or evaluating something. </li></ul><ul><li>A  measure  is a quantity, a p...
Selecting Metrics Future orientation  How will changes to development processes affect the organization’s ability to deliv...
Completed Features Objective : Goal of the project is to deliver a working software Measure : Easily measurable from the p...
Financial Value <ul><li>Objective : </li></ul><ul><li>Attach a profitability value in monetary terms to every release/ ite...
Earned Business Value
Earned Business Value <ul><li>Objective : </li></ul><ul><li>To measure the earned value to business with each delivery </l...
Velocity <ul><li>Velocity is </li></ul><ul><li>The sum of the estimates of the stories that were completed in an iteration...
Velocity Objective : Customer satisfaction Measure : Stories delivered/ Story points delivered or even ideal hours deliver...
Burn Charts <ul><li>Burn Up chart </li></ul><ul><li>How much work has been completed </li></ul><ul><li>Burn Up chart </li>...
Other Metrics <ul><li>Code Analysis : </li></ul><ul><ul><li>The use of tools to perform static code analysis can uncover m...
Earned Value Management <ul><li>Measuring actual value of integrated cost, schedule and scope against a baseline plan usin...
EVM - Metrics
EVM - Agile <ul><li>Story points are seen as a measure of work planned v/s completed </li></ul>
Velocity Report Card
Thank You A lot of material is available over the Internet this presentation is a summarized view and probably presents a ...
Upcoming SlideShare
Loading in …5
×

Agile Metrics

2,375 views
2,314 views

Published on

A short presentation on numbers that can be measured for an Agile project

Published in: Technology, Business
1 Comment
3 Likes
Statistics
Notes
  • On the slide #16, SPI should be EV/PV. Correct it and re-upload the slide otherwise it will mislead people. Thank you for valuable information.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
2,375
On SlideShare
0
From Embeds
0
Number of Embeds
32
Actions
Shares
0
Downloads
166
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

Agile Metrics

  1. 1. Metrics for Agile projets
  2. 2. Agile I deas / Concepts + Product Mgr Release Mgt Team Product Backlog Release Backlog Iteration – Story Backlog Release Release Iteration – Story Backlog Agile Team Product Owner Agile Coach Product Features Stories Iterations Portfolio Program Project Feature 1 Arch 1 Feature 2 Arch 2 Feature 3 Arch 3
  3. 3. The Agile Package <ul><li>Iterative development </li></ul><ul><li>Common coding standards </li></ul><ul><li>Continuous integration </li></ul><ul><li>Test driven development </li></ul><ul><li>Team ownership </li></ul><ul><li>Collaborative modeling </li></ul><ul><li>Co-located teams </li></ul><ul><li>Retrospectives </li></ul><ul><li>Sustainable pace of development </li></ul><ul><li>Daily stand-ups </li></ul>
  4. 4. Feature v/s Story Feature Feature is something about the product which may be sold to the end user; it may have a license attached or sold as bundle with the entire product. Example: PDF generation in MS word Story Story is the smallest unit of value/ requirement/ work which is visible to both project team and product owner. A story may have a description, validation criteria, complexity and business value.
  5. 5. <ul><li>A metric is a standard for measuring or evaluating something. </li></ul><ul><li>A measure is a quantity, a proportion, or a qualitative comparison of some kind. </li></ul><ul><li>Quantity : </li></ul><ul><li>There are five items remaining out of ten in this iteration </li></ul><ul><li>Proportion : </li></ul><ul><li>This release required 20% less effort than last one </li></ul><ul><li>Qualitative comparison : </li></ul><ul><li>The new version of the software is easier to use than the old version. </li></ul><ul><li>A metric can: </li></ul><ul><ul><li>Provide information on trends (Leads) </li></ul></ul><ul><ul><li>Provides information on outcomes (Lags) </li></ul></ul>Metrics Copyright © 2007-2009 Dave Nicolette
  6. 6. Selecting Metrics Future orientation How will changes to development processes affect the organization’s ability to deliver value and quality in the future? Business value How do application development projects contribute (directly or indirectly) to quantitative business benefits? User orientation How effective is the team in meeting the users’ needs? Operational excellence How does management measure development teams’ effectiveness? Velocity Features delivered vs. planned Post-iteration feedback/working demo Surveys, Customer-filed defects Earned business value Agile scorecard
  7. 7. Completed Features Objective : Goal of the project is to deliver a working software Measure : Easily measurable from the product backlog. Team can measure the running & tested features Trend: The number of features should increase with time When to measure: This is a continuous measure
  8. 8. Financial Value <ul><li>Objective : </li></ul><ul><li>Attach a profitability value in monetary terms to every release/ iteration </li></ul><ul><li>Measure : </li></ul><ul><ul><li>Profit = Income – Costs </li></ul></ul><ul><li>Trend: </li></ul><ul><li>A steady or upward trend is desirable </li></ul><ul><li>When to measure: </li></ul><ul><li>Post release </li></ul>
  9. 9. Earned Business Value
  10. 10. Earned Business Value <ul><li>Objective : </li></ul><ul><li>To measure the earned value to business with each delivery </li></ul><ul><li>Measure : </li></ul><ul><ul><li>BV of Services  Issue  Book  Issue Book is calculated as: </li></ul></ul><ul><ul><ul><li>(1/1) * (4/10) * (8/13) * (5/5) * (2/10) ~= 5% </li></ul></ul></ul><ul><ul><li>BV (bucket) = BV (parent) * [Wt (bucket) / Wt (bucket) + ∑Wt (sibling) ] </li></ul></ul><ul><ul><li>EBV is the summation of BV of all stories that have been coded and are up and running </li></ul></ul><ul><li>Trend: </li></ul><ul><li>A steady or upward trend is desirable </li></ul><ul><li>When to measure: </li></ul><ul><ul><li>Post release </li></ul></ul><ul><ul><li>When the list of stories and features is finalized else BV may change </li></ul></ul>
  11. 11. Velocity <ul><li>Velocity is </li></ul><ul><li>The sum of the estimates of the stories that were completed in an iteration. </li></ul><ul><li>It is an empirical observation of the team’s capacity to complete work per iteration. </li></ul><ul><li>It is based on the team’s own sizing of work items </li></ul><ul><li>It is comparable across different iterations for a given team on a given project </li></ul><ul><li>Not: </li></ul><ul><li>an estimate </li></ul><ul><li>a target to aim for </li></ul><ul><li>based on estimated or actual time </li></ul><ul><li>dictated or imposed by anyone other than team members </li></ul><ul><li>It is not comparable across teams & projects </li></ul>
  12. 12. Velocity Objective : Customer satisfaction Measure : Stories delivered/ Story points delivered or even ideal hours delivered; the key fact is that only completed items count Trend: Upward or stable trend is expected When to measure: This is a continuous measure
  13. 13. Burn Charts <ul><li>Burn Up chart </li></ul><ul><li>How much work has been completed </li></ul><ul><li>Burn Up chart </li></ul><ul><li>How much work is left or still remains </li></ul><ul><li>With each iteration remaining work should decrease and completed work should increase </li></ul><ul><li>Normally iterations are plotted on X axis and Stories/ story points on the Y axis </li></ul>
  14. 14. Other Metrics <ul><li>Code Analysis : </li></ul><ul><ul><li>The use of tools to perform static code analysis can uncover many details like: </li></ul></ul><ul><ul><ul><ul><li>Test coverage </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Primary areas of focus (eg JSPs or controllers) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Method complexity </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Lines of code </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Documentation v/s code </li></ul></ul></ul></ul><ul><li>TDD : </li></ul><ul><ul><li>TDD compilation or execution of tests at build time can provide an inference on the current state of development </li></ul></ul><ul><li>Story Cycle Time: </li></ul><ul><ul><li>Number of iterations it takes to complete a story </li></ul></ul><ul><li>Cycle Time: </li></ul><ul><ul><li>Average time between delivery of completed work items </li></ul></ul>
  15. 15. Earned Value Management <ul><li>Measuring actual value of integrated cost, schedule and scope against a baseline plan using Earned Value Management (EVM) metrics </li></ul><ul><li>It compares the earned value (EV) with the planned value (PV) </li></ul>
  16. 16. EVM - Metrics
  17. 17. EVM - Agile <ul><li>Story points are seen as a measure of work planned v/s completed </li></ul>
  18. 18. Velocity Report Card
  19. 19. Thank You A lot of material is available over the Internet this presentation is a summarized view and probably presents a set of metrics which can be used in a project following the Agile principles; many thanks to all the people who have shared similar content

×