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.

How to explain to the team that they need to come up with an estimation
Last Post 25 Feb 2014 09:29 PM by Ian Mitchell. 3 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Not Resolved
Pablo Rossi
Basic Member
Basic Member
Posts:173
Pablo Rossi

--
25 Feb 2014 12:33 PM
    Hi all,

    I'm wondering how a Scrum master can assist/coach teams in coming up with an estimation when a story still generates functional discussions during the first part of the Sprint planning meeting.

    1) Due to time constraint (you want to be able to estimate x stories for the upcoming sprint), does the Scrum master (at some moment in time) stops the discussion and ask the team to come up with a guestimation? If yes, how would the Scrum master explain that towards the team because they are still in the mindset of "how can we give a estimation if we don't know all the specs".

    2) Is the team allowed to refuse a story, but has the highest business value for the customer?


    Cheers, P
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1535
    Ian Mitchell

    --
    25 Feb 2014 05:23 PM
    Make use of backlog refinement sessions. The Development Team and the Product Owner should attend although the Scrum Master may facilitate.

    It's reasonable to spend up to 20% of each Sprint grooming user stories so they are in a fit state for Sprint Planning, and this can also include their estimation. Product Backlog refinement should allow Sprint Planning to occur smoothly within its time-box and without impediment.

    A Development Team can refuse to accept any item into their Sprint Backlog. However, if they have had sight of the Product Backlog during refinement sessions, surprises for the Product Owner can be avoided.
    Pablo Rossi
    Basic Member
    Basic Member
    Posts:173
    Pablo Rossi

    --
    25 Feb 2014 08:44 PM
    HI Ian, thanks for the quick reply!


    Posted By Ian Mitchell on 25 Feb 2014 10:23 PM
    Make use of backlog refinement sessions. The Development Team and the Product Owner should attend although the Scrum Master may facilitate.


    I've read that the goal of a refinement session is to get more understanding of the stories. When stories are clear during the refinement session, estimations can be given during this session.
    Even if we have a refinment session, I think we can agree that the stories can never be 100% clear so at some point the team needs to start estimating

    I think I'm more looking for a way to tell the team that we need to start estimating the stories while it's still a bit unclear.
    What do you usually say to a team?
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1535
    Ian Mitchell

    --
    25 Feb 2014 09:29 PM
    > I think I'm more looking for a way to tell the
    > team that we need to start estimating the
    > stories while it's still a bit unclear. 
    > What do you usually say to a team? 

    I'll ask them to do a team sort, which they usually find easier. I've described the technique in this thread:

    https://www.scrum.org/Forums/aft/500
    You are not authorized to post a reply.


    Feedback