Software controlling

Abstract

The development of large scale software systems requires an effective and efficient project management. In particular, it is necessary to integrate goal oriented risk management for software quality into the development process. The typical "classical" project controlling approachmainly focuses on reaching the required external quality properties of the final product (e.g. the satisfaction of functional requirements) and compliance with schedule and budget. The experience from many long running projects shows that it is necessary to take a more detailed and comprehensive look at the quality of software documents and intermediate development products in order to spot quality related project risks early and to take appropriate action in the development process. At Capgemini sd&m (Munich) currently a comprehensive set of technical and organisational measures for a holistic quality oriented risk management is being introduced as standard elements of the development processes. Essential components of the approach are (1) a quality model based on key performance indicators fromcompleted projects, which combines internal product properties with effort, test, and defect data, (2) a project control board integrated with the development environments, and (3) specific KPI-based process elements for quality and risk assessment. © 2008 Springer-Verlag.