Ken Schwaber and the rest of us advocate paying attention to what “done” means for a Product Backlog Item (PBIs, or “stories”). For a lot of programmers (like me), “done” often means “It works on my workstation!” The Scrum Master is charged with advocating a “done” that includes everything else needed to build a potentially-shippable product increment. So we need a cross-functional team.
To avoid nasty surprises at the Sprint Review Meeting, I’d suggest initially attaching a definition of done to each PBI during the estimation process. Don’t be surprised if the estimate more than doubles — better to find out now than have the illusion of progress and an unpredictable ship date.
If you’re using cards, write the definition of done on the cards. I prefer the larger index cards for teams just starting out. If you’re using ScrumWorks, write the definition of done in the “description” field — that’s what it’s for. Remember to check this during the Sprint Review Meeting. 98% done rounds to zero.
Scrum, a generalized framework rather than a defined process, doesn’t prescribe a particular definition of done. We expect you to use an inspect-and-adapt process to discover the appropriate definition for your unique circumstances.
However, reading this may save you a couple iterations because the same kinds of things come up a lot. I’ve listed some things I recommend talking about as you inspect and adapt your way toward your best definition of done. You may not need all the listed things in the beginning. I’ve discovered setting the bar too high initially can make the team feel it’s pedaling a bicycle uphill in the wrong gear. But talking about these things is better than unpleasant surprises at the end.
- Business Criteria often forgotten
- degree of feature richness
- interoperability (e.g. supported browsers)
- in production or not
- cross-cutting concerns
- compliance with corporate integration needs
- external regulations (i.e. legal)
- whether/when regression failures allowable
- Example engineering criteria to prevent Technical Debt
- pair programming, code/design review
- manual test
- automated test coverage
- unit tests
- system tests
- prefer same language (e.g. Java, if your production code is in Java, not brittle capture/playback or proprietary scripting languages)
- changing internals without changing behavior. Incrementally remove duplicate code, business logic in your presentation layer (JHTML, JSPs, etc.), complex conditional logic, poor naming, obsolete libraries….
Software Process Mentor
Danube Technologies, Inc.