Software process and early project planning: issues, insights and lessons learned

Abstract

A matured software process is important, particularly for large or long-lived systems. It can help to ensure quality and reduce maintenance cost. Software processes based upon software engineering institute capability maturity model will head off many problems and lead to efficient, steady-state development. However, the business acquisition phase omits many important process considerations. When this happens, it is hard to reverse and virtually impossible to optimize the eventual contract and process. Several categories of breakdown can occur in such areas as communication, coordination, timely execution, training, capital planning and procurement, and roles and role transitions. These can be considered as management challenges, and are solvable. This paper contains examples of problems arising, and presents some ideas on an enlightened business acquisition model that avoids process problems during program execution.