Forums

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. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

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.

Sprint Planning part 1: Selecting items for the Sprint Backlog
Last Post 19 Mar 2014 09:47 AM by Anja Huebler. 3 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Not Resolved
Franck van der Sluijs
New Member
New Member
Posts:22
Franck van der Sluijs

--
18 Mar 2014 05:21 PM
    When backlog refinement and estimation is done before the Sprint Planning meeting and when the velocity of the team is known. Then what is the sense of the first part of the Sprint Planning meeting? The Sprint Backlog can be filled “automatically” as result of the velocity and the effort of the PBI’s, isn’t it?
    Ludwig Harsch
    Basic Member
    Basic Member
    Posts:272
    Ludwig  Harsch

    --
    19 Mar 2014 03:14 AM
    Hi Franck,
    unfortunately it is not that simple. Software development is a complex process and the velocity varies with many factors. Just to name a few:
    - Who will be working on the Sprint Backlog?
    - Has the Definition of Done changed?
    - Are there any new or removed impediments?
    - Are there scarce skills in the team?
    - Technological and business coherence
    A self-organizing team can intuitively give a good estimation based on previous velocity and the factors above. To my experience this estimation is much better than a calculated "capacity" based on the available man hours. The reason is that people vary in skills and velocity and there are complex social processes in a team.
    Best, Ludwig
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1486
    Ian Mitchell

    --
    19 Mar 2014 03:58 AM
    > When backlog refinement and estimation is done before the Sprint Planning
    > meeting and when the velocity of the team is known. Then what is the sense
    > of the first part of the Sprint Planning meeting?

    I look at it this way: backlog refinement and estimation, when done regularly and conscientiously, will allow Sprint Planning to go smoothly.
    Anja Huebler
    New Member
    New Member
    Posts:3
    Anja Huebler

    --
    19 Mar 2014 09:47 AM
    ...and it's another opportunity to adapt. Furthermore it's important to ensure that there's a consensus due to prospective work for the next sprint. Sprint planning is your best chance to ensure that.
    You are not authorized to post a reply.


    Feedback