A new Scrum Master is asked by a director where in Scrum the organisation gets to see whether the last four weeks of work were worth anything, and what should change as a result. Which event is she describing?
Professional Scrum Master I, objective 3. Managing products with agility easy
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
The options
Not correct The Sprint Retrospective, where the team examines how the Sprint went
Wrong, and it is the near miss. The Retrospective inspects how the Scrum Team works — people, interactions, process, tools — not what the product is now worth to anyone.
Not correct The Daily Scrum, where progress toward the Sprint Goal is inspected every day
Wrong. The Daily Scrum is the Developers' fifteen minutes to inspect progress and adapt their plan for the next working day; it is not where stakeholders judge value.
Not correct Sprint Planning, where the Product Owner proposes how the product could increase its value
Wrong on timing. Planning is where value is proposed and a Sprint Goal is agreed; it comes before the work rather than after it, so there is no outcome to inspect yet.
Correct The Sprint Review, whose purpose is to inspect the outcome of the Sprint and determine future adaptations
Correct. It is the one event that turns the Increment outward — the Scrum Team and key stakeholders look at what was actually accomplished and at what has changed around them, then decide what to do next.
Why
The two inspection events at the end of a Sprint are easy to confuse and the exam relies on it. Sprint Review looks outward at the product and its environment and asks whether the outcome was valuable; Sprint Retrospective looks inward at the Scrum Team and asks how it works. Note the word outcome — the Review is not a demo of output, and the Guide is explicit that it is a working session the Scrum Team should avoid limiting to a presentation.
Where this comes from
- Cited
- Scrum Guide section Sprint Review
- What it says
- The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations.
Practise this
Reading one question is not practice. The trainer will draw a set from objective 3 and space the ones you get wrong.
Practise Professional Scrum Master I
More questions on this objective
- A portfolio manager has drawn up a spreadsheet ranking every requested feature by projected revenue and tells the Scrum Team to build them in that order. The Product Owner believes two of the top five items will not be used by the customers she has spoken to. Who is accountable for maximising the value of the product? machine-checked
- It is the last afternoon of the Sprint. Three of the eight selected items are coded and demonstrable on a laptop, but they have not been through the automated regression suite the Definition of Done requires. The Product Owner suggests showing them at tomorrow's Sprint Review anyway, marked as "pending test". What does Scrum say? machine-checked
- A Scrum Team spent a Sprint building a bulk-import feature. It meets the Definition of Done, it is usable, and it was released on day nine. At the Sprint Review the stakeholders explain that since the Sprint began their largest customer has moved to a different data format, and nobody will use the feature. What does Scrum say about this Sprint, and what happens now? machine-checked
- A delivery manager introduces a quarterly target: every Scrum Team must raise its velocity by fifteen per cent, and team performance reviews will cite the number. Within two Sprints the team's story point totals have risen and no more working software is reaching users than before. What is the most accurate statement about this measure? machine-checked
- A Scrum Team is agreeing what it will actually put in front of stakeholders at the end of each Sprint. Which TWO of the following statements about the Increment are true in Scrum? machine-checked
- On day six of a two-week Sprint, a Done item fixes a checkout bug that has been costing sales daily. The Product Owner wants it in production this afternoon. A release manager objects that nothing ships before it has been shown at the Sprint Review on day ten. Who is right? machine-checked