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.

Development team composition and PO typical activities
Last Post 10 Feb 2015 05:02 AM by Ian Mitchell. 5 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Adrian Turcanu
New Member
New Member
Posts:12
Adrian Turcanu

--
26 Jun 2014 09:52 AM
    hi,

    Please give your ideas on the following:

    1. Is the Development Team's composition allowed to change during a sprint?

    2. Are there any typical activities that a Product Owner would undertake in the phase between current sprint review and the next sprint planning? updating project plan with stakeholders, refining product backlog, or there are no such activities.
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1556
    Ian Mitchell

    --
    26 Jun 2014 12:07 PM
    A Development Team should self-organize in order to meet the Sprint Goal. If that means changing team composition mid-sprint then so be it, but it would be a drastic action and the repercussions could be more disruptive than beneficial.

    A new Sprint commences immediately upon the termination of its predecessor. The only activity that any team members typically engage in between a Sprint Review and Sprint Planning is the Sprint Retrospective. There is no time for anything else.
    Hiep To Dinh
    New Member
    New Member
    Posts:1
    Hiep To Dinh

    --
    02 Jul 2014 02:15 AM
    About the second quesiton: 2. Are there any typical activities that a Product Owner would undertake in the phase between current sprint review and the next sprint planning? updating project plan with stakeholders, refining product backlog, or there are no such activities.

    The answer here should be Sprint Retrospective but there is no option for it. Then the most suitable could be No such activities?
    Randy Ho
    New Member
    New Member
    Posts:47
    Randy Ho

    --
    02 Jul 2014 06:45 AM
    The Sprint Retrospective and review happen at the end of a sprint. When a sprint ends, a new one is immediately started.

    A sprint starts with a planning session. The retrospective happens at the end of a sprint so that the entire sprint can be inspected upon and adapted.

    Updating stakeholders on the project plan, refining the product backlog should be done continuously and iteratively. Posting the release burndown in a visible and accessible location and keeping it updated can be one way of emitting project plans to stakeholders.
    Werner Moser
    New Member
    New Member
    Posts:1
    Werner Moser

    --
    10 Feb 2015 03:26 AM
    I could fully agree with you, if we talked about Core-Scrum.
    But the Scrum Guide does not say, that a Sprint has to begin with the Planning meeting. Core Scrum does!
    The Guide only tells us, that the work for the Sprint is planned in the Sprint planning.
    So if a review shows, that the backlog has to be changed significantly one could do a Backlog refinement session together with the team before the planning.
    From this point of view, the answer could possibly also be: "Refining the Backlog".
    I am not sure if "there is no time for anything else".


    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1556
    Ian Mitchell

    --
    10 Feb 2015 05:02 AM
    The Scrum Guide says, with regard to Sprint Planning:

    "Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less". No exception is made, at the beginning of the Sprint, for anything to occur other than planning for this immediate start.

    It's quite acceptable for outstanding Product Backlog refinement to be taken care of in the Review of the *previous* Sprint. This includes assessing undone work and revising the Product Backlog accordingly. However, it wouldn't be acceptable to roll the debt from one time-box (such as inadequate refinement) over into the next one, and to try and deal with it before planning commences. To do so would amount to robbing the next Sprint of the time available.
    You are not authorized to post a reply.


    Feedback