During one Sprint the Developers complete work meeting the Definition of Done on four separate days. At the Sprint Review a stakeholder asks how many Increments the Sprint produced. What is the accurate answer in Scrum terms?
Professional Scrum Master I, objective 1. Understanding and applying the Scrum framework medium
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
Correct Four — multiple Increments may be created within a Sprint, each additive to the ones before it, and the sum of them is what is presented at the Sprint Review
Correct. An Increment is created by meeting the Definition of Done, not by reaching the end of the Sprint, so a Sprint can produce several and often does.
Not correct One — an Increment is by definition what a Sprint produces
Wrong, and it is a habit left over from how Scrum used to be taught. A Sprint produces at least one usable Increment, and nothing limits it to one.
Not correct None yet — the work becomes an Increment when it is accepted at the Sprint Review
Wrong. An Increment is born the moment a Product Backlog item meets the Definition of Done, and there is no acceptance step at the Sprint Review to wait for.
Not correct Four were created, but only the last one counts, because each Increment supersedes the one before
Wrong. Increments are additive rather than replacements: each is added to all prior Increments and thoroughly verified so that they all work together.
Why
Increments accumulate. Each one is a concrete stepping stone toward the Product Goal, additive to everything already built and verified against it, and any of them may go to stakeholders before the Sprint ends. The Sprint Review presents the sum of them to support empiricism — it is where the accumulated result gets inspected, not the moment the result comes into existence.
Where this comes from
- Cited
- Scrum Guide section Increment
- What it says
- Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism.
Practise this
Reading one question is not practice. The trainer will draw a set from objective 1 and space the ones you get wrong.
Practise Professional Scrum Master I
More questions on this objective
- A department is choosing an approach for a product where both the requirements and the technology are poorly understood and keep changing as the team learns. Someone argues for Scrum "because it is founded on empiricism". What does founding an approach on empiricism actually commit the team to? machine-checked
- At the end of a Sprint three items are functionally complete but have not been through the automated test suite the Definition of Done requires. To avoid an awkward conversation the Developers mark them Done on the board and include them in the Sprint Review. Which pillar has been damaged, and what follows from that? machine-checked
- A Scrum Team holds every event on schedule, keeps a burn-down chart and reviews its metrics carefully. For six Sprints running, the same impediment — a two-day wait for a shared test environment — has been named in the Retrospective, and nothing about it has changed. What is the accurate diagnosis? machine-checked
- Mid-Sprint, the Developers discover that a third-party API rate-limits far below what they assumed, which makes the current plan unworkable. One of them suggests carrying on as planned and raising it at the Sprint Retrospective, so the Sprint is not disrupted. What should happen instead? machine-checked
- Which THREE of these statements about Scrum theory are accurate as the framework defines it? machine-checked
- A Developer is fairly sure the design the team agreed last week will not scale. The team is halfway through the Sprint, everyone else seems content, and saying so means an uncomfortable conversation and probably rework. Which Scrum value most directly asks them to speak? machine-checked
All questions on Understanding and applying the Scrum framework