AgilePM Practitioner study materials
AgilePM Practitioner study resources

AgilePM Practitioner: AgilePM Fundamentals and the Agile Project Management Approach

AgilePM Practitioner · Work through your exam, one topic at a time.

All guide sections

AgilePM Fundamentals and the Agile Project Management Approach

Core philosophy and framework

AgilePM is a method that combines the flexibility of agile with the governance of traditional project management. It is built on the DSDM (Dynamic Systems Development Method) philosophy, which rests on eight principles: focus on the business need, deliver on time, collaborate, never compromise quality, build incrementally from firm foundations, develop iteratively, communicate continuously and clearly, and demonstrate control. These principles guide behaviour and decision-making; they are not optional.

The AgilePM approach uses a lifecycle with distinct phases: Pre-Project, Feasibility, Foundations, Evolutionary Development, Deployment, and Post-Project. Each phase has specific objectives and products. The Evolutionary Development phase is where the majority of work happens, using timeboxes (iterations) to build the solution incrementally.

A key concept is the timebox: a fixed period (typically 2–4 weeks) during which a defined set of work must be completed. Timeboxes are never extended; instead, scope is flexed to fit the time. This ensures predictability and control. Another fundamental is the MoSCoW prioritisation (Must have, Should have, Could have, Won't have this time). Musts should not exceed 60% of the effort to allow contingency.

Traps and worked example

Candidates often confuse AgilePM with other agile methods like Scrum. AgilePM is broader and includes roles, products, and practices not found in Scrum. Also, remember that the business need drives everything; if the business case is not viable, the project should be stopped.

Worked example: In a timebox, if work is running late, the correct action is to reduce the scope by dropping the lowest-priority (Could have) requirements, not to extend the timebox. This maintains the principle of delivering on time.

Rule of thumb: If a question asks about handling change, the answer should align with agile principles: embrace change, but keep it controlled through prioritisation and timeboxing.