DEV Community

Discussion on: Estimation is not impossible

Collapse
 
scottshipp profile image
scottshipp

I agree. I think that when the estimation relates to "When can we release this feature to customers?" but there's no other contingency on it than that, it really makes it difficult to find a compelling reason why you would need an estimate. Generally, you would think that what truly matters is exactly what you said: what has the highest business value?

There are a few times I have seen teams trying to coordinate with each other and communicate with various stakeholders where the estimate is meaningful as far as allocating resources and ordering work at the layer above. Think of a situation where a team is needed to support the efforts of several other teams, and thus they want to know if team A will need them only three weeks or six weeks, because team B will need them in three weeks.

A lot of the time such situations can be avoided if teams are self-sufficient, but in reality there are situations where that is not possible, e.g. when you are resource-constrained and trying to work lean.