In Scrum, an Increment is a concrete step toward the Product Goal. To ensure transparency, the Increment must be usable and meet the Definition of Done.
The 2020 Scrum Guide says that an Increment is created whenever a Product Backlog item is completed , and that multiple Increments may be created within a Sprint . Most importantly, the sum of the Increments must be done at the end of a Sprint .
That makes C the correct answer.
Why C is correct:
By the end of every Sprint, there must be at least one usable, Done Increment. This supports inspection at the Sprint Review and maintains transparency.
Why A is incorrect:
Scrum does not define a separate “acceptance testing phase” as a required step before an Increment becomes done.
Why B is incorrect:
Scrum does not allow waiting every 3 Sprints for an Increment. A Done Increment is expected by the end of each Sprint.
Why D is incorrect:
Scrum does not include a “release Sprint” concept as a required part of the framework.
Why E is incorrect:
The Product Owner does not decide whether an Increment should exist. Scrum requires an Increment through the Sprint’s work, and it must meet the Definition of Done.
Key Scrum point:
A product may be released whenever the Product Owner decides it is appropriate, but the Increment itself must be Done no later than the end of the Sprint.
[References:, 2020 Scrum Guide – Increment: https://scrumguides.org/scrum-guide.html#increment , 2020 Scrum Guide – Sprint: https://scrumguides.org/scrum-guide.html#sprint , ===========]
