“Software Estimation Without Guessing” by George Dinwiddie
There is a love-hate relationship around estimations. So for this months podcast, our hosts chose the book Software Estimation Without Guessing by George Dinwiddie.
It not only reveals 732 questions, but also the whole point of estimating – which is to start a conversation. It doesn’t matter if you follow the #no-estimation movement or estimate on a daily basis, check out our book review! There were some wonderful takeaways, that will serve you all.
In the second part of this podcast, our hosts have prepared a list of questions for the author. George joins them with answers and some insights about the book.
About the book
Estimating software development often produces more angst than value, but it doesn’t have to. Identify the needs behind estimate requests and determine how to meet those needs simply and easily. Choose estimation techniques based on current needs and available information, gaining benefit while reducing cost and effort. Detect bad assumptions that might sink your project if you don’t adjust your plans. Discover what to do when an estimate is wrong, how to recover, and how to use that knowledge for future planning. Learn to communicate about estimates in a healthy and productive way, maximizing advantage to the organization and minimizing damage to the people.
In a world where most developers hate estimation and most managers fear disappointment with the results, there is hope for both. It requires giving up some widely held misconceptions. Let go of the notion that “an estimate is an estimate” and estimate for the particular need you, and your organization, have. Realize that estimates have a limited shelf-life, and reestimate frequently if it’s important. When reality differs from your estimate, don’t lament; mine that disappointment for the gold that can be the longer-term jackpot.
Estimate in comparison to past experience, by modeling the work mathematically, or a hybrid of both. Learn strategies for effective decomposition of work and aspects of the work that likely affect your estimates. Hedge your bets by comparing the results of different approaches. Find out what to do when an estimate proves wrong. And they will. They’re estimates, after all. You’ll discover that you can use estimates to warn you of danger so you can take appropriate action in time. Learn some crucial techniques to understand and communicate with those who need to understand.
Address both the technical and sociological aspects of estimation, and you’ll help your organization achieve its desired goals with less drama and more benefit.
About the author
George Dinwiddie is a Software Development Consultant and Coach who helps organizations develop software more effectively. He helps organizations, managers, and teams solve the problems they face by providing consulting, coaching, mentoring and training at the organizational, process, team, interpersonal, and technical levels. Involved in the Agile community since 2000, he has helped organizations ranging from a 6-person startup to a Fortune 100 company and a billion-plus dollar federal program, either directly or in partnership with other companies.
