Forums

By posting to our forums you are agreeing to the Forum terms of use.
When the sprint backlog can change?
Last Post 21 Mar 2013 11:44 PM by Sanjay Saini. 6 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Not Resolved
Maicol
New Member
New Member
Posts:1
Maicol

--
20 Mar 2013 11:37 AM
    Hi,

    When the sprint backlog can change?

    Both remove an item because it no longer makes sense for the scope or add an item just because the sprint backlog is over, but the sprint timebox not yet.

    What are the rules and what are the exceptions?

    thanks,

    Maicol
    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:559
    Ian Mitchell

    --
    20 Mar 2013 01:05 PM
    Hi Maicol

    In both of the situations you describe, the sprint backlog should be replanned immediately. There is usually no value in progressing a redundant PBI or in having a team wait until the end of a sprint before accepting more work.

    Note: only the development team can change the sprint backlog, because they own it. Nothing can be put in or taken out without their authorisation.
    Charles Bradley
    Basic Member
    Basic Member
    Posts:212
    Charles Bradley

    --
    20 Mar 2013 01:09 PM
    +++++1 to Ian's response, though I would also add that the PO should be involved in the discussion about what is dropped or added to a Sprint.

    In terms of adding or removing scope, you might find this chart helpful:
    http://www.scrumcrazy.com/scope
    Sanjay Saini
    New Member
    New Member
    Posts:78
    Sanjay Saini

    --
    21 Mar 2013 12:42 AM
    The whole team including PO should be involved while adding/removing anything from the sprint backlog. While adding anything new it should be PO's decision to take the top priority item from product backlog and move it into the sprint backlog.

    The team should be transparent in telling about any change in the sprint backlog during the sprint review meeting.
    Charles Bradley
    Basic Member
    Basic Member
    Posts:212
    Charles Bradley

    --
    21 Mar 2013 01:11 PM
    Sanjay,

    I want to make a distinction in your advice. The Sprint Backlog is "PBI's + a plan to deliver the PBI's". The PO doesn't ever really have to be involved if the "plan" changes, but they do have to be involved if the PBI's change materially (or the number of them forecasted for the sprint changes materially).

    So, while the PO must be involved in the decision to add/change/drop PBI's, they need not be involved in any changes to the "plan". It is also ok if the Dev Team wants to involve the PO in changing the "plan".

    Also, the Scrum Master doesn't need to be involved in any of the above, except as needed to make sure that Scrum is followed.

    Does that make sense?
    Charles Bradley
    Basic Member
    Basic Member
    Posts:212
    Charles Bradley

    --
    21 Mar 2013 01:14 PM
    While adding anything new it should be PO's decision to take the top priority item from product backlog and move it into the sprint backlog.

    Also, this is not always the case. The PO may decide to bring a PBI into the sprint that is *not* the top priority item from the PB. They may have other reasons for bringing something different into the sprint, which is why they should always be involved when changing the "scope"(PBI's) of the Sprint Backlog.

    It's also worth nothing that priority is just one factor when ordering the Product Backlog. Other factors are necessity, technical dependency, business value, etc. See the Scrum Guide for more info on that.
    Sanjay Saini
    New Member
    New Member
    Posts:78
    Sanjay Saini

    --
    21 Mar 2013 11:44 PM
    Yep

    My idea was on adding/removing a PBI in the sprint backlog. I agree that PO and SM should not be involved in sprint execution plan.
    You are not authorized to post a reply.


    Feedback