Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
J R
2,037 PointsWhen the Definition of "Done" is done and at what event can be reviewed it?
When is the Definition of "Done" done and at what event can be reviewed it?
2 Answers
Matt Anthes-Washburn
Treehouse Guest TeacherHi J R,
The Definition of "Done" is part of the team's expectations or norms. Ideally, the team discusses these when the team forms or launches. Periodically, the team will revisit their Definition of "Done," especially if they feel like things are getting sloppy. For example, if the retrospective reveals that the team is finding more and more bugs in stories that were supposedly completed, they might look at the Definition of "Done" again and add something to the definition that is likely to catch more issues before the team moves on from a story.
Above is one example of an actionable item that can come up in retrospective and be brought into the next sprint. Generally, it's a good idea to stick to just one thing everyone agrees they can change in the next sprint. This keeps the team's attention focused on one aspect of their practice and makes it easier to see if the change had a positive effect on the team's work.
So yes, a team will usually stick to one retrospective item for the new backlog. That item might be about the Definition of Done, but it might be about something completely different, like more snacks at meetings. That's one of my favorites. :)
Does that make sense?
Craig Dennis
Treehouse TeacherIn my experience there is a time when the team starts doing Scrum practices, and it is defined then.
It can be reviewed during each retrospective at the end of each Sprint. It should not change during the Sprint, as it would mean that some stories are "done" differently.
That make sense?
J R
2,037 PointsIt makes sense but the question came because there is a quiz question where the product of a Sprint Retrospective is defined as: "one item that can be taken into the next sprint that the team agrees to try to do better". If there is a list of actionable commitments from a Scrum Retrospective and also a review or increase to the definition of "Done" then why is the product of a scrum retrospective defined as "one item" ?