David Rodenas PhD
1 min readAug 12, 2024

--

I really appreciate your contribution, but I still feel like something is missing. One of the main reasons for claiming that asking for estimates is a telltale sign is that the development team should be more closely integrated with the rest of the business. In fact, they shouldn’t be a separate team. Breaking down tasks more is correct, but it should be done with the right criteria; it should be done in a way that allows each step to be tested. In other words, instead of breaking down at a technical level, break down at a business level. So, that's something that developers cannot do alone. At this point, the use of decomposition subtly changes from an estimation tool because the priority becomes delivering what brings the most value first and as quickly as possible. This way, we can correct the course or refine even better as quickly as possible.

This approach provides much more value than any planning or estimation done separately. The difference is so significant that asking for estimates is a telltale sign because it likely means a lot of valuable capacity is being thrown away.

What do you think? Instead of keeping business and development separate, why not make them cooperate?

--

--

David Rodenas PhD
David Rodenas PhD

Written by David Rodenas PhD

Passionate software engineer & storyteller. Sharing knowledge to advance our skills. Join me on a journey of discovery in the world of software engineering.

Responses (1)