Forums

By posting to our forums you are agreeing to the Forum terms of use.
Best describes the topics covered in Sprint Planning
Last Post 11 Mar 2014 05:31 PM by Nitin Khanna. 7 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
cologne1986
New Member
New Member
Posts:6
cologne1986

--
19 Dec 2013 05:11 AM
    Hi,

    could you please help me with the following question?


    Which answer best describes the topics covered in Sprint Planning?

    1What can be done and how to do it.
    2What went wrong in the last Sprint and what to do differently this Sprint.
    3Who is on the team and what team member roles will be.
    4What to do and who will do it.
    5How conditions have changed and how the Product Backlog should evolve.

    I think answer 1 is right or?

    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:571
    Ian Mitchell

    --
    19 Dec 2013 05:35 AM
    > I think answer 1 is right

    The question isn't simply asking for the right answer, it's asking for the best one. The process of evaluation is important. So, why do you believe answer 1 is the best? Can you explain why the other options don't seem to be as good?
    cologne1986
    New Member
    New Member
    Posts:6
    cologne1986

    --
    19 Dec 2013 05:57 AM
    Hello Ian,

    i think:

    2: It is input for other Meeting
    3: Scrum team member roles (PV, DT and Scrum Master) must be clear by beginning the project and when changed not input for sprint Planning meeting
    4: who will do it discuss in daily scrum

    But im not sure righty answer is number 1 or 2
    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:571
    Ian Mitchell

    --
    19 Dec 2013 07:03 AM
    2: It is input for other Meeting

    Yes, what went wrong & what to do differently should be discussed in a Sprint Retrospective, not Sprint Planning

    3: Scrum team member roles (PV, DT and Scrum Master) must be clear by beginning the project and when changed not input for sprint Planning meeting

    Membership could potentially change as an adaptation following a Sprint Retrospective, but it would be unusual to do so. You are right that the matter has nothing to do with Sprint Planning.

    4: who will do it discuss in daily scrum

    The team can make tentative plans for the allocation of work to team members during Sprint Planning. However, any such plans are subject to modification during the Daily Scrum, or indeed at any point. Therefore, this is not likely to be the best answer.

    What about number 5 though? Should a Scrum Team look at "how conditions have changed and how the Product Backlog should evolve"? If so, can you identify the Scrum Event that is most suitable for that purpose?

    cologne1986
    New Member
    New Member
    Posts:6
    cologne1986

    --
    09 Jan 2014 03:40 AM
    Yes. Check requirements / conditions changed is important! And impact must be considered into PB. 1 and 5 correct. But detailed and important statement answer 5.
    Thank you for your help Ian :-)
    Nitin Khanna
    New Member
    New Member
    Posts:47
    Nitin Khanna

    --
    09 Jan 2014 09:58 AM
    Hi Mandy,

    For (5), would you consider the Sprint Review event to be more appropriate?
    Darya
    New Member
    New Member
    Posts:2
    Darya

    --
    11 Mar 2014 05:25 PM
    I would say that answer 5 is more about Backlog Grooming and Sprint Review but can be done in any Scrum event as all of them are an opportunity to inspect and adapt.
    So I would say that answer 1 is the best fit.
    Please correct me if I'm wrong as I'm planning to pass the PSM assessment and think this question might come up.
    Nitin Khanna
    New Member
    New Member
    Posts:47
    Nitin Khanna

    --
    11 Mar 2014 05:31 PM
    Hi Darya,

    From an assessment perspective, I would select 1.

    If there's more clarification needed, I would encourage people to look at the Scrum Guide's section on "Sprint Planning."
    You are not authorized to post a reply.


    Feedback