Software Estimation Without Guessing

Software Estimation Without Guessing
Author :
Publisher : Pragmatic Bookshelf
Total Pages : 308
Release :
ISBN-10 : 9781680507416
ISBN-13 : 1680507419
Rating : 4/5 (419 Downloads)

Book Synopsis Software Estimation Without Guessing by : George Dinwiddie

Download or read book Software Estimation Without Guessing written by George Dinwiddie and published by Pragmatic Bookshelf. This book was released on 2019-12-19 with total page 308 pages. Available in PDF, EPUB and Kindle. Book excerpt: 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. What You Need: No software needed, just your past experience and concern for the outcomes.


Software Estimation Without Guessing Related Books

Software Estimation Without Guessing
Language: en
Pages: 308
Authors: George Dinwiddie
Categories: Computers
Type: BOOK - Published: 2019-12-19 - Publisher: Pragmatic Bookshelf

GET EBOOK

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 m
Software Estimation
Language: en
Pages: 466
Authors: Steve McConnell
Categories: Computers
Type: BOOK - Published: 2006-02-22 - Publisher: Microsoft Press

GET EBOOK

Often referred to as the “black art” because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. In fact
#NoEstimates
Language: en
Pages: 180
Authors: Vasco Duarte
Categories:
Type: BOOK - Published: 2015-09-15 - Publisher:

GET EBOOK

How to always be on time, and not risk missing important deadlines or go over budget This book is the result of many years of hard work, and plenty of lessons l
Competing with Unicorns
Language: en
Pages: 186
Authors: Jonathan Rasmusson
Categories: Computers
Type: BOOK - Published: 2020-03-16 - Publisher: Pragmatic Bookshelf

GET EBOOK

Today's tech unicorns develop software differently. They've developed a way of working that lets them scale like an enterprise while working like a startup. The
Making Software
Language: en
Pages: 624
Authors: Andy Oram
Categories: Computers
Type: BOOK - Published: 2010-10-14 - Publisher: "O'Reilly Media, Inc."

GET EBOOK

Many claims are made about how certain tools, technologies, and practices improve software development. But which claims are verifiable, and which are merely wi