Back to Forum

When the number of sprints of a release is defined?

Last post 05:21 pm August 25, 2013 by Anonymous
2 replies
Anonymous
07:49 am August 23, 2013

Hi

I'm studying SCRUM for imolement thin in my Company.

I got this doubt because I did not find this definition in the Scrum Guide. I think this task has to be done in the Release Planning, but I'm not realy sure about this.

Can anyone help me?

Thank you.

Ian Mitchell
12:38 pm August 24, 2013

Hi Leandro

The simple answer is that the number of sprints before a release is defined in the Sprint Review. The Scrum Guide identifies the following as a suitable item for Review:

"Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product"

Please note : In Scrum, each Sprint must result in an increment of functionality that is potentially releasable at the discretion of the Product Owner. There may or may not be a cadence to those releases, and so the number of sprints before an actual release may or may not be constant.

There are other frameworks (such as SAFe) that seek to establish a release cadence, but that isn't part of the Scrum philosophy.

Anonymous
05:21 pm August 25, 2013

Thanks for the reply Ian!!

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.