# Increment The Increment is a [[4.1 Product Backlog|Product Backlog item]] which meets the [[5.3 Definition of Done|Definition of Done]][^the-moment-a-pbi][^work-cannot-be]. Each Increment[^an-increment-is] is: - a valuable improvement towards the [[5.1 Product Goal|Product Goal]], - built on top of previous Increments. [^an-increment-is]: "An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable."[^scrum-guide-2020] [^the-moment-a-pbi]: "The moment a Product Backlog item meets the Definition of Done, an Increment is born."[^scrum-guide-2020] [^work-cannot-be]: "Work cannot be considered part of an Increment unless it meets the Definition of Done."[^scrum-guide-2020] For each [[3.1 Sprint|Sprint]], there can be multiple Increments[^multiple-increments]. The [[2.1 Developers|Developers]] are [[1.8 commitment|committed]] in creating at least one[^developers-definition]. The whole [[1.5 Scrum Team|Scrum Team]] is accountable for the [[4.3 Increment|Increment]][^increment-sprint-accountability]. [^multiple-increments]: "Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, 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."[^scrum-guide-2020] [^developers-definition]: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."[^scrum-guide-2020] [^increment-sprint-accountability]: "The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint."[^scrum-guide-2020] The Increment is presented at the [[3.4 Sprint Review|Sprint Review]] to the participating [[6.2 stakeholders|stakeholders]], but it can be delivered before. The [[6.1 organization|organization]] can [[1.3 Scrum theory|inspect]] the [[4.3 Increment|Increment]] at the [[3.4 Sprint Review|Sprint Review]], giving visibility to some of decisions of the [[2.2 Product Owner|Product Owner]][^for-po-succeed][^purpose-sprint-review]. [^for-po-succeed]:For Product Owners to succeed, the entire organization must respect their decisions. These decisions are visible in the content and ordering of the Product Backlog, and through the inspectable Increment at the Sprint Review."[^scrum-guide-2020] [^purpose-sprint-review]: "The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed." The [[2.3 Scrum Master|Scrum Master]] helps "the Scrum Team focus on creating high-value [[4.3 Increment|increments]] that meet the [[5.3 Definition of Done|Definition of Done]]"[^scrum-guide-2020]. [^scrum-guide-2020]: [[1.2 Scrum Guide|Scrum Guide (2020)]] [^multiple-increments]: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint." "Multiple Increments may be created within a Sprint."[^scrum-guide-2020] ## Increments and Nexus In the [[N1.1 Nexus framework|Nexus framework]], the Increments of the [[1.5 Scrum Team|Scrum Teams]] are combined in an [[N4.2 Integrated Increment|Integrated Increment]][^represents-current-sum]. [^represents-current-sum]: "The Integrated Increment represents the current sum of all integrated work completed by a Nexus toward the Product Goal. The Integrated Increment is inspected at the Nexus Sprint Review, but may be delivered to stakeholders before the end of the Sprint. The Integrated Increment must meet the Definition of Done."[^nexus-guide-2021] [^nexus-guide-2021]: [[N1.2 Nexus Guide|Nexus Guide (2021)]]