Skip to main content

Agile Story Point Estimation Techniques - Planning Poker - By Ankur Mistry

In my previous article, we have discussed what is Agile Story Point Estimation. In this article, we will learn how to estimate story points using "Planning Poker" cards.

Planning Poker is a relative estimation technique used by teams to estimate the user story.

Before starting, the planning poker team will define and agree on the parameters to measure the amount of work like a number of screens and number of fields etc. Identify a reference story that the team has done before or understands very well. Ideally, they will compare other stories with the reference story and one by one do the estimation.

Steps
  1. Product Owner will explain the story to be estimated and the development team will ask questions if they have any issues or unclarity. For example -

    Design Related- Do we have to learn new things before starting the design/HTML/jQuery etc?
    Coding Related- Do we have any code class library ready or we have to write it from the scratch?
    Testing Related- Any specific setup required for Unit testing?

    Other questions like any dependencies in tasks, does anyone have written code for similar stories etc. are also included.
  2. Once the Team understands the user story, they compare the story with the reference story that they have selected.
  3. Each team member comes up with the size of the story related to the reference user story.
  4. Team members show the card to everyone.


    Image Source: Autentia Planning Poker 
  5. If the team member has consensus or the variance is less, assign the story points and move on to the next.
  6. If there are conflicts, then each team member explains the rationale behind the number.
  7. The product owner explains the story further or clarifies misunderstanding if any.
  8. Team repeats steps until the team has consensus or variance is less or up to three rounds.
    image source: https://www.youtube.com/watch?v=sCCUEtjCpCs  
Even after three rounds, if there is no consensus and variance is high, assign the biggest number and move forward.

For first few months with the team, it's challenging but once the team is used to it, it will be great fun and useful for the product owner to make decisions for the team as well as the business.

I hope you liked this article. In my next article, we will discuss T-Shirt size estimation.

Reference
  • https://leanpitch.com/
  • http://www.agilebuddha.com/agile/agile-estimation-8-steps-to-successful-story-point-estimation/

Comments

Post a Comment

Popular posts from this blog

Agile Story Point Estimation Techniques - T-Shirt Sizing by - Ankur Mistry

In my previous articles, we have discussed  Agile Story Point Estimation  and  Agile Story Point Estimation Techniques - Planning Poker . In this article, we will learn Story Point Estimation using T-Shirt Size Technique. What is T-shirt sizing? T-shirt Sizing is one of the Story points sizing technique to estimate user story usually used in agile projects. It's a relative Estimation Technique. Rather than using a number of planning pokers, here, Items are classified into t-shirt sizes: XS, S, M, L, XL. The term originates from the way T-shirt sizes are indicated in the US. Rather than having T-shirts in sizes 4, 5, 6 etc, there are just a few sizes: Small (S), Medium (M), Large (L) and Extra Large (XL) and so on. With T-shirt measuring, the development team is made a request to evaluate whether they think a story is extra-small, small, medium, large, extra-large, or double extra-large. By expelling the numerical score, the development team is allow...
Post a Comment
Read more

Retrospective Meetings By:Namrata Parik

This article talks about the least important meeting in a Sprint, the retrospective meeting, at  least as considered by the business and sometimes also by the developers. It is often considered to be a waste of time and given the least priority, and sometimes even omitted if there are time constraints. In fact it is the most important meeting but does not show any immediate business value. Talking about my own experience, we were newly into the project and the geek in the team was not getting enough technical tasks to devour, resulting in not so good documentations by him and his general disinterest in the team. This was discussed in the retrospective and his problem was faced, assessed and solved within a span of two weeks (a single Sprint), and he was given enough tasks to fulfill his coding appetite, resulting in better output by the entire team. Talking about retrospective techniques, the most effective way to conduct a retrospective is the Timeline Review. The te...
Post a Comment
Read more

Scrum Framework - 5 Events in Scrum Framework - By Ankur Mistry

In my previous articles, we have discussed  3 Roles  and  3 Artifacts  in Scrum. In this article, we are going to discuss 5 events in the Scrum Framework. There are Five events in Agile Scrum Framework. Sprint Planning Daily Scrum Sprint Review Sprint Retrospective The Sprint ( Figure: Life cycle of Scrum from  http://www.agiletroop.com/product/life-cycle-of-scrum/ ) Sprint Planning  is the event in which the Product Owner presents the ordered product backlog to the development team. As the word suggests, 'Sprint Planning' means we are going to plan the work to be done in the Sprint. There are two main parts - 'What' and 'How'. 'What' can be done in this Sprint? 'How' will the selected work get done? What can be done in the Sprint - In this part, the Product Owner presents the product backlog items with high business value tasks as a first priority to the development team. All team members collaborate to understand ...
1 comment
Read more