Posts tagged ‘point estimations’

March 3, 2011

When is the perfect time to play Planning Poker?

by Sampath Prahalad

Question: When is the right time to estimate the User stories in the Product backlog?

Answer: User story estimations are usually taken up during Sprint planning. To know the planning poker process involved, refer to ‘Estimating using Planning Poker’. The good thing of doing the estimations just at the beginning of the Sprint is that the Product Owner knows exactly which user story is urgent and important to be taken up at that point of time. However, the flip side is that there is pressure (and good amount of monotony) on the delivery team to complete the estimation and then perform task break up and task assignments within the small planning window. There is a tendency of the planning window becoming big and eating into the actual implementation time of the Sprint.

So then, what is the solution to this?

The solution is to make the User story estimation meeting a short recurring one and not tie it to the Sprint planning session.

Here is how it works.

read more »

January 12, 2011

Estimation using Planning Poker

by Sampath Prahalad

Now imagine that each team member is holding a deck of cards, containing the following cards:


Let’s do the estimation. The product owner says:


Before we continue, a small note on the numbers.

1: Small UI enhancement or bug fix. Easy to develop, easy to test.

2: Adding a small change/enhancement to existing functionality

3: A slightly bigger change to existing functionality or a fairly simple module to develop and test

5: A feature or enhancement that touches few other modules, We understand it well. It is complex. Testing impact is significant.

8: A feature or enhancement. We have some understanding, Some investigation is needed, it is quite complex and will touch few modules. Very significant testing impact.

13: Pretty complex. Might need more than a Sprint to accomplish by 1 person. Better to split into smaller User stories.

20: I don’t even know what you are talking about. Very complex, Needs good amount of investigation. Let us revisit it once the PM provides more clarity. Cannot estimate at this point of time.

The team starts thinking about how long the story will take.


All participants have to present a card, face down, containing their estimate. Everybody has to present a card, so Mr D and E wake up. Mr D admits that he was sleeping and asks what the story is about. It’s harder to slack off when doing estimates this way :o)

When they are done, all cards are turned over simultaneously, revealing everyone’s estimates.


Whoops! Big divergence here. The team, in particular Mr A and Mrs C, need to discuss this story and why their estimates are so wildly different. After some discussion, Mr A realizes that he has forgotten some important tasks that need to be included in the story. Mrs C realizes that, with the design that Mr A presented, the story might be smaller than 20.

After the discussion (3 minutes in total) they do another estimation round for that same story.


Convergence! OK, not complete convergence. But they agree that an estimate of 5 should be close enough. Next story.

%d bloggers like this: