Estimating in Points Seems a Bit Stupid!

A while ago I blogged about “What’s the Point in estimating?“.

To be honest, I didn’t understand the concept of estimating in Points when we first adopted agile. Actually, I thought it sounded a bit stupid!

But I get it now, and it makes a lot of sense.

I would add to my original blog post now, that developers are more inclined to give a relative estimate in points based on minimal information about a feature, whereas to estimate in days implies precision and can be a barrier to getting someone to commit to how big it is.

But the key thing about estimating in points is actually about how a team’s estimating is self-correcting. Even if they are bad at it.

Let me give you some examples…

Let’s say your team estimates they can complete 100 Points in a Sprint. Actually, they over-estimated because they’re naturally cautious, and in practice you find they deliver 150 Points. Great news! Next Sprint you bring 150 Points into Sprint Planning. Imagine that in hours. Imagine your team’s response when you say they tend to be cautious, so your going to plan on them doing 7.5 days a week! Not going to go down too well I suspect.

Now look at it the other way round. The team again estimates 100 Points but actually achieves only 50. In this case the team is over-optimistic and let’s say they consistently under-estimate, causing late delivery or delivery of reduced scope. You adjust accordingly and bring only 50 Points into the Sprint, because you know that’s what they can typically achieve. They start to deliver on time and the business unit or customer is happy because you’re meeting expectations. Now imagine this in days. You tell the customer or business you’re only going to plan on the team doing 2.5 days a week because you know they tend to under-estimate, or you use negative statements like you’re planning on 50% productivity or utilisation. Not going to go down well either!

Using Points makes the unit of estimation abstract, which makes it easier to commit to, and easier to adjust your commitments to.

Of course on a project, making this adjustment could mean you won’t be able to deliver everything you planned to in the original timescales. Agile – and estimating in Points – doesn’t solve that. But it will highlight it early, while there’s still time to do something about it.

And the self-correcting nature of estimating in points will help you to meet expectations more consistently.

Kelly.

Photo by MissTurner

Share on facebook
Facebook
Share on twitter
Twitter
Share on linkedin
LinkedIn

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Posts

In The Zone with Marcin Zasepa

Welcome to the second in our new series, ‘in the zone’, a collection of conversations with CTO’s within the CTO Zone community. Each week we’ll be discussing the latest trends, insights gained from there experiences, and future predictions for their industry. This week we’d like to welcome Marcin Zasepa, CTO at Homegate AG in Switzerland. Every episode will be approximately 30 minutes

Read More »

In The Zone with Sasha Bilton

Welcome to the first in our new series, ‘in the zone’, a collection of conversations with CTO’s within the CTO Zone community. Each week we’ll be discussing the latest trends, insights gained from there experiences, and future predictions for their industry. This week we’d like to welcome Sasha Bilton. Every episode will be approximately 30 minutes long, and we aim

Read More »

Case Study: DAZN Data Engineering

Find out how 101 Ways helped DAZN improve their existing data warehouse as well as planning and setting the foundations of the new cloud-based data platform. Click here to download the full case study. Get in touch with a member of the 101 Ways team if you would like to discuss ways in which we can help you and your company

Read More »

Search the Blog

Agile Management Made Easy!

All About Agile

By Kelly Waters

“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. Allaboutagile.com is one of the most popular blogs about agile on the web. ”

Kelly Waters

Agile 101 is available to purchase. GAME ON!

Agile 101

Emma Hopkinson-Spark

“Whilst there are lots of ways you can vary the game depending on the teams you have and the learning outcomes you want, the basic flow of the game play is common to all.”
Emma Hopkinson-Spark

Why did we make the game?

How to play the game?

London

101 Ways Limited
41 Corsham Street
London
N1 6DR
United Kingdom

Manchester

101 Ways Limited
No.1 Spinningfields
Quay Street
Manchester
M3 3JE
United Kingdom

Amsterdam

101 Ways BV
Weesperstraat 61-105
1018 VN Amsterdam
Netherlands

Contact Us

If you would like to get in touch with one of the team at 101 Ways, then please fill out the form below or email us at contact-us@101ways.com.