Managing Stakeholder Expectations with an Incomplete Increment
In Scrum, it’s essential that each Increment is complete and meets the Definition of Done before it is released to customers. This ensures that the product is of high quality and is ready for use. However, there can be situations where stakeholders push for the release of an Increment that is not fully complete, which can lead to potential risks.
Exam Question
At a Sprint Review the Scrum Team and stakeholders inspect an Increment and discuss a Product Backlog item that is not done, because the required documentation needed for the Product Backlog item is not complete. The stakeholders are happy with the outcome and push the Scrum Team to put the product in the hands of the customer immediately.
You are the Scrum Master, what do you do with respect to the Increment and the push by the stakeholders to put the product in the hands of the customer immediately?
Explanation
Handling Incomplete Increments
- Upholding the Definition of Done:
Scrum’s Role: As a Scrum Master, it is crucial to ensure that the Definition of Done is upheld. The Definition of Done is a shared understanding within the Scrum Team that an Increment must meet certain quality standards and be fully complete, including all necessary documentation, before it can be considered ready for release.
Example: In this scenario, the documentation for a Product Backlog item is incomplete. This means the Increment does not meet the Definition of Done. Despite stakeholder pressure, it is the Scrum Master’s responsibility to ensure that the Increment is not released until it fully complies with the Definition of Done. - Educating Stakeholders:
Scrum’s Role: The Scrum Master should educate stakeholders on the importance of releasing only complete and fully tested Increments. Releasing an incomplete Increment could lead to potential risks, such as defects, customer dissatisfaction, and technical debt.
Example: The Scrum Master might explain to the stakeholders that while the current Increment looks promising, releasing it without the required documentation could lead to future problems, including difficulties in maintaining or scaling the product. - Facilitating a Compromise:
Scrum’s Role: The Scrum Master can facilitate a discussion between the stakeholders and the Scrum Team to find a compromise. For example, the team could agree to prioritize completing the documentation in the next Sprint, allowing for a complete Increment to be released shortly after.
Example: The Scrum Master might suggest that the stakeholders can start internal preparations or even demo the Increment to select customers while the team completes the necessary documentation.
Relevance to the PSM III Exam
In the PSM III exam, demonstrating an understanding of how to manage stakeholder expectations while upholding Scrum principles is critical. This scenario tests the Scrum Master’s ability to maintain the integrity of the Increment and ensure that it meets the Definition of Done before release.
Key Takeaways
- Definition of Done: Ensures that an Increment is fully complete and meets all quality standards before release.
- Stakeholder Education: It’s essential to educate stakeholders on the risks of releasing incomplete Increments.
- Compromise: Facilitate discussions to find a balanced approach that satisfies both the team’s and stakeholders’ needs without compromising quality.
Conclusion
As a Scrum Master, it’s important to ensure that the Scrum Team adheres to the Definition of Done, even when stakeholders push for an early release of an incomplete Increment. By educating stakeholders on the potential risks and facilitating a compromise, the Scrum Master can help ensure that only high-quality, fully complete products are delivered to customers.

Get ready for the official PSM III exam
80+ PSM III essay practice questions, each with a model answer and an in-depth explanation.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 24 random questions in 150 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSM III exam fee ($500) is paid separately to Scrum.org.
More PSM III exam questions
- One Monday morning the Developers are in chaos. Over the weekend Riley, the company’s executive product officer, made some significant changes to the work already done by the Developers. Some Developers are not able to retrieve the work they created last week. Riley says the changes were required to make the product compliant with the company’s legal guidelines. The anger and tension in the team room is huge. The Developers appear confused about how to proceed.
- An executive leader in your company recently returned from a conference. She says that many of the other executives she met were discussing business agility and what their companies are doing. She is curious what business agility means, and how can our company reap similar benefits.
- A start-up is a one-person Scrum Team. The individual takes on the accountabilities of Scrum Master, Product Owner, and Developer. You are a Scrum Master who is a friend of this person. They ask you for your opinion on how they are operating.
- Scrum is an empirical process. For empiricism to work, all artifacts must be transparent.” (PSM III)
- A Developer asks the Scrum Master, “Why must Developers attend the Daily Scrum, but Scrum Master and Product Owner attendance is optional? What happens if we have an impediment for the Scrum Master to resolve, but the Scrum Master is not present at the Daily Scrum?
