Scott Hanselman has a pretty interesting discussion with Scrum co-creator Ken Schwaber around the concept of when is a story Done.
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?