The app team at Nestbot finishes three separate Product Backlog items on three different days within the same Sprint, each one meeting the Definition of Done as soon as it's finished. According to the Scrum Guide, how many Increments has the team created that Sprint?
Select an answer to reveal the explanation.
Short Explanation
Nothing says a team has to wait until Sprint Review to have an Increment. The moment a Product Backlog item meets the Definition of Done, it becomes part of an Increment, and that can happen multiple times inside a single Sprint. Three items finished on three different days can genuinely mean three Increments.
Full Explanation
The Guide is explicit that multiple Increments may be created within a single Sprint, and each one comes into being the moment a Product Backlog item meets the Definition of Done, not on a fixed schedule tied to the Sprint's end. So a team finishing three qualifying items on three different days has, in the Guide's own terms, produced multiple Increments during that Sprint. Believing a single Increment is released only at Sprint Review confuses the moment an Increment is created with the separate question of when the Product Owner chooses to release it; those are different decisions. Claiming no Increment exists until the Sprint ends contradicts the Done-based trigger directly and would leave teams unable to inspect real progress mid-Sprint. Counting Increments per Developer misreads the Increment as a personal artifact rather than a cumulative, shared body of the team's Done work. An operational check at Nestbot: log the date each item actually meets the Definition of Done, not the date it's demoed, and treat that as the moment the Increment count changes.