Forrester: - Making Leaders Successful Every Day |
Search Forrester.com |
|||||||||||
Global Navigation
Local Navigation |
||||||||||||
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
|
July 27, 2009 Software Size Matters, And You Should Measure ItFind The Right Software-Sizing Technique For Your Development Organizationby Mary Gerush, Dave West with Mike Gilpin, David D'Silva, Justinas Sileikis, Wallis Yu |
Average: 8
(2 ratings)
|
This is an excerpt
It is critical for application development professionals to be able to effectively and objectively answer the question "how big is your software project?" in order to provide effective metrics, improve estimation practices, target improvement initiatives, and refine governance and architectural processes. Yet too few organizations measure software or project size in a consistent and structured way; most instead rely on subjective approaches to provide comparison and context. Practitioners argue that traditional sizing techniques are too complex and add overhead. But sizing does not have to be complex. Forrester increasingly sees effective organizations introducing pragmatic sizing approaches that quantify size early in the development process and then applying that information to development measures such as progress, quality, and stability. For these organizations, size provides a currency that enables effective discussions on cost, value, and productivity.
This is an excerpt
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.
Application Development, Application Development Metrics & Benchmarks, Application Development Processes & Tools