Book Details

Synopsis

Budget and cost overruns in systems development are the rule rather than the exception. Although managers can answer questions like what requirement or what design is needed, they cannot adequately tell how much time, how much money, or how much risk is involved.

Controlling Software Projects shows managers how to organize software projects so they are objectively measureable, and prescribes techniques for making early and accurate projections of time and cost to deliver. To replace the traditional wet-finger-in-the-air kind of estimating, the author argues for a set of function metrics: quantifiable indications of system size and complexity derived directly from the requirement. He presents a scheme for collection and use of such metrics to project results and track progress toward completion.