Tag: absolute estimation
Agile estimating 4/4: Kanban approach to estimating
Now I also promised you a second option of using a range of numbers instead of one number. This is something we use in a typical kanban implementation. I’ll explain how we would go about it. In kanban we would start by collecting historical data. Using this data we can discover several types of work that have significantly different cycle times, time to complete a...
Agile estimating 3/4: Measurement of an estimate
Now why haven’t I talked about time in the previous chapter? Because using time for our estimates is very dangerous. When you ask someone how long something is going to take and they say 1 hour, your initial reaction is to expect it to be done the next hour. It’s not because we are egotistical or evil. Again, it’s just how the human brain works....
Agile estimating 2/4: Absolute versus relative estimates
When you think about it, people always ask for absolute estimates. How long is it going to take to fix my car, when can I have it? And they are not happy when you say between 1-4 hours or 2-3 weeks. They need one absolute number, and some don’t even care if it’s right or wrong. They just need that number or date or timing....
Agile estimating 1/4: Ideal versus elapsed time measurement
Why is it that people always think they can estimate the time it will take to finish some amount of work using this wondrous concept of ideal time? Hey, I’m not saying I never do that, I’m one of those people doing just that. What do we think this ideal time consists of? I like the example of a typical NBA match. Ever watched the...