What may a Development Team deliver at the end of a Sprint?

At the end of a Sprint, the Development Team is expected to deliver an increment of working software that is "done." This concept is fundamental to Scrum, which emphasizes producing a potentially shippable product increment at the conclusion of each Sprint. The term "done" implies that the increment meets the Definition of Done agreed upon by the Scrum Team, ensuring that it is fully functional and ready for release or deployment.

Delivering a "done" increment signifies that the software is not just partially completed or a draft; it has undergone necessary development steps such as coding, testing, and integration. This aligns with Scrum's primary objective of providing value to stakeholders and users through usable, working software. The clarity around what constitutes "done" is vital for maintaining quality and meeting stakeholder expectations.

In contrast, other options suggest outcomes that do not fit the Scrum framework's purpose. Draft versions of software, updated timelines, or plans for future development are not the tangible deliverables expected from the Development Team at the end of a Sprint, as they do not represent a fully functional product increment. The focus is squarely on delivering a robust and complete software increment that can be utilized immediately.