AgilePM Fundamentals and the Agile Project Management Approach
AgilePM is built on the DSDM (Dynamic Systems Development Method) philosophy, and Foundation questions test whether you understand its underlying principles rather than memorising process steps.
The eight principles
Every AgilePM project is founded 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; demonstrate control. These are not optional good ideas - the framework states that if a project cannot apply all eight, it should not claim to be using AgilePM. A classic trap is being offered a plausible-sounding principle that is not one of the eight (for example, "maximise documentation" or "follow the plan rigidly"). Learn the exact wording.
Philosophy and the time/feature/cost trade-off
DSDM's philosophy is that "any project must be aligned to clearly defined strategic goals and focus upon early delivery of real benefits to the business." The central mechanism is fixing time and cost (and often quality) at the outset, while allowing the scope of a timebox to flex. Questions frequently test whether you know which variable is fixed and which is allowed to vary - the answer is that requirements are prioritised using MoSCoW and lower-priority work is sacrificed to protect the deadline.
The AgilePM lifecycle
You must be able to order the phases: Pre-Project, Feasibility, Foundations, Evolutionary Development (comprising Deployment and Engineering), and Post-Project. Traps include confusing Feasibility with Foundations (Foundations establishes the firm foundation and produces the business case and solution foundations) and forgetting that Evolutionary Development is the only phase that is repeated.
Rule of thumb: if a statement cannot be tied back to one of the eight principles or to the fix-time-flex-scope model, treat it with suspicion.