Correct Answer:

When a Product Owner raises concerns about the team's commitment and productivity based on comparisons ofvelocitywith other teams, this signals a need for coaching onempiricism, transparency, and appropriate use of Scrum metrics. As a Scrum Master, my response would focus on reframing the discussion fromoutput comparisontovalue delivery and continuous improvement.
First, I would explain thatvelocity is a team-specific, contextual measure. Velocity reflects how much work a specific team completes within a given context, using its own Definition of Done, skills, tooling, and domain complexity. The Scrum Guide does not define velocity as a performance or comparison metric.
Comparing velocity across teams is misleading and risks encouraging dysfunctional behavior, such as inflating estimates, cutting quality, or gaming the system. Therefore, a higher velocity does not automatically indicate higher productivity, commitment, or value delivery.
Second, I would explore the Product Owner's underlying concern rather than focusing on velocity itself.
Often, concerns about velocity are proxies for deeper issues such as:
* Missed Sprint Goals,
* Unmet stakeholder expectations,
* Slow value delivery,
* Quality problems or unpredictability.
As a Scrum Master, I would help the Product Owner articulatewhat outcome they are truly worried about, and then guide the discussion toward metrics and observations that better reflect those concerns, such as progress toward Product Goals, customer feedback, Increment quality, or predictability over time.
Third, I would reinforce the importance ofempiricism and transparency. If there are genuine concerns about commitment or effectiveness, these should be inspected using transparent evidence within the team's own context. The Sprint Review and Sprint Retrospective provide structured opportunities to inspect outcomes and ways of working. Rather than privately judging the team based on external comparisons, these concerns should be addressed openly and constructively with the Scrum Team.
Fourth, I would coach the Product Owner onScrum Values, particularlyRespect and Openness. Assuming lower commitment based on velocity comparisons risks undermining trust and psychological safety. Scrum encourages respecting the team as capable professionals and being open to learning what is actually limiting their effectiveness. Blame-oriented comparisons reduce the likelihood of honest inspection and improvement.
Finally, if improvement is needed, the Scrum Master should support the Scrum Team inidentifying and addressing impediments. This may involve examining workload, technical debt, unclear backlog items, excessive dependencies, or organizational constraints. The focus should be on enabling the team to improve sustainably, not on pushing them to match another team's numbers.

Correct Answer:

TheProduct Ownertakes the lead in inspection by focusing onproduct value and direction, ensuring that learning from evidence directly informs future decisions.
1. Inspecting and Ordering the Product Backlog Based on Evidence
The Product Owner continuouslyinspects the Product Backlogusing information gained from:
* Delivered Increments,
* Stakeholder feedback,
* Market changes and risks.
By ordering and refining the Product Backlog, the Product Owner leads inspection of whether the backlog still reflects themost valuable and relevant work, ensuring that adaptation is based on evidence rather than assumptions.
2. Leading Product Inspection During the Sprint Review
The Product Owner leads inspection during theSprint Reviewby framing the conversation around:
* The Product Goal,
* What value the Increment delivers,
* What has been learned.
By engaging stakeholders in inspecting the Increment and guiding discussions about what to do next, the Product Owner ensures that feedback is transformed intoProduct Backlog adaptation.

Correct Answer:

When Developers raise the lack of certain knowledge or expertise as an impediment, the Scrum Master must address the situation in a way that reinforcesScrum principles, especiallycross-functionality, empiricism, and self-management, while also supporting value delivery.
First, it is essential to verify whether this is truly animpediment. In Scrum, an impediment is something the team cannot resolve on its own. As a Scrum Master, I would facilitate a discussion with the Developers and, if appropriate, the Product Owner to inspect whether the expertise is genuinely required to achieve the desired outcome. In some cases, the scope or approach can be adapted, or the Product Backlog Item can be refined so that alternative solutions are viable. This conversation may reveal that the need for specialized knowledge is less critical than initially assumed.
Second, if the expertise is indeed necessary, the Scrum Master should encourage the team to address the issue as across-functional Scrum Team. Scrum expects teams to have, or acquire, all skills needed to deliver value. Therefore, I would ask the Developers how they couldlearn or acquire the necessary knowledge themselves. Possible options include allocating time for learning, research, training, experimenting, or building a prototype. These activities can be planned as part of the Sprint Backlog and support long-term team capability.
Third, the Scrum Master can help the team make effective use ofoutside expertise without undermining self- management. During Sprint Planning or refinement, the team may consult internal or external experts to gain insights, validate approaches, or reduce uncertainty, while still retaining ownership of the work and the Sprint Backlog.
Finally, if none of these options resolve the impediment, the Scrum Master has a responsibility tohelp the organization support the Scrum Team. This may involve facilitating access to expertise from elsewhere in the organization or, if necessary, from outside the organization. The Scrum Master does not solve the problem personally but works to remove organizational barriers so the team can proceed.

Correct Answer:

A distant Product Owner represents arisk to value delivery, transparency, and empiricism. While the Product Owner has provided a Product Backlog for the Sprint, lack of collaboration during the Sprint undermines learning and informed decision-making. As a Scrum Master, the focus should be oncoaching, enabling collaboration, and addressing systemic impediments, not substituting for the Product Owner.
1. Make the Impact Transparent
The Scrum Master should help make the impact of the Product Owner's absencevisible:
* Reduced ability to clarify Product Backlog Items,
* Slower decision-making when discoveries occur,
* Increased risk to the Sprint Goal and product value.
This transparency should be established through respectful conversations with the Product Owner and, if needed, through Scrum events such as the Sprint Retrospective.
2. Coach the Product Owner on Accountability
The Scrum Guide states that the Product Owner is accountable formaximizing valueandProduct Backlog management, which requires ongoing collaboration with Developers. The Scrum Master should coach the Product Owner to understand that handing over a backlog at Sprint Planning isnot sufficientand that availability during the Sprint is essential for empiricism.
3. Enable Better Collaboration Without Replacing the Product Owner
The Scrum Master should help create opportunities for collaboration, such as:
* Encouraging regular clarification moments during the Sprint,
* Improving Product Backlog refinement so fewer questions remain unanswered,
* Helping Developers prepare focused questions to use limited Product Owner availability effectively.
However, the Scrum Master mustnot take over Product Owner responsibilities, as this would blur accountabilities.
4. Address Organizational Causes
If the Product Owner's distance is due to workload, role confusion, or organizational pressure, this becomes an organizational impediment. The Scrum Master should raise this issue with leadership and help the organization understand the risk of an unavailable Product Owner to product outcomes.