{'fraction_non_alphanumeric': 0.03398926654740608, 'fraction_numerical': 0.0, 'mean_word_length': 5.781818181818182, '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}}
Complex project as a knowledge process: Conceptualisations and examples: Applying rethinking project management (RPM) in software-intensive CoPS

Software (SW) and Information Technology (IT) has frequently used in ‘Complex Products and Systems’ (CoPS) and ways of handling projects. This study has identified three dominant conceptualisations to narrow down the ‘Rethinking Project Management (RPM)’ theory — projects as a knowledge process. Firstly, there is a similar characteristic of managing CoPS and Knowledge-Intensive Firm (KIF), which give an opportunity to propose a new model based on the ‘enabling context’. Secondly, managing CoPS fall under the umbrella of ‘craft’ — more about exploration and less about exploitation. This finding lead to the third conceptualisation that the primary knowledge processes occurred in CoPS development is all about knowledge creation and knowledge integration. Furthermore, the most prominent enabling context in managing software-intensive projects are the shared perspective, which connected closely with the availability of both boundary spanner and a boundary object.