Agile

To estimate or not to estimate? That is the question.

Or is it?

It’s not so much the act of estimation that’s the issue. We accept that estimation can be a useful tool to help teams gain a shared understanding of a work item, and to break work down. It’s what we do with those estimates afterwards that matters. Other than the value to the team, the most common reason for doing any estimation is in an attempt to be predictable: we want to be predictable so that we can budget for projects, and provide our stakeholders with some understanding of the progress of those projects.

Continue reading