Demonstrating Scrum Team Improvement
A Scrum Team’s journey towards delivering more valuable and useful Increments is continuous. After practicing Scrum for over six months, there should be measurable indicators of improvement. These improvements can manifest in various ways, such as better quality of work, increased productivity, or enhanced collaboration. Here, I provide two examples from my experience that demonstrate how a Scrum Team has measurably improved over time.
Exam Question
A team has been practicing Scrum for over 6 months. Consider that a goal of the Scrum Team is to get better and better at delivering valuable and useful Increments.
Provide two examples from your experience that measurably demonstrate that a Scrum Team has improved.
Example 1: Improved Velocity and Predictability
- Context:
– The Scrum Team had been struggling with predictability and often failed to complete their Sprint commitments. Over time, this led to inconsistent delivery of Increments, which affected stakeholder confidence. - Improvement:
– After six months of continuous inspection and adaptation, the team began to show a consistent improvement in velocity. They implemented better refinement practices, clearer definition of done, and more accurate estimation techniques. As a result, the team’s velocity became more stable, and their ability to predictably deliver on Sprint commitments improved significantly. - Measurement:
– Velocity Consistency: The team’s velocity stabilized, with less fluctuation between Sprints, indicating better planning and execution.
– Sprint Goal Achievement Rate: The rate at which the team achieved Sprint Goals increased from 60% to 90%, demonstrating improved predictability and alignment with the Product Owner’s expectations.
Example 2: Reduction in Defects and Technical Debt
- Context:
– Initially, the Scrum Team faced challenges with maintaining high-quality Increments, leading to an accumulation of technical debt and frequent defects in delivered Increments. This was impacting the team’s ability to deliver valuable Increments consistently. - Improvement:
– The team focused on integrating Test-Driven Development (TDD) and Continuous Integration (CI) practices into their workflow. They also prioritized addressing technical debt during each Sprint. Over time, this led to a significant reduction in the number of defects and a more maintainable codebase. - Measurement:
– Reduction in Defects: The number of defects found during Sprint Reviews and post-release dropped by 50%, indicating a higher quality of Increments.
– Technical Debt Reduction: The team tracked technical debt using a specific metric and reduced it by 40% over the six months, leading to more sustainable development and faster delivery of new features.
Relevance to the PSM III Exam
In the PSM III exam, demonstrating a deep understanding of how continuous improvement can be achieved within a Scrum Team is essential. These examples showcase practical applications of Scrum principles and how they contribute to a team’s ability to deliver high-value Increments consistently.
Key Takeaways
- Velocity and Predictability: Consistent velocity and improved Sprint Goal achievement rates are strong indicators of a Scrum Team’s maturity and ability to deliver valuable Increments.
- Quality Improvement: A focus on reducing defects and managing technical debt can significantly enhance the value and usability of Increments, contributing to the long-term success of the product.
Conclusion
A Scrum Team’s ability to continuously improve in delivering valuable Increments is a testament to the effectiveness of Scrum. By focusing on areas such as predictability, velocity, and quality, teams can make measurable progress over time.

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
- Discuss the correlation between “Technical Debt” and Not “Done” work?
- The Product Owner is a part of the Scrum Team.
- 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.” (PSM III)
- 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.
