Maximise the Scope of Product Increment: Difference between revisions
Jump to navigation
Jump to search
(Created page with "__NOTOC__ For each team, the scope of the Product Increment should be as close as is practicable to releasable end-to-end value. == Description == The Scrum Guide describes the Increment as a concrete stepping stone toward the Product Goal, i.e. to realisable value to customers and stakeholders. The Definition of Done provides the guardrails to ensure that the incremental work of the team(s) will be of sufficient quality to release. Where a product is a composite of the...") |
No edit summary |
||
| Line 18: | Line 18: | ||
*[[Organise around value streams]] | *[[Organise around value streams]] | ||
*[[Shared context improves decisions]] | *[[Shared context improves decisions]] | ||
*[[Favour Teams with broader Business Domain | *[[Favour Teams with broader Business Domain Competence]] | ||
*[[Favour Teams with broader Solution Accountability]] | *[[Favour Teams with broader Solution Accountability]] | ||
*[[Maximise Team autonomy]] - ''Contending'' | *[[Maximise Team autonomy]] - ''Contending'' | ||
*[[Limit Team Mental Workload]] - ''Contending'' | *[[Limit Team Mental Workload]] - ''Contending'' | ||
Latest revision as of 22:13, 21 May 2024
For each team, the scope of the Product Increment should be as close as is practicable to releasable end-to-end value.
Description
The Scrum Guide describes the Increment as a concrete stepping stone toward the Product Goal, i.e. to realisable value to customers and stakeholders. The Definition of Done provides the guardrails to ensure that the incremental work of the team(s) will be of sufficient quality to release. Where a product is a composite of the output of multiple teams, then they should be working to a collective broadly scoped Increment with a common set of Definition of Done elements. A combined Sprint Review provides a further enabling constraint, encouraging the team to regularly collaborate and integrate their work.
Rationale
- Widen the perspective of all involved teams to the broader mission and remind them that they win or lose as a collective.
- Increase transparency and quality of their planning to incorporate concerns relevant to the integrated whole Product Increment.
- Reduce the risks and problems caused by poor assumptions.
- Provides faster feedback on changes that may impact other teams' work.
- Reduces the technical debt and waste caused by unintegrated work.