Re: Definitions of "Done"
- --- In email@example.com, "bmstallings"
>Perhaps I missed the point of your question, but how about something
> In preparing some training / coaching materials for the Scrum teams
> I am involved with, I would like to collect your favorite
> definitions. Please send them along.
> Bryan Stallings
as simple as, "Everything we said we would do is as done as we said
it would be."
What you might be looking for are the things that should be included
in the list of "we said we would do ___", but I think it is risky to
get caught up in the details of a "done-list" if it means losing
sight of the basic principle, "As done as we said it would be."
One of the things I like about the attitude of Scrum is making
decisions of done-ness visible. The specific content of a done-list
is not as important as having a visible and understood list. For
example, it might be simple to have a rule like, "All unit-level test
cases written and passing", but it might be more practical to
say, "All the normal cases written and passing, but the error cases
are deferred to a later Sprint." As long as the team, including the
customer, understands what "Done" means with respect to unit-level
testing, either scenario is acceptable. I can't imagine finding
agreement for the contents of a done-list, since the list is unique
to the needs of a project. I hope we would all agree with the need
for a project to have such a list.
The point of the definition "As done as we said it would be" is to be
sure all work, functionality, and deliverables are accounted for
somewhere, and we can unambiguously assess whether we made it at the
end of the sprint.