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.

The Sprint Planning Input
Last Post 30 May 2014 12:44 PM by Timothy Baffa. 2 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Resolved
Rafal Balcerski
New Member
New Member
Posts:3
Rafal Balcerski

--
29 May 2014 08:32 PM
    Hello,

    According to the the Scrum Guide description of the Sprint Planning:

    "The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team."


    On the other hand, in the Sprint Review description:

    "The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning."


    Isn't it that the "last Sprint Review conclusions on what to do next" are missing in the description of the Sprint Planning input?
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1575
    Ian Mitchell

    --
    29 May 2014 09:12 PM
    • Accepted Answer
    When the team collaborate on what to do next, the Product Backlog will be discussed and perhaps refined further, and the Product Owner will reorder it appropriately. The backlog should be rendered in the best possible state for Sprint Planning.
    Timothy Baffa
    Basic Member
    Basic Member
    Posts:227
    Timothy Baffa

    --
    30 May 2014 12:44 PM
    The sprint review provides valuable input to product backlog maintenance (prioritization, new user stories).

    The Product Backlog is the direct input into Sprint Planning Part 1. The latest Product Increment is the result of the previous sprint, and is the input to PB maintenance. Team performance is also considered as the team collaborates with the PO to craft the offer in Sprint Planning Part 1.

    Team Capacity for the upcoming sprint is calculated in Sprint Planning Part 2.
    You are not authorized to post a reply.


    Feedback