How Estimation Got Removed From Scrum
#NoEstimates and Scrum
Ask any Scrum practitioner about estimation and get ready for a spirited discussion. Given this, I find it curious why the Scrum Guide doesn’t mention the words estimate or estimation at all. What happened? And what does this mean?
In this article, I will show how estimates and estimation used to have a prime role in Scrum and how it (almost) completely vanished from the Scrum Guide.
Estimates in the 1st Scrum Guide — focus on output
The first Scrum Guide, published in 2010, discussed estimation left, right, and centre. The rules and tips were shaky at best. If you believe Scrum is about achieving your goals and creating value, then get ready to be shocked by what the 2010 Scrum Guide had to say about estimation.
Product Backlog items needed to have the following three attributes:
- A description
- A priority
- An estimate
This first Scrum Guide even informed us how to get better estimates:
“Better estimates are made based on the greater clarity and increased detail.” — Scrum Guide 2010
