Learning from Burndown Charts

3,251
-1

Published on

Too often we label software "done" when it’s not tested, only partially documented and only half ready for release. We produce no business value, we pile on technical debt, and stakeholders have no confidence in our status reports. This presentation explores how you can use Burndown charts to improve your process.

Published in: Education, Sports

Learning from Burndown Charts

  1. 1. Learning from Burndown Charts
  2. 2. http://www.flickr.com/photos/therahim/5587920310
  3. 3. Think about your team
  4. 4. Think about your team
  5. 5. ContinuousImprovement
  6. 6. http://www.flickr.com/photos/andybeatty/2715799788
  7. 7. Iteration Burndown
  8. 8. Iteration Burndown
  9. 9. Iteration Burndown
  10. 10. Iteration Burndown
  11. 11. Iteration Burndown
  12. 12. Final Burndown
  13. 13. Typical Burndown
  14. 14. Iteration Waterfalls All Storiesin Iteration 1 Iteration 1
  15. 15. Stop the Waterfallshttp://www.flickr.com/photos/macieksz/38747643
  16. 16. How?
  17. 17. Define Done
  18. 18. “The beginning of wisdom is a definition of terms Socrates
  19. 19. http://www.flickr.com/photos/fernandowagner/2607557
  20. 20. Continuous ImprovementTechnical Debt & Waterfall Behavior
  21. 21. Focus on Story Done Stor y Stor y Stor y 1 2 3 All Storiesin Iteration All Stories in Iteration All Stories in Iteration
  22. 22. Healthy Burndown
  23. 23. Fake Burndown
  24. 24. Applies at theRelease level too
  25. 25. Release with Hardening
  26. 26. No Hardening Release
  27. 27. http://www.flickr.com/photos/therahim/5587920310
  28. 28. Next Retrospective What S What has What HYPOTHESE HELPED HIND has could we ERED us?! us?! draw about how we move forward?!
  29. 29. Smooth Delivery h"p://www.flickr.com/photos/computerhotline/4611181320  

×