Most methods of software sizing are based on software requirements and design documents, or on the source code itself.  For both new applications and enhancements this means that substantial funds will have been expended before sizing takes place. 

Many risks are proportional to software size.  As a result of delayed sizing, software project risk analysis usually occurs after development methods are locked in place.   When problems or risks are identified, it is often too late to introduce improved methods so the only options are staffing increases, unpaid overtime, or deferred functionality. Continue reading →