The Agile community has been arguing about whether estimates are a good idea or not for a while now. In this talk at Øredev in November 2015, I think I did a pretty good job of threading the needle. I talk about how and when to estimate, and why you might not want to.
Estimates or No Estimates?
There’s a debate raging in the Agile world: should we estimate, or not? Lost in the noise are more important questions: When should we estimate, and why? When should we not estimate, and why not?
As with so many Agile questions, the answer to “should we estimate?” isn’t a clear-cut “yes” or “no.” Instead, the answer depends on what your team is capable of, what your organization needs, and how to best balance the two.
We’ll take a deep look at how estimates work, why they work, and when and why to discard them. Along the way, we’ll encounter surprising insights about the nature of Agile development and the teams that use it.