Choose PSM-III most accurate study material

Correct Answer:

TheSprint Reviewis a formal Scrum Event held at the end of each Sprint toinspect the outcome of the Sprint andadapt the Product Backlogif needed. Its primary purpose is to enable empirical decision-making by involving both theScrum Team and stakeholdersin inspecting the product and determining what to do next.
Purpose of the Sprint Review
The main purpose of the Sprint Review is toinspect the "Done" Product Incrementin the context of overall product progress. During this event:
* The Scrum Team presents the Increment that meets the Definition of Done.
* The Developers explain what was delivered, what was not delivered, and the challenges encountered.
* Stakeholders activelyinspect the product, often by using it, rather than reviewing documents or reports.
This inspection provides real, hands-on feedback and creates a shared understanding of the current state of the product and its direction.
Result of the Sprint Review
The Sprint Review results inheightened transparencyfor all participants. By jointly inspecting the Increment, new insights emerge about customer needs, market conditions, risks, and opportunities. These insights inform conversations aboutwhat is needed next.
Based on this shared understanding:
* TheProduct Owner collaborates with stakeholders and the Scrum Teamto adapt and update the Product Backlog.
* Completed work is accepted or further work is identified.
* New Product Backlog Items may be added, reordered, or refined to reflect the latest understanding of the product.
The Sprint Review does not aim to approve or reject work formally, but to enable learning and adaptation.

Correct Answer:

As a Scrum Master, I donot agreewith the statement that technical debt is the sole concern of the Development Team. While Developers are responsible for recognizing and understanding technical debt, its impact extends far beyond the team and affectsagility, quality, and deliveryat the product and organizational level.
First, technical debt directly influences a team'sability to remain agile. As technical debt accumulates, the cost and effort required to change the product increase. This slows down development, reduces predictability, and eventually makes it difficult-or even impossible-to deliver working software within reasonable timeframes. When agility is reduced, the entireorganizationsuffers, not just the Development Team.
Second, technical debt has a significant impact onproduct quality and delivery. High levels of technical debt often lead to defects, instability, and integration problems. This undermines the Scrum principle of delivering a "Done" Increment each Sprint. When the product cannot be reliably delivered or inspected, customers and stakeholders are directly affected, making technical debt a shared concern.
Third, while Developers are best positioned toidentify when technical debt occurs, addressing it requires collaboration across the Scrum Team. The Product Owner must understand that not all work in a Sprint will result in new functionality. Investing in reducing technical debt is an investment in future value, sustainability, and delivery capability. Stakeholders also need transparency about this trade-off.
Fourth, Scrum encourages making technical debt visible andaddressing it continuously, rather than postponing it indefinitely. This may involve adding technical debt-related work to the Product Backlog and prioritizing it alongside functional work. Treating technical debt as "invisible" or purely technical undermines empiricism and long-term value creation.

Correct Answer:

The Sprint Retrospective is a formal Scrum event where the Scrum Team inspects how the last Sprint went with respect toindividuals, interactions, processes, tools, and their Definition of Done, and identifies improvements for future Sprints. The Scrum Master attends the Sprint Retrospective inmultiple, complementary ways, consistent with the Scrum Guide.
First, the Scrum Masterjoins the Sprint Retrospective as a Scrum Team member. The Scrum Guide defines the Scrum Team as consisting of the Product Owner, Developers, and the Scrum Master. Therefore, the Scrum Master is not an external observer but afull participantin the event. As such, the Scrum Master activelyinspects people, processes, and tools, and contributes insights based on their perspective and experience, while remaining respectful of the team's self-management.
Second, the Scrum Master oftenfacilitates the Sprint Retrospective. According to the Scrum Guide, the Scrum Master is accountable for ensuring that Scrum events take place and are productive. Facilitation may include helping the team create a safe environment, encouraging openness, ensuring balanced participation, keeping the discussion focused on improvement, and helping the team stay within the timebox. However, facilitation does not imply control; the Scrum Master facilitatesto serve the team, not to direct outcomes.
Third, the Scrum Mastersupports empiricism during the Retrospective. By fostering transparency, encouraging honest inspection, and helping the team identify actionable improvements, the Scrum Master strengthens the Scrum pillars oftransparency, inspection, and adaptation. The Scrum Master may also help the team turn improvement ideas into concrete actions that can be planned for the next Sprint.
Finally, the Scrum Master helps ensure that the Sprint Retrospective results inmeaningful adaptation. While the Scrum Team decides what improvements to implement, the Scrum Master supports the team in identifying impediments, coaching on improvement techniques, and helping remove organizational or systemic obstacles that are beyond the team's direct control.
In summary, the Scrum Master attends the Sprint Retrospective byjoining as a full Scrum Team member, participating in inspection,often facilitating the event, andsupporting continuous improvement and empiricism. This balanced participation ensures that the Retrospective remains a powerful mechanism for learning and adaptation rather than a ritualistic meeting.

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.