^ [[3 PM2-Agile – Overview]] # 3.1 PM2-Agile Principles To help people gain a better understanding of what Agile software development is all about, the seventeen authors of the **Agile Manifesto** described what they mean by "Agile" in 12 principles. PM2-Agile has adopted – with **some modifications** – these principles. The 12 principles of PM2-Agile: - The highest priority is to **satisfy the client** through early and **continuous delivery of valuable solutions**. - **Changes** in requirements **are welcome**. - Deliver value frequently through **working solutions**. - Business people and the [[Project Core Team (PCT)]] must **work together** throughout the project. - Create teams with **motivated individuals**. Give them the environment and support they need to **self-organise**, and **trust them** to get the job done. - The most efficient and effective method of communication is **face-to-face conversation**. - The primary **measure of progress** is the value and **use of what has been delivered**. - Continuous attention to **quality**. - **Simplicity** – the art of maximising the amount of work not done – is essential. - At regular intervals, the team reflects on how to **improve**, then tunes and adjusts its behaviour accordingly. - Agile processes promote **sustainable development**. The Project Team should be able to maintain a **constant pace** indefinitely. - Agile practices should **be enterprise-aware by considering IT governance, enterprise architecture, and interoperability requirements**. Agile teams should be able to collaborate effectively with teams and stakeholders following alternative approaches. You can read more about the PM2-Agile Principles in [[Appendix B - Additional Resources]]. Next: [[3.2 Agile & PM2]]