The default use of an “estimate-driven” approach is pervasive in software development efforts. While estimates can be useful, it is worthwhile to scrutinize our use of estimates, and to seek better ways to manage the development of software when estimates are not appropriate.
Let’s explore the purpose and use of estimates and consider possible alternatives. The default use of an “estimate-driven” approach is pervasive in software development efforts, and while estimates can be useful, it is worthwhile to scrutinize our use of estimates of cost, time, and effort, and to seek better ways to manage software development projects. We depend on estimates to make important decisions, and yet we’re often disappointed by the results. There are a number of things to explore and many questions to ask. For example, do we really need estimates for all the things we are currently using them? Are we getting a reasonable benefit from them? Is it possible to manage software development projects without these estimates, or at least with fewer estimates? Is there a way to prove that estimates are helping us make good decisions? Is it possible there are other ways to approach our work? In this workshop session we’ll participate in some interactive information gathering activities to see if we can gain a shared idea of our current understanding of the purpose and use of estimates. We’ll examine the nature of software development projects, and see if we can work together to come up with some ideas about alternatives to using estimates.
Video producer: https://www.agileonthebeach.co.uk/
Further reading: #NoEstimates – Alternative to Estimate-Driven Software Development