Which TWO of these statements about the Increment are true in Scrum?
Professional Scrum Master I, objective 1. Understanding and applying the Scrum framework hard
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
Choose 2.
Correct Work cannot be considered part of an Increment unless it meets the Definition of Done
Correct. This is what makes the word Increment mean something: it is not a collection of nearly finished work, and an item that misses the Definition of Done returns to the Product Backlog instead.
Correct In order to provide value, the Increment must be usable
Correct. Usable is the bar, and it is why work that only becomes usable after a later integration phase does not qualify.
Not correct An Increment must be released to customers at the end of every Sprint
Wrong. Scrum requires the Increment to be usable, not that it is shipped. Whether to release is a decision about value and belongs to the Product Owner, who may release mid-Sprint or hold several Increments back.
Not correct An Increment is a concrete stepping stone toward the Sprint Goal
Wrong by one word, which is why it is offered: the Increment is a stepping stone toward the Product Goal. The Sprint Goal is the Sprint Backlog's commitment, not the Increment's.
Not correct An Increment becomes Done when it is presented and accepted at the Sprint Review
Wrong. It is Done the moment it meets the Definition of Done, which may be any day of the Sprint, and Scrum has no acceptance step at the Review.
Why
Attach each commitment to the right artifact and half of these questions collapse: Product Backlog to Product Goal, Sprint Backlog to Sprint Goal, Increment to Definition of Done. The Increment's own properties are then short — usable, additive, thoroughly verified against everything already built, and created the instant the Definition of Done is met rather than at a meeting.
Where this comes from
- Cited
- Scrum Guide section Increment
- What it says
- Work cannot be considered part of an Increment unless it meets the Definition of Done.
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