Document Controls
For Application Development & Delivery Professionals
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
 |
August 16, 2010 Case Study: Software Estimation Isn't Too Taxing For The IRS — How Can You Improve Your Return?by Mary Gerush with Mike Gilpin, Jeff Scott, David D'Silva |
|
This is an excerpt
Executive Summary
Estimating the true effort and cost of software development projects is tough. You have to understand your business, your technology, your resources, and the cost for each — generally with too little information to build a strong understanding. Unfortunately, there is no simple formula for producing a reliable estimate, because there are so many variables to consider. The IRS faced this dilemma, as most organizations do, and it took action: It initiated the creation of an estimation program office (EPO) to improve estimation in pursuit of making better investment decisions. The IRS succeeded by focusing on business needs, establishing support and knowledge, defining a relevant cost structure, implementing an estimation tool, and building stakeholder trust. Learn from the IRS's experiences, and you too can improve your software estimates.
Keywords
TABLE OF CONTENTS
- The Problem: Estimating Software Development Challenged The IRS
- Getting Started: The Estimation Program Office Got The Support It Needed
- Next Step: The EPO Moved Estimation From Textbook To The IRS Reality
- End Game: Transparent, Reliable Estimates Engender Continued Credibility
- The Next Stage: Make A Great Estimation Program Even Greater
RECOMMENDATIONS
- Want Better Estimates? Take A Step Back And Revise Your Approach
- Related Research Documents
This is an excerpt
Buy Risk-Free
Price: US $499
Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.
Already a Forrester Client?
Log in to read this document.
