Increment and Definition of Done Explained in Scrum
The Increment is the usable result created during a Sprint. It represents a concrete step toward the Product Goal.
For work to become part of the Increment, it must meet the Scrum Team's Definition of Done.
What Is an Increment?
An Increment is a usable, valuable result created during the Sprint.
A Scrum Team can create multiple Increments during a single Sprint. Each Increment must meet the Definition of Done.
Increment = A usable piece of the product that meets the Definition of Done.
What Is the Definition of Done?
The Definition of Done is a formal description of the quality state required for an Increment to be considered complete.
It creates a shared understanding of what "Done" means for the Scrum Team.
Example Definition of Done
For a software development team, the Definition of Done might include:
- Code completed
- Code reviewed
- Automated tests passed
- Required testing completed
- Security checks completed where applicable
- Documentation updated where required
- Product functionality meets the agreed quality criteria
The exact Definition of Done depends on the product, organization and Scrum Team.
Why Is Definition of Done Important?
Without a shared understanding of "Done", different people may have different views about whether work is actually complete.
The Definition of Done improves transparency and helps the team maintain a consistent quality standard.
When Is Work Considered Done?
A Product Backlog item is part of the Increment only when it meets the Definition of Done.
If an item does not meet the Definition of Done, it is not considered part of the Increment.
Increment vs Product Backlog Item
These terms are related but are not the same.
- Product Backlog Item represents work or value that may be needed.
- Increment represents the usable result after the applicable work meets the Definition of Done.
Simple Example
Imagine a team is developing a shopping application and works on a new payment feature.
The code has been written, but security testing is still incomplete.
If security testing is part of the team's Definition of Done, the feature is not Done yet.
"Code complete" does not automatically mean "Done". The work must satisfy the team's Definition of Done.
Who Is Responsible for the Definition of Done?
The Definition of Done is a commitment associated with the Increment and provides a shared quality standard for the Scrum Team.
If the organization has an established quality standard that applies to the product, it forms the minimum required standard. Otherwise, the Scrum Team establishes a Definition of Done appropriate for the product.
What Is the Scrum Master's Role?
The Scrum Master helps the Scrum Team understand the importance of transparency and quality.
The Scrum Master can also help the team identify gaps when work repeatedly fails to meet the Definition of Done.
Product Backlog → Work that may be needed
Sprint Backlog → Current Sprint plan
Increment → Usable product result
Definition of Done → Quality standard for "Done"
Key Takeaway
A Scrum Team should not treat unfinished work as completed. The Definition of Done creates transparency about whether the Increment actually meets the required quality standard.
Scrum Artifacts Section Complete
You have now covered all three Scrum artifacts and their commitments:
- Product Backlog → Product Goal
- Sprint Backlog → Sprint Goal
- Increment → Definition of Done