The Agile Daily Standup - AgileDad

Being Too Precise Hurts Your Plans - Mike Cohn

Aug 15, 2024

Mike Cohn, an expert in agile methodologies, discusses the dangers of the precision trap in project planning. He illustrates how overly specific estimates can mislead teams and create unnecessary pressure. Using relatable examples, Cohn advocates for prioritizing accuracy over precision, suggesting that rounded estimates foster better understanding and satisfaction among stakeholders. With a nod to real-world scenarios, he emphasizes the importance of flexibility in estimation to enhance project effectiveness.

05:22

Creator website

Episode guests

Mike Cohn

AI Summary

AI Chapters

Episode notes

Podcast summary created with Snipd AI

Quick takeaways

Over-reliance on precise estimates, like 6.66 sprints, creates confusion and impacts effective planning in project management.

Emphasizing ranges over exact figures, such as shipping in approximately seven months, fosters better stakeholder relationships and realistic expectations.

Deep dives

The Precision Trap in Estimation

Relying on overly precise estimates can lead to the 'precision trap,' which makes planning ineffective. For instance, calculating project timelines down to decimals, like 6.66 sprints for a task, may seem intelligent but can create unnecessary confusion and inaccuracies. Instead of focusing on precise numbers, it's more effective to present estimates as ranges, such as six to eight sprints, which provide a clearer picture of project timelines. This shift in perspective emphasizes the importance of accuracy over precision in delivering expectations to stakeholders.

Navigating the Precision Trap in Project Estimation

5min

Being Too Precise Hurts Your Plans - Mike Cohn

I need a new backup drive. I don’t need a 40 TB drive but the site I buy from listed one available. I thought I might as well click on it to see the price.
The price seemed reasonable for that much storage, but what caught my attention is that the drive ships in 205 days.
Seriously, what are they thinking? How can they possibly know the drive will ship in 205 days, not 204 or 206?
This website fell into what I call the precision trap, which is applying a false level of precision to some estimate or plan. We often fall into the precision trap because of the math involved in planning.
Let me clarify this with an example. Suppose a team has estimated that it needs to deliver 100 story points of work to achieve some objective. They’ve already calculated their velocity to be 15. Someone on the team does the simple math of 100 divided by 15 and gets 6.66. Team members then proclaim that they will be done in 6.66 sprints. Or hopefully someone decides to round that up and say it will take 7 sprints.
But math like this leads to the precision trap. You can see from this how the website decided the drive would ship in 205 days.The precision trap persists because we seem wired to like precision. It feels good to say we’ll be done in 6.66 sprints. We must be really smart to know that.
But we need to favor being accurate over being precise. Accuracy is about being right. The easiest way to be right is to be less precise.
For example, that website could have told me the drive would ship in “about 7 or 8 months.” That would have been enough precision for me to decide whether to buy it.
When math tells a team they can deliver in 6.66 sprints, that is very precise. But it’s probably not very accurate. Just like the ship date of the hard drive, that estimate should be conveyed as a range. Instead of 6.66 sprints, maybe it’s 6 to 9 sprints or even 7 to 10 sprints.
Avoid falling into the precision trap if you want to succeed with agile

How to connect with AgileDad:

- [website] https://www.agiledad.com/

- [instagram] https://www.instagram.com/agile_coach/

- [facebook] https://www.facebook.com/RealAgileDad/

- [Linkedin] https://www.linkedin.com/in/leehenson/