A product Increment must be released to production at the end of each Sprint.

The Scrum Framework requires that each Sprint produces a valuable and usable Increment that meets the Definition of Done. This Increment must be in a potentially releasable state. However, the decision to actually release the Increment to production is a business decision made by the Product Owner. A release can occur at any point during the Sprint when the Product Owner deems it appropriate; it is not a mandatory event that must happen at the end of every Sprint. The key principle is that the Scrum Team creates the option to release, but not the obligation.

The statement "True" is incorrect because it misrepresents a core concept of Scrum. Mandating a release at the end of every Sprint would remove the flexibility and business-driven decision-making that is central to the Product Owner's role. The Sprint Review is a session to inspect the Increment and adapt the Product Backlog, not a formal gate for releasing value.

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide.

Page 10

"Increment" section: "An Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value." This statement explicitly decouples the act of releasing from the end-of-Sprint ceremony

indicating that a release is not a mandatory final step of every Sprint.

Page 10

"Increment" section: "In order to provide value

the Increment must be usable." This highlights the required state of the Increment—it must be usable and therefore potentially releasable

but does not mandate the release itself. The decision to release is separate from the creation of the usable artifact.

2. Verheyen

G. (2013). Scrum: A Pocket Guide (A Smart Travel Companion). Van Haren Publishing.

Section 3.5

"The Increment": "The sum of all Increments forms the product. A new Increment is not an isolated piece of work. It is an addition to the previous Increments of the product... The Product Owner decides whether to actually release an Increment." This source

written by a prominent Scrum expert

reinforces that the release is a decision owned by the Product Owner

not an automatic event.

3. Stray

V.

Sjøberg

D. I.

& Dybå

T. (2016). The daily stand-up meeting: A grounded theory study. Journal of Systems and Software

114

101-124. https://doi.org/10.1016/j.jss.2016.01.004

While this paper focuses on the Daily Stand-up

it discusses the broader context of Scrum practices. It notes that Scrum's iterative nature is designed to produce a "potentially shippable product increment" at the end of each sprint (p. 102). The term "potentially shippable" is key

as it implies capability and readiness for release

not a mandatory release action. This aligns with the principle that the decision to release is separate from the development cycle.