To Estimate Or #NoEstimate, That Is The Question by Gil Zilberfeld
To Estimate Or #NoEstimate, That Is The Question
From the early days of agile, there were discussion on how to do estimations “right”. Although there’s no real mentioning them in the agile manifesto, scrum and other methodologies have put effort into this topic because there seems a need for estimations.
What makes an estimation method work? And what will happen one day if we stop estimating?
In this talk, I’m going to discuss where estimation works, what we do with estimations and if that’s the only way to do it. We’ll talk about how our experience and biases control them, and how the #NoEstimates discussion tries to change the way we make decisions.
Finally, we're going to discuss what other methods we can use instead (or in parallel to estimations)/
The next time people ask us for estimations, let’s consider the process first. Then we’ll give them a better answer.
Why do we want estimates
We really want better decisons
Why estimates can be misused
Why we're really bad at it
Practices for better planning (unknowns, complexity, cost of delay, using team data, reducing variance)
What is #NoEstimates, and who's behind it
|Constraints and Class Arrangement||
Will be given at Agile Practitioners 2015, Jan-15.
|Last Updated||04 Jan 10:34|