Maintaining an Improvement Programme


Why is it Necessary?

Software Process Improvement (SPI) is an iterative process. In order to capitalise on the investment it is important to ensure that each iteration's improvements are sustained at the new level of performance and continuous improvement is embedded as a key organisational value adopted by all.

How does it Work?

Once initiated, maintenance of the programme must be continuous, involving all members of the organisation working as a team, being led by the stakeholders. During planning (see Starting an Improvement Programme) three key drivers (Monitoring, Review and Support) should have been addressed.

Monitoring Processes and Performance

Measurements must be taken to monitor the processes and performance. These must then be analysed for compliance with the plan and to identify trends or discrepancies. The results of the measurement and anlysis are then fed into the review process.

Review Processes and Improvements

The measurements and analysis are reviewed to see if the improvements are working effectively. Any trends or discrepancies that show deviation from the plan should be further analysed and the results should be fed into the next planning cycle.

Support, Education and Training

On-going support must be provided through education, training and consultancy (whether from stakeholders or external suppliers) in the new processes, tools and skills.

GIFPA Ltd. 2016

Copyright 2016

All Trademarks Acknowledged

Applying Software Metrics
Assessing Capability     
Estimating and Risk       
Improving Processes     
Measuring Performance
Tools and Techniques   
About GIFPA         
Copyright & Legal