What's the best way to define and update 'done' for Scrum artifacts and deliverables?

1 What is 'done' in Scrum?

In Scrum, 'done' is a shared understanding among the Scrum team and the product owner of the quality and completeness of the work that is delivered at the end of each sprint. It is not a subjective opinion, but a set of objective and measurable standards that are agreed upon and communicated before the work begins. The definition of 'done' applies to all Scrum artifacts, such as the product backlog, the sprint backlog, the product increment, and the sprint review.

2 Why is 'done' important in Scrum?

Having a clear and consistent definition of 'done' in Scrum is important for several reasons. First, it helps the Scrum team to focus on the most valuable and feasible work that can be delivered within a sprint, and to avoid scope creep and technical debt. Second, it helps the product owner to verify that the product increment meets the acceptance criteria and the business goals, and to provide feedback and guidance to the Scrum team. Third, it helps the stakeholders to trust and support the Scrum team, as they can see the tangible and quality results of each sprint.

3 How to create a definition of 'done' in Scrum?

Creating a definition of 'done' in Scrum is a collaborative process that involves the Scrum team, the product owner, and the stakeholders. It should be based on the product's vision and goals, user and customer expectations, technical and functional requirements, quality standards and best practices of the organization, as well as any constraints and risks of the project. The definition of 'done' should be documented and visible to everyone involved in the project, and it should be regularly reviewed and refined to ensure its relevance and alignment with changing conditions and feedback.

4 How to update a definition of 'done' in Scrum?

Updating a definition of 'done' in Scrum is an ongoing activity that should be done whenever there is a change in the product vision, goals, requirements, standards, or feedback. The Scrum team, the product owner, and the stakeholders should review the current definition of 'done' and identify any gaps, inconsistencies, or improvements that are needed. The update should be communicated and agreed upon by all parties, and reflected in the Scrum artifacts and deliverables.

5 How to use a definition of 'done' in Scrum?

Using a definition of 'done' in Scrum is a way of ensuring quality and value in every sprint. The Scrum team should use the definition of 'done' as a checklist and a guideline for their work, and as a way of validating and demonstrating their progress and achievements. The product owner should use the definition of 'done' as a way of evaluating and accepting the product increment, and as a way of providing feedback and direction to the Scrum team. The stakeholders should use the definition of 'done' as a way of verifying and supporting the product delivery, and as a way of expressing their satisfaction and expectations.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?