Also known as "The Pizza Principle".
The relationship between a developer and estimations is simple and crucial. Estimation is a skill; like any skill, it needs sharpening. It takes time to serve it right.
Imagine you're ordering a pizza - the delivery estimate is 50 minutes. It shows up 30 minutes late. You're annoyed, and still hungry. Now, imagine if the estimate was 50 minutes, but it arrived in 30. You're thrilled. Same pizza, different expectations.
When you estimate, it's better to allow a buffer for the unexpected. But move fast. Estimate a bit longer and deliver early โ that builds trust. Stakeholders don't just appreciate it, they remember it. It's how you build a reputation for getting the job done.
Consistently beat your estimates.
If this resonates with you, discover more on my blog!
Top comments (2)
Estimates are a complete waste of time. I stopped doing them many years ago
Maybe... While some find estimates unnecessary, they can help set expectations, build trust, and provide a foundation for planning. What's a plan without a timeline?