{'fraction_non_alphanumeric': 0.025665399239543727, 'fraction_numerical': 0.0076045627376425855, 'mean_word_length': 5.622641509433962, '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}}
10.1.1 Managing the Project Team as a Special Class of Stakeholder for Enterprise Transformation Projects

The Los Alamos National Laboratory's (LANL's) Enterprise Project – the implementation of a commercial off‐the‐shelf (COTS) enterprise resource planning (ERP) system to replace the home‐grown business computing systems in use since the early 1980's – provides a provocative case study regarding the management of project teams in which team members are, themselves, stakeholders. This paper describes the project's approach to stakeholder management for the project team, which had mixed success, discusses the theoretical underpinnings of the approaches used, and provides lessons learned for handling project team members as a special class of stakeholders who have special needs. Specifically, it is noted that project team members may be either system advocates or system critics or adversaries. It is recommended that transition management tactics be developed in anticipation of both types of stakeholders being present on the project team.