{'fraction_non_alphanumeric': 0.02102376599634369, 'fraction_numerical': 0.0009140767824497258, 'mean_word_length': 4.6735751295336785, '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}}
The Role of the Project Manager in the Agile Methodology

The role of the Project Manager was well defined by the PMBOK [1] before the introduction of the Agile approach to R & D organizations. The basic assumption of this study is that the development methodology in the organization, being the traditional Waterfall or Agile, impacts the role of the PM. Therefore, this research is looking to prove how the functioning of a PM in Agile has changed from the functioning of the traditional PM is functioning. In the literature survey, we encountered new management roles in the agile world, that didn't exist before: The Scrum Master (team lead in Agile) and the Agile coach (a function that is meant to help the organization define new agile processes and assimilate the agile methodology). Based on the literature review, we formulated our research hypotheses about an overlap between these functions and the PM role in agile. It was found that agile reduces the importance of the PM role, causing a reduction in control and quality and less commitment to him, since he is not a scrum master.