^ [[3 PM2-Agile – Overview]] # 3.3 The PM2-Agile Model PM2-Agile is not a new Agile philosophy or approach. **PM2-Agile simply tailors proven Agile and Lean practices and connects them to PM2**. PM2-Agile allows Agile teams to **remain aligned with PM2** Project Management Methodology by enabling them to **apply Agile values and principles** and maintain enterprise awareness and compliance at the overall project level. PM2-Agile is connected to Project Management, Software Engineering and the other Enterprise Practices (e.g. Portfolio Management, Programme Management, IT operations etc.). ![[3.3 The positioning of PM2-Agile within the Organisation environment.png]] Among the advantages over other popular standard Project Management methodologies, PM2 consciously enables ‘agility’ (i.e. the PM2 processes and mindsets are aligned with the Agile philosophy) and interlinks with the rest of an organisation’s management structures and processes. Though PM2-Agile is not a software engineering library, it does include some optional techniques such as Test-Driven Development, Pairing, etc. However, since it is **used primarily for software development, PM2-Agile is well-integrated with software engineering practices**. Agile advocates self-organising teams. PM2 provides the appropriate governance framework, which reflects the governance needs of the organisation as a whole, but also enables the Project Core Teams (PCT) to harness the benefits of self-organisation. For this purpose, **PM2-Agile organises Project Core Team (PCT) members who work in an Agile way**. Figure below shows how **PM2-Agile teams fit into the overall project organisation** ![[3.3 Agile Teams in the context of the PM2 project organisation.png]] A set of roles and responsibilities is set out for the Agile team (see section 6, “Roles and Responsibilities”). Next: - [[3.3.1 Lifecycle]] | [[3.3.2 Iterations]] | [[3.3.3 Releases]] - [[3.4 The PM2-Agile Mindsets]]