Skip to main content

Can the Increment be delivered to Stake Holders before the Sprint Review?

Last post 11:38 am December 16, 2020 by Thomas Owens
2 replies
07:24 am December 16, 2020

 

> As the Scrum Guide 2020 says that the value may be released to the stake holders prior to the end of the Sprint and the Sprint Review should never be considered as a gateway to release value.


07:44 am December 16, 2020

Can the Increment be delivered to Stake Holders before the Sprint Review?

What commitment ought to have been made for that increment, and was it satisfied?


11:38 am December 16, 2020

I think the Scrum Guide is pretty clear here:

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.

In previous iterations of the Scrum Guide, the Increment was described as "potentially releasable" and the Product Owner made the decision about whether or not to release the Increment. Considering this, the team is expected to create one or more Increments during the Sprint. Each Increment builds upon the previous Increment. The Product Owner decides if and when to release the Increment to stakeholders, so conducting a Sprint Review is not a gate to such a release.

I'd also point out that a Sprint Review could also happen without releasing an Increment. Although the Increment could be released, it could be too costly to release based on the added value. The Increment may be released later, perhaps after more work is done. However, it is still reviewed to give the Scrum Team and stakeholders a chance to align on the next steps.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.