{'fraction_non_alphanumeric': 0.016646848989298454, 'fraction_numerical': 0.0023781212841854932, 'mean_word_length': 5.682539682539683, '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}}
Laying out the scope of developers' risk management responsibilities

Most of the standards and process models are not explicit enough about identifying risk management responsibilities of developers. Usually, they do not identify them at all. In this paper, we identify the risk management responsibilities of developers within 53 software companies. Our goal is to find out what exactly developers do within pre-project and project phases such as requirements management, project and task planning and what risk management responsibilities they have within these phases. Our results show that the responsibility portfolio of developers varies depending on the degree of their engagement within pre-project and project phases; the broader the developers' responsibility portfolio, the broader their risk management responsibility portfolio.