Study PSM I Events, Timeboxes, and Inspection: key concepts, common traps, and exam decision cues.
Scrum events are a connected operating system, not separate meetings. PSM I questions here often punish answers that turn events into status reviews, management gates, or optional ceremonies.
| Event | Stronger purpose |
|---|---|
| Sprint | fixed-length container for value creation and learning |
| Sprint Planning | align on Sprint Goal, selected work, and initial plan |
| Daily Scrum | inspect progress and adapt the near-term plan |
| Sprint Review | inspect the Increment with stakeholders and adapt the Product Backlog |
| Sprint Retrospective | improve how the team works together |
Timeboxes create urgency, protect focus, and keep feedback loops short. They do not mean every event must consume the full allowed time. The stronger answer protects the purpose of the event first and treats the timebox as a limit, not a target.
A team wants to skip the Sprint Review because the Increment is already accepted by internal testers. The stronger Scrum answer is to keep the Sprint Review, because its purpose is broader than internal acceptance. It is where stakeholders inspect the Increment and product direction can adapt.
What is the strongest reason to keep the Sprint Review distinct from the Sprint Retrospective?
A. The Review inspects the product and stakeholder direction, while the Retrospective improves the team’s way of working
B. The Review is for Developers only, while the Retrospective is for the Product Owner only
C. The Review finalizes task assignments, while the Retrospective approves release dates
D. The Review replaces backlog refinement, while the Retrospective replaces Sprint Planning
Best answer: A
Why: Scrum keeps product inspection and team-process improvement separate on purpose because they answer different questions.
Why the others are weaker: B, C, and D invent purposes Scrum does not assign to those events.