{'fraction_non_alphanumeric': 0.015719467956469165, 'fraction_numerical': 0.0, 'mean_word_length': 5.043795620437956, '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}}
Implementing and improving the SEI Risk Management method in a university software project

Although risk management approaches appeared more than one decade ago, there is the evidence of low penetration rate of their techniques in current software projects. One of the most widely known methods is the SEI Software Continuous Risk Management (SEI-CRM) method. This paper addresses the usage of the SEI-CRM method in a big university software development project. Moreover, the study we carried out suggests that SEI-CRM is limited in terms of the organizational risk perspective. This research is expected to contribute with the knowledge on risk management for software development projects by for which we propose to extend the SEI-CRM method with some organizational risk factors that we have found relevant from our study.