Agile Metrics

5,568 views

Published on

Published in: Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,568
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
214
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Agile Metrics

  1. 1. <ul><li>To Know More About Project Agile Metrics </li></ul>Agile Metrics May 16 th , 2009 Sam Tong
  2. 2. Agenda <ul><li>Traditional Metrics </li></ul><ul><li>Agile Metrics measuring the Schedule </li></ul><ul><li>Agile Metrics measuring the Productivity </li></ul><ul><li>Agile Metrics measuring the Quality </li></ul><ul><li>Q&A </li></ul>
  3. 3. Traditional Metrics <ul><li>Schedule </li></ul><ul><ul><li>Plan Variation based on Milestones </li></ul></ul><ul><li>Quality </li></ul><ul><ul><li>Defect Density based on Integration/System testing/UAT </li></ul></ul><ul><ul><li>Document Defect Density based on Reviews </li></ul></ul><ul><li>Productivity </li></ul><ul><ul><li>KLOC / staff-day </li></ul></ul>
  4. 4. Agile Metrics - Schedule <ul><li>Sprint Level Effort Burn Down </li></ul><ul><ul><li>Re-estimated Remaining effort based on the sprint backlog </li></ul></ul><ul><ul><li>Identify the “Effort” </li></ul></ul><ul><ul><ul><li>Effort could be estimated hours </li></ul></ul></ul><ul><ul><ul><ul><li>The whole team agreed estimates </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Planning Poker can be used for generating the estimates </li></ul></ul></ul></ul><ul><ul><ul><li>Effort could be “story point” </li></ul></ul></ul><ul><ul><ul><ul><li>Define a standard story as one story point </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Story points for stories should follow the Fibonacci Series </li></ul></ul></ul></ul>
  5. 5. Agile Metrics – Schedule - 1 <ul><li>Sprint Level Effort Burn Down </li></ul><ul><ul><li>Daily task tracking </li></ul></ul><ul><ul><ul><li>Previous Sprint experience - Expected curve </li></ul></ul></ul><ul><ul><ul><li>Daily Remaining Effort - Actual curve </li></ul></ul></ul>
  6. 6. Agile Metrics – Schedule - 2 <ul><li>Sprint Level Effort Burn Down </li></ul><ul><ul><li>How’s the data collected, analyzed, and used </li></ul></ul><ul><ul><ul><li>Collecting data: XPlanner, JIRA, RedMine, Green Hoper </li></ul></ul></ul><ul><ul><ul><ul><li>We had much experience using the XPlanner (Iteration, Story, Task Tracking, Burn Down Chart functionality provided) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>RedMine is still developing (Gantt View, Calendar View, Task tracking) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>JIRA (Issue tracking system, can also be used as Task Tracking system) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Green Hoper (JIRA plug-in - Online Task planning tool, Task tracking) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Use database (SQL) tool to extract data from the tracking system </li></ul></ul></ul></ul>
  7. 7. Agile Metrics – Schedule - 3 <ul><li>Sprint Level Effort Burn Down </li></ul><ul><ul><li>How’s the data collected, analyzed, and used </li></ul></ul><ul><ul><ul><li>Analyze the data: Burn Down Chart </li></ul></ul></ul><ul><ul><ul><li>Use the data </li></ul></ul></ul><ul><ul><ul><ul><li>Expected curve </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Are we on track? </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Know when to take actions (20% Variation is the trigger) </li></ul></ul></ul></ul>
  8. 8. Agile Metrics – Schedule - 4 Iteration N Burn Down – Story Point Iteration N Burn Down - Hours
  9. 9. Agile Metrics – Schedule - 4 Iteration N+1 with Expected Curve - Hours Iteration N+1 with Expected Curve – Story Point * This is the curve without any change on the scope during the iteration
  10. 10. Agile Metrics – Schedule - 4 Iteration N+1 with Expected Curve - Hours Iteration N+1 with Expected Curve – Story Point * This is the curve after changing the scope on 12/1
  11. 11. Agile Metrics – Project Schedule <ul><li>Project Burn Down </li></ul><ul><ul><li>Remaining effort based on the project backlog </li></ul></ul><ul><ul><li>Identify the “Effort” </li></ul></ul><ul><ul><ul><li>Effort could be estimated hours </li></ul></ul></ul><ul><ul><ul><li>Effort could be “story points” </li></ul></ul></ul><ul><ul><li>Sprint basis tracking </li></ul></ul><ul><ul><ul><li>Planned burn down </li></ul></ul></ul><ul><ul><ul><li>Actual burn down </li></ul></ul></ul><ul><ul><li>How’s the data collected, analyzed, and used </li></ul></ul><ul><ul><ul><li>Are we on track </li></ul></ul></ul><ul><ul><ul><li>Need to identify the indicator (20% Variation) </li></ul></ul></ul>
  12. 12. Agile Metrics – Project Schedule 2 Iteration Release Plan is the planned curve
  13. 13. Agile Metrics - Quality <ul><li>Our Understanding </li></ul><ul><ul><li>Client does not necessarily want to know the defect density, but the working product </li></ul></ul><ul><ul><li>Quality metric is not only the way to measure the delivery, but also it’s the way to find possible improvements during the project. - The topic that should be included in the retrospective meeting </li></ul></ul><ul><ul><li>Defect is only regarding the working product </li></ul></ul><ul><li>Metrics definition </li></ul><ul><ul><li># defects per sprint </li></ul></ul><ul><ul><li># defects per story point </li></ul></ul><ul><ul><li># defects per hour </li></ul></ul><ul><li>How’s the data collected, analyzed, and used </li></ul>
  14. 14. Sample data and analysis
  15. 15. Agile Metrics - Productivity <ul><li>Our Understanding: </li></ul><ul><ul><li>We do not focus on #KLOC that the team can produce </li></ul></ul><ul><ul><li>We want to know how many features/ user stories that the team can finish in a fixed time box </li></ul></ul><ul><li>Metrics Definition </li></ul><ul><ul><li># story points per sprint </li></ul></ul><ul><ul><li># story points per staff-sprint </li></ul></ul><ul><ul><li># estimated hours per sprint </li></ul></ul><ul><ul><li># estimated hours per staff-sprint </li></ul></ul><ul><li>How’s the data collected, analyzed, and used </li></ul>
  16. 16. Sample data & Analysis 5% Variation is the trigger for detail analysis for the dropping or improvement of the productivity in retrospective meeting
  17. 17. Q&A

×