{'fraction_non_alphanumeric': 0.010914051841746248, 'fraction_numerical': 0.0, 'mean_word_length': 5.016393442622951, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Software process improvement strategy

Software Process Improvement (SPI) has been around within the software industry for a while. Many organisations have been practicing SPI following different appraisal models focusing on different maturity levels aiming to change the practice of their software work. Getting success in SPI has shown to be a difficult challenge for many organisations. This paper argues that an SPI effort should be viewed as a change programme rather than a process improvement effort. In this way one important aspect in succeeding in making change happen in reality is having a clear SPI Strategy. This paper describes what strategy means in the light of SPI and what an effective SPI strategy should address.