### 6.5.1 Project Manager (PM) In the context of PM2, the Project Manager (PM) has several different **responsibilities**, which includes, **among others**, the following: - Methodology compliance - Team and progress management - Managing stakeholders’ expectations The extended governance model defined by **PM2-Agile identifies a set of new roles** that will take on some responsibilities usually assigned to the Project Manager (PM). **Methodology Compliance** ==In the context of PM2==, one of the Project Manager’s responsibilities is to **actively encourage and educate the Project Core Team (PCT) on the proper usage of the methodology**, as described in the **Project Handbook**. ==When PM2-Agile is incorporated==, this **responsibility is shared with the Team Coordinator (TeCo)**, who will guarantee that all aspects related with agile values and principles are followed according to what is described in the Development Handbook. For example, the **Team Coordinator (TeCo) is responsible** for facilitating and assuring that the team properly conducts the **agreed agile ceremonies (Iteration Planning, Review, Retrospective)**. The Project Manager ==(PM) participates in these ceremonies as a regular Agile Team Member (ATeM), while the Team Coordinator (TeCo) should be facilitating==. **Team and Progress Management** ==PM2== defines the Project Manager (PM) responsible for **ensuring the efficient usage of resources**. He/she assigns and monitors the work of each team member until the work is complete. ==When Introducing PM2-Agile==, the Agile principles of self-organising team and decentralised decision-making hold the Agile Project Core Team (A-PCT) responsible for managing its work (as described in the Development Work Plan). This approach allows the **Project Manager (PM) to focus on the problems and impediments** identified by the Agile Project Core Team (A-PCT) via the Team Coordinator (TeCo). **Managing Business Stakeholders Expectations** ==With PM2-Agile==, the **new Product Owner’s (PrOw) role becomes the permanent point of contact between the requester and provider organisations**. Regarding the scope of the solution and the corresponding time frame, he/she is ==responsible for aligning all expectations in collaboration with the Agile Project Core Team (A-PCT), the Business Manager (BM) and Business Implementation Group (BIG)==. **The Project Manager (PM), together with the Business Manager (BM)**, may need to **intervene** when the expectations are not aligned or the Product Owner (PrOw) and the rest of the Agile Project Core Team (A- PCT) cannot come to a **consensus**.