PSM-I · Question #151
For the purpose of transparency, when does Scrum say a new increment of working software must be available?
The correct answer is D. At the end of every Sprint. According to the Scrum Guide, a usable Increment must be created at the end of every Sprint. This is a fundamental principle of Scrum: each Sprint produces a potentially releasable Increment that meets the Definition of Done. This cadence of producing working software every…
Question
For the purpose of transparency, when does Scrum say a new increment of working software must be available?
Options
- AAfter the acceptance testing phase.
- BBefore the release Sprint.
- CEvery 3 Sprints.
- DAt the end of every Sprint.
- EWhen the Product Owner asks to create one.
How the community answered
(34 responses)- A3% (1)
- C3% (1)
- D88% (30)
- E6% (2)
Explanation
According to the Scrum Guide, a usable Increment must be created at the end of every Sprint. This is a fundamental principle of Scrum: each Sprint produces a potentially releasable Increment that meets the Definition of Done. This cadence of producing working software every Sprint is what enables transparency - stakeholders and the Product Owner can inspect real working software rather than status reports or partially completed features. Option A (after acceptance testing) implies testing is separate from development, which contradicts Scrum's integrated approach. Option B (before release Sprint) references a 'release Sprint,' which is an anti-pattern. Option C (every 3 Sprints) defeats the inspect-and-adapt feedback loop. Option E (when the PO asks) gives too much discretion and undermines the consistent cadence Scrum requires.
Topics
Community Discussion
No community discussion yet for this question.