For the purpose of transparency, when does Scrum say a valuable and useful Increment must be available? (choose the best answer)

The core purpose of a Sprint is to create a valuable and useful Increment of the product. According to the Scrum Guide, this Increment is a concrete, inspectable result that must be available by the end of the Sprint. This regular cadence is fundamental to Scrum's empirical nature. It provides a transparent, tangible measure of progress toward the Product Goal. Stakeholders can inspect this "Done" Increment at the Sprint Review, fostering a shared understanding and enabling informed decisions and adaptations for the next Sprint. This cycle of creating an Increment every Sprint is the heartbeat of Scrum.

B. Waiting for multiple Sprints contradicts the principle of frequent feedback and reduces transparency, delaying the opportunity to inspect and adapt.
C. The concept of a "Release Sprint" is not a formal part of the Scrum framework; a potentially releasable Increment is expected every Sprint.
D. In Scrum, testing is an integral activity performed within the Sprint to meet the Definition of Done, not a separate phase that follows development.
E. An Increment is a mandatory outcome of every Sprint's work, not something created only upon the Product Owner's ad-hoc request. ---

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. Scrum.org.

Page 8

"The Sprint" section: "Sprints are the heartbeat of Scrum

where ideas are turned into value... The purpose of the Sprint is to create a valuable

useful Increment."

Page 10

"Increment" section: "An Increment is a concrete stepping stone toward the Product Goal... The sum of the Increments is presented at the Sprint Review thus supporting empiricism." This confirms the Increment is the inspectable result available at the end of the Sprint.

2. Verwijs

C.

& Russo

D. (2022). A Theory of Scrum's Five Events. In Proceedings of the 23rd International Conference on Agile Software Development (XP 2022). Association for Computing Machinery.

Section 3.1

"The Sprint": The paper describes the Sprint as the "containing event" whose primary purpose is to "create a ‘Done’ Increment." This reinforces that the creation of an Increment is tied directly to the Sprint cycle. (DOI: https://doi.org/10.1145/3533716.3533729)

3. Rubin

K. S. (2012). Essential Scrum: A Practical Guide to the Most Popular Agile Process. Addison-Wesley Professional.

Chapter 5

"Sprints"

Page 91: "At the end of each sprint

the team produces a potentially shippable product increment—a version of the product of high-enough quality to be given to customers." This is a widely used textbook in university courses and confirms the end-of-sprint timing.