Scrum Master Practice Test

The Sprint Retrospective is an event for the entire Scrum Team. The Scrum Guide explicitly states that the Scrum Team (which includes the Scrum Master, Product Owner, and Developers) participates in the Retrospective. The Product Owner is an integral member of the Scrum Team and contributes process insights (such as stakeholder collaboration or backlog refinement quality), so they must not be excluded.

In Scrum, the Sprint is the container for the rest of the events, so its cadence provides the team's core rhythm. Backlog uncertainty is normal and should be managed through planning and refinement rather than by casually deferring the Sprint itself.

As a facilitator and coach, the Scrum Master must ensure that Scrum events are positive, productive, and kept within their timeboxes. When personal attacks occur, the Scrum Master must intervene to uphold the Scrum Value of Respect and protect psychological safety, while helping the team pivot back to productive, professional problem-solving.

Developers can choose any structure or technique that keeps the focus on progress toward the Sprint Goal. is correct because Scrum does not require one rigid script for the Daily Scrum; it requires focus on progress toward the Sprint Goal and adaptation of the plan. The cited source, The Scrum Guide, supports this answer for the Daily Scrum scenario rather than the adjacent distractors.

The Product Owner is one person, not a committee. While the Product Owner may represent the desires of a committee or stakeholders in the Product Backlog, those who want to change the Product Backlog's content or ordering must attempt to convince the Product Owner. The entire organization must respect the Product Owner's decisions for Scrum to succeed.

The Scrum Guide states that the Developers select the items from the Product Backlog to include in the Sprint. The Scrum Team plans the Sprint work, and the Developers are the ones who decide how much they can undertake. Relying on past performance (velocity) and understanding their active capacity helps the Developers make a realistic plan, and they should not be pressured by external stakeholders to overcommit.

A Scrum Team consists of one Scrum Master, one Product Owner, and Developers. is correct because The correct framing is that the Scrum Team has three accountabilities: Product Owner, Scrum Master, and Developers. The cited source, The Scrum Guide, supports this answer for the Scrum Team scenario rather than the adjacent distractors.

The Sprint Goal is the commitment for the Sprint Backlog, while the Product Goal belongs with the Product Backlog and the Definition of Done belongs with the Increment. Keeping those pairings clear improves transparency about what each artifact is trying to accomplish.

Ensure the Developers understand the purpose of the Daily Scrum as a 15-minute planning event, and coach them to discuss deep technical details after the event. is correct because The Scrum Master is responsible for ensuring that Scrum events take place and are positive, productive, and kept within the timebox. The cited source, The Scrum Guide, supports this answer for the Scrum Master Accountability scenario rather than the adjacent distractors.

Empiricism relies on frequent inspection and timely adaptation. The Scrum events (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) are specifically designed to provide regular opportunities for inspection and adaptation. Delaying inspection to a three-month release cycle defeats the purpose of the two-week Sprint feedback loop and increases the risk of delivering the wrong product.