• Next: No Bugs
• Previous: Chapter 7: Releasing
• Up: Chapter 7: Releasing

in 99 words

A story is only complete when on-site customers can use it as they intended. In addition to coding and testing, completed stories are designed, refactored, and integrated. The build script builds, installs, and migrates data for the story. Bugs have been identified and fixed (or formally accepted), and customers have reviewed the story and agree it's complete.

To achieve this result, make progress on everything each day. Use test-driven development to combine testing, coding, and design. Keep the build up to date and integrate continuously. Demonstrate progress to your customers and incorporate their feedback as you go.

Commentary

The Cornerstone of Agile Planning

Section Outline

• "Done Done"
• Production-Ready Software
• How to Be "Done Done"
• Making Time
• Questions
  • How does testers' work fit into "done done"?
  • What if we release a story we think is "done done," but then we find a bug or stakeholders tell us they want changes?
• Results
• Contraindications
• Alternatives

Full Text

This section will go online later this year. In the meantime, why not buy the book?

• Next: No Bugs
• Previous: Chapter 7: Releasing
• Up: Chapter 7: Releasing