Don’t do estimates

by Feb 8, 2023

I hear some people on social media saying: ‘Estimates are useless. Don’t do it!’

Claiming you can’t predict the future. That there are too many variables in software development and that it isn’t agile to estimate. We can’t take short cuts on proper code and good solutions.

But the thing is when you have years of experience, you should be able to give a ballpark estimate how long something will take. There are a lot of creative professions that also have a lot of variables in their work, and they can do it because of their experience.

When doing agile, the idea is to make small increments. So, the work should already be sliced into decent small units of work, which don’t need to be estimated, because they are kind of the same size.

And then the idea that all code or solutions need to be the holy grail: They don’t. Depending on the context and the budget we are getting, the delivered solution can be quite different.

What can you do with a budget of €1000? What about a budget of €10.000 or €100.000? I think the solutions would be completely different for the same problem.

Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more