PRINCE2 Agile Foundation study guide
PRINCE2 Agile Foundation · Work through your exam, one topic at a time.
PRINCE2 Agile Foundation is an entry-level certification in the PRINCE2 family of project management credentials offered by Peoplecert. Where classic PRINCE2 provides a structured, principle-based governance framework for projects, PRINCE2 Agile is aimed at people who need to combine that structure with agile ways of working - so that delivery teams can iterate and respond to change while the wider organisation retains clear roles, controls and decision points. The PRINCE2 Agile Foundation study guide has 5 sections and about 1,524 words.
01Agile concepts and why they are used
Agile is a way of working suited to complexity and uncertainty. PRINCE2 Agile draws directly on the Agile Manifesto's four value statements (individuals and interactions over processes and tools; working products over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan) and insists that the items on the right still matter - the values describe relative priority, not replacement.
322 words, about 2 min02The PRINCE2 Agile approach: blending PRINCE2 with agile
PRINCE2 Agile is PRINCE2 tailored for agile delivery . PRINCE2 supplies direction, accountability, boundaries and justification - the 'what' and 'why'.
302 words, about 2 min03Agile ways of working, frameworks and techniques
Scrum has three roles (Product Owner, Scrum Master, Development Team), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) and three artefacts (Product Backlog, Sprint Backlog, Increment). Its theory is empirical: transparency, inspection, adaptation.
285 words, about 1 min04Applying the PRINCE2 principles, themes and processes in an agile context
The seven principles are applied through agile behaviour: 'learn from experience' becomes retrospectives and reviews; 'focus on products' becomes the definition of done and acceptance criteria; 'tailor to suit the project environment' is exactly what the Agilometer informs; 'manage by stages' still means stage boundaries and continued business justification at each one. Theme tailoring in brief: business case - value is defined by the customer, kept light and reviewed frequently, with early delivery realising benefits sooner; organization - project board, project manager, team manager and delivery team, with roles such as Product Owner allocated to the right people; quality - acceptance criteria, definition of done and quality tolerances rather than heavy product descriptions; plans - a high-level project plan plus release plans and sprint/team plans, planned in rolling waves; risk - risk appetite set by the board, with frequent delivery and transparency reducing exposure; change - change is expected, handled through the backlog with delegated authority and a change budget; progress - measured by delivered, working products and burn charts rather than percentage complete.
320 words, about 2 min05Agile behaviours, the focus areas and the Agilometer
PRINCE2 Agile expects behaviours as well as techniques: transparency (make work and problems visible), collaboration (across the delivery team and with the project board), rich communication (face-to-face, visual, osmotic, co-located where possible), self-organisation (the team decides how), and exploration (discover through doing). These apply to the board as much as to the team.
295 words, about 1 min