Agile project tracking - burn up charts

15,920 views

Published on

A gently introduction to tracking Agile projects with burn-down charts

Published in: Technology, Business
1 Comment
18 Likes
Statistics
Notes
No Downloads
Views
Total views
15,920
On SlideShare
0
From Embeds
0
Number of Embeds
4,545
Actions
Shares
0
Downloads
0
Comments
1
Likes
18
Embeds 0
No embeds

No notes for slide

Agile project tracking - burn up charts

  1. 1. Agile project tracking<br />A gentle introduction to using burn-up charts to manage Agile projects<br />
  2. 2. One question …<br />
  3. 3. “Is my project on track?”<br />
  4. 4. Yes<br />Target<br />date<br />Scope<br />Time<br />
  5. 5. No<br />Target<br />date<br />Scope<br />Time<br />
  6. 6. Yes<br />Today<br />Target<br />date<br />Predicted finish<br />Scope<br />Time<br />
  7. 7. No<br />Today<br />Predicted finish<br />Target<br />date<br />Scope<br />Time<br />
  8. 8. Easy …<br />
  9. 9. … how do I make one of those?<br />
  10. 10. completion of scope<br />plotted over time<br />
  11. 11. Scope<br />Time<br />completion of scope<br />plotted over time<br />
  12. 12. scope = story points*<br />
  13. 13. scope = story points*<br />*story point = estimation unit<br />
  14. 14. scope = story points*<br />time = iterations<br />*story point = estimation unit<br />
  15. 15. iteration scope added<br />
  16. 16. Scope<br />Time<br />iteration scope added<br />
  17. 17. iteration scope completed<br />
  18. 18. Scope<br />Time<br />iteration scope completed<br />
  19. 19. Scope<br />Time<br />Iteration 1<br />
  20. 20. Scope<br />Time<br />Iteration 1<br />Iteration 2<br />
  21. 21. Scope<br />Time<br />Predicted trend<br />Iteration 1<br />Iteration 2<br />Iteration 3<br />Iteration 4<br />
  22. 22. do cross the beams!<br />
  23. 23. Scope<br />Time<br />
  24. 24. Scope<br />Time<br />Iteration 1<br />Iteration 2<br />Iteration 3<br />Iteration 4<br />
  25. 25. hurrah!<br />
  26. 26. when lines go bad<br />
  27. 27. Scope<br />Time<br />Target<br />date<br />Ahead of target<br />
  28. 28. Scope<br />Time<br />Target<br />date<br />On target<br />
  29. 29. Scope<br />Time<br />Target<br />date<br />Behind target<br />
  30. 30. Scope<br />Time<br />Target<br />date<br />On target<br />
  31. 31. Scope<br />Time<br />Off target<br />Target<br />date<br />
  32. 32. Scope<br />Time<br />Scope trends too!<br />Target<br />date<br />
  33. 33. Scope<br />Time<br />This project may never end!<br />
  34. 34. What to do if the lines don’t meet?<br />
  35. 35. have a conversation<br />
  36. 36. of course …<br />
  37. 37. … how do I get one again?<br />
  38. 38. Scope your work in stories<br />Story: Add a big red button to the homepage<br />
  39. 39. Estimate those stories<br />Story: Add a big red button to the homepage<br />Estimate: 2 points<br />
  40. 40. Track when a story is added<br />Story: Add a big red button to the homepage<br />Estimate: 2 points<br />Iteration added: 1<br />
  41. 41. Track when a story is done<br />Story: Add a big red button to the homepage<br />Estimate: 2 points<br />Iteration added: 1<br />Iteration signed off: 3<br />
  42. 42. Plot them on a chart<br />Story: Add a big red button to the homepage<br />Estimate: 2 points<br />Iteration added: 1<br />Iteration signed off: 3<br />
  43. 43. Scope<br />Iteration 1<br />Iteration 2<br />Iteration 3<br />Iteration 4<br />Time<br />
  44. 44. Mingle can do this too!<br />
  45. 45. Don’t forget …<br />
  46. 46. Scope<br />Time<br />Expect scope to grow …<br />So factor in a schedule buffer in your release plans<br />
  47. 47. Agile teams test as they go …<br />If you’re not continuously testing in a production-like environment, expect to spend time testing and stabilizing at the end of the project<br />
  48. 48. Capture all requirements as stories<br />Otherwise your chart won’t be showing you the whole picture<br />
  49. 49. Development complete ≠ complete<br />A story doesn’t count as finished until it’s verified to be working in a production-like environment<br />
  50. 50. There are still risks<br />Continue to track risks, issues and external dependencies(they’re not going away)<br />
  51. 51. Mythical man-month<br />Predicting the impact on velocity of changes in team size is hard<br />
  52. 52. Remember a team has velocity, not an individual<br />
  53. 53. Further reading<br />http://www.xprogramming.com/xpmag/BigVisibleCharts.htm<br />http://alistair.cockburn.us/Earned-value+and+burn+charts<br />http://www.agilekiwi.com/agile_charts.htm<br />http://studios.thoughtworks.com/mingle-agile-project-management/2.2/help/creating_charts_and_tables_in_wiki_pages.html<br />

×