Forums

By posting to our forums you are agreeing to the Forum terms of use.
When the number of sprints of a release is defined?
Last Post 25 Aug 2013 04:21 PM by LeandroRibeiro. 2 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
LeandroRibeiro
New Member
New Member
Posts:2
LeandroRibeiro

--
23 Aug 2013 06:49 AM
    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
    Advanced Member
    Advanced Member
    Posts:575
    Ian Mitchell

    --
    24 Aug 2013 11:38 AM
    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.
    LeandroRibeiro
    New Member
    New Member
    Posts:2
    LeandroRibeiro

    --
    25 Aug 2013 04:21 PM
    Thanks for the reply Ian!!
    You are not authorized to post a reply.


    Feedback