Forums

By posting to our forums you are agreeing to the Forum terms of use.
A question
Last Post 22 Aug 2012 05:02 PM by Alex Armstrong. 4 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
fereydoun
New Member
New Member
Posts:1
fereydoun

--
18 Aug 2012 10:13 PM
    " A properly functioning scrum team will have at least one release sprint and may well have several"
    this sentence true or fals and why?
    Gary Pedretti
    New Member
    New Member
    Posts:4
    Gary Pedretti

    --
    20 Aug 2012 08:31 AM
    The sentence is false.

    Any adjective in front of the word "Sprint" is invalid - there are NO Testing Sprints, Stabilization Sprints, Architecture Sprints, Rest Sprints, etc.

    If the Increment - a potentially shippable piece of software - is an artifact that comes out of the Sprint, then any activity those adjectives describe would have to take place within every Sprint, by definition.
    MrHinsh
    New Member
    New Member
    Posts:17
    MrHinsh

    --
    20 Aug 2012 09:15 AM
    When you have software that has more than a small amount of work to get it into production Scrum Teams may opt to have a Sprint dedicated to that Sprint Goal.

    Therefor you may have a Sprint Goal of "Version 2 of our software runs in production" with all of the stories needed to get there assigned to this single sprint.

    While this is common your goal should be to minimise this as it detracts from the flow of delivering added value to the customers. If you find that this is taking up a lot of your time (more than one Sprint) then you should impress upon the product owner that you need to spend some time streamlining that process to minimise its impact on the team and increase the "features" that they build for him.

    Ideally your entire deployment process should be able to be conducted as part of the sprint as well.
    Dominik Maximini
    New Member
    New Member
    Posts:64
    Dominik Maximini

    --
    21 Aug 2012 02:56 AM
    Hi fereydoun,

    let me clarify it a bit further for you: If somebody asks you that question to improve his Scrum knowledge, the answer is of course "false" - if the team is properly functioning, it will product a "Done" increment every Sprint and not only every release.

    However, there are some situations out there in the ugly world that require you to introduce such "stabilization phases" or "release sprints". For example in the automotive industry, you aren't really "Done" before you did proper summer- and winter-testing, which takes several weeks each. It's impossible to do that every Sprint, but it's required to deliver a fully integrated "Done" product.

    If you view your question under this light, the words "at least" jump at you. This would imply that Scrum requires you to do release Sprints, which is obviously not correct, even though there may be certain circumstances where your team requires such.

    Does this help you?
    Alex Armstrong
    New Member
    New Member
    Posts:74
    Alex Armstrong

    --
    22 Aug 2012 05:02 PM
    While healthy discussion about the underlying rationale for questions and answer is highly encouraged, please try to stay away from directly posting questions and answers from the assessments. Doing so doesn't help anyone.

    Thank you,
    Alex
    You are not authorized to post a reply.


    Feedback