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.

1. Learning from Burndown Charts

2. http://www.flickr.com/photos/therahim/5587920310

3. Think about your team

4. Think about your team

5. Continuous
Improvement

6. http://www.flickr.com/photos/andybeatty/2715799788

7. Iteration Burndown

8. Iteration Burndown

9. Iteration Burndown

10. Iteration Burndown

11. Iteration Burndown

12. Final Burndown

13. Typical Burndown

14. Iteration Waterfalls
All Stories
in Iteration
1
Iteration 1

15. Stop the Waterfalls
http://www.flickr.com/photos/macieksz/38747643

16. How?

17. Define Done

18. “The beginning of wisdom
is a definition of terms
Socrates

19. http://www.flickr.com/photos/fernandowagner/2607557

21. Continuous Improvement
Technical Debt & Waterfall Behavior

23. Focus on Story Done
Stor y Stor y Stor y
1 2 3
All Stories
in Iteration
All Stories
in Iteration
All Stories
in Iteration

24. Healthy Burndown

25. Fake Burndown

26. Applies at the
Release level too

27. Release with Hardening

28. No Hardening Release

29. http://www.flickr.com/photos/therahim/5587920310

30. Next Retrospective
What
S
What has What HYPOTHESE
HELPED HIND has could we
ERED
us?! us?! draw about
how we move
forward?!

31. Smooth Delivery
h"p://www.flickr.com/photos/computerhotline/4611181320