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