What is the definition of Done?

July 1, 2008 by mrdavidlaing
Filed under: Agile 

 Scott Hanselman has a pretty interesting discussion with Scrum co-creator Ken Schwaber around the concept of when is a story Done.

http://www.hanselman.com/blog/HanselminutesPodcast119WhatIsDoneWithScrumCoCreatorKenSchwaber.aspx

Ken raising some interesting points, most notable that a well defined concept of Done, understood by all members of the project is a cornerstone of a good scrum process.  Without it, you can guarentee that you are building up technical debt; and your software won’t be in a releasable state once you have “Done” all the features, which kind of defeats the point of release planning!

So, what is your definition of done?

  • All acceptance cases / test scenarios pass?
  • Unit tests pass?
  • Performance tests pass?
  • Customers have used and approved the feature?

Comments

Tell me what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!

You must be logged in to post a comment.

  • Tags

  • Recommended reads

    Applying Domain-Driven Design and Patterns: Using .Net
    Domain-driven Design: Tackling Complexity in the Heart of Software
    Clean Code: A Handbook of Agile Software Craftsmanship (Robert C. Martin)
    Agile Estimating and Planning (Robert C. Martin)
    Test Driven Development (The Addison-Wesley Signature Series)
  • Latest del.icio.us links