When I want to paint a wall and I have hired a painter, the first question I want to ask the painter is about estimates in Time & Cost. Because that is a parameter which makes me to either dive into the project or not. I want to be certain about the cost and time I will have to bear.
I consider that as a part of human curiosity and I have given myself a good excuse to ask such question. Same curiosity applies to any industry including our lovely software industry or IT industry in general.
As an investor I want to know when I will be able to deliver the product to my end users or customers.
Why Estimates Fail?
19% due to tools,
37% related to process issues, and
44% related to behaviour issues.
Nolan of Rolls Royce and published by INCOSE
At least we have established that estimates are helpful when it comes to knowing the Time & Cost. After all I don’t want to pay a lot and see my painted wall after waiting for long time.
We know that at least 90% of our Estimates always fail.
How do we better estimate or lets say no estimates 😊
Estimates are prone to failure and it should only be considered as a reference point but we cannot say that is a hardline to deliver a value to customer. Our customer does not care if I spent the whole day fixing a bug. The important thing is whether they can run a system bug free at the end of the day that matters.
Doing agile , lean are great however if we are forgetting the core of why we do agile in the first place then there is something wrong.
Customer Collaboration Over Contract Negotiation.