PRINCE2 Agile Foundation (Version 2) Study Plan
A practical timed study plan for the PeopleCert PRINCE2 Agile Foundation (Version 2) exam, with 7-day, 14-day, 30-day, and 60/90-day paths.
How to use this Study Plan
This Study Plan is for candidates preparing for the PeopleCert PRINCE2 Agile Foundation (Version 2) exam, exam code PRINCE2 Agile Foundation.
Use it to turn your available time into a realistic preparation schedule. The plan is independent study guidance, not an official PeopleCert resource. Use the current PeopleCert syllabus, official course materials, and exam instructions as your source of truth.
The goal is to move from recognition of terms into exam-ready judgment:
- How PRINCE2 governance works with agile delivery.
- How roles, responsibilities, products, practices, and processes are adapted.
- How agile concepts such as iterative delivery, collaboration, transparency, and frequent feedback fit within a project environment.
- How to answer scenario-style questions without overthinking them.
Which plan should you use?
| Time until exam | Best if you… | Daily study target | Main risk | Primary focus |
|---|---|---|---|---|
| 7 days | Have already studied and need final review | 2 to 3 hours | Trying to learn everything from scratch | Diagnostic practice, weak-area repair, timed mocks |
| 14 days | Know some PRINCE2 or agile concepts but need structure | 90 to 150 minutes | Staying too theoretical | Focused content review plus mixed practice |
| 30 days | Are starting a serious first pass | 60 to 120 minutes | Delaying practice too long | Balanced concept review, scenario practice, mocks |
| 60 days | Are new to PRINCE2 Agile or studying around work | 45 to 90 minutes | Forgetting early topics | Spaced review, weekly practice, mock progression |
| 90 days | Need a low-pressure plan or have limited weekly time | 30 to 60 minutes | Going too slowly without testing | Gradual topic build, recurring recall, staged mocks |
If you have fewer than 14 days, do not aim for perfect notes. Aim for accurate terminology, reliable process flow, and the ability to explain why each practice answer is right or wrong.
What to study for PRINCE2 Agile Foundation (Version 2)
The exam is not just “PRINCE2 plus agile vocabulary.” Study how the two work together: PRINCE2 provides project governance and control, while agile ways of working support delivery, feedback, collaboration, and adaptability.
The study-time mix below is a planning guide, not an official exam weighting.
| Study area | Suggested time share | What you should be able to do |
|---|---|---|
| PRINCE2 governance and structure | 25% | Explain roles, decision points, control, escalation, business justification, progress, and project governance. |
| Agile concepts and ways of working | 25% | Recognize agile principles, behaviours, iterative delivery, prioritization, collaboration, feedback, and common agile approaches referenced in your materials. |
| PRINCE2 Agile tailoring | 30% | Decide how PRINCE2 roles, practices, processes, management products, tolerances, and reporting can be adapted in agile environments. |
| Scenario judgment | 15% | Choose the best answer when a question mixes stakeholder pressure, delivery uncertainty, change, risk, quality, value, or governance. |
| Exam technique | 5% | Manage time, avoid distractors, and review missed questions efficiently. |
Core knowledge map
Build one page of notes around these headings:
| Heading | Questions your notes should answer |
|---|---|
| Purpose of PRINCE2 Agile | Why combine PRINCE2 with agile ways of working? What problem does the combination solve? |
| Governance | Who makes decisions? Who escalates? What controls remain important even when delivery is agile? |
| Roles and responsibilities | How do project-level roles interact with delivery-level agile roles and teams? |
| Delivery approach | What changes when work is iterative, incremental, collaborative, and feedback-driven? |
| Tailoring | What can be adjusted, simplified, or made more frequent without losing control? |
| Time, cost, quality, scope, risk, and benefits/value | Which aspects are controlled, protected, flexed, or negotiated in a PRINCE2 Agile context? |
| Stakeholders and communication | How are transparency, rich communication, collaboration, and frequent feedback used? |
| Risk, change, and quality | How do agile practices help reveal risk, manage change, and protect fitness for purpose? |
| Predictive, agile, and hybrid judgment | When is stronger upfront planning useful? When is agile delivery more appropriate? How are they blended? |
Daily practice rhythm
Use the same rhythm most days. The exact content changes, but the structure should stay consistent.
| Available time | Study rhythm |
|---|---|
| 45 minutes | 10 min recall, 20 min topic review, 15 min practice and corrections |
| 60 minutes | 10 min recall, 25 min topic review, 20 min practice, 5 min error log |
| 90 minutes | 10 min recall, 35 min review, 30 min practice, 15 min missed-question analysis |
| 2 hours | 15 min recall, 45 min review, 40 min practice, 20 min missed-question analysis |
| 3 hours | 20 min recall, 60 min review, 60 min practice, 40 min mock review and notes |
Daily non-negotiables
Do these on every study day:
- Recall before reading. Write 5 to 10 terms, roles, or tailoring points from memory.
- Study one defined topic. Do not jump randomly between governance, agile, and mock questions.
- Answer practice questions. Even short sessions should include some question practice.
- Review explanations. The explanation review is where most improvement happens.
- Update an error log. Track why you missed questions, not just which questions you missed.
Missed-question review method
Do not just mark missed questions as “review later.” Classify the reason for each miss and assign a repair action.
| Miss type | What it looks like | Repair action |
|---|---|---|
| Terminology gap | You did not recognize a PRINCE2 Agile term, role, product, behaviour, or technique. | Add the term to a recall list and retest it the next day. |
| Governance confusion | You mixed up who decides, who manages, who delivers, or who escalates. | Redraw the role/responsibility flow for that scenario. |
| Agile concept gap | You confused iterative, incremental, empirical, collaborative, or feedback-based working. | Compare the concept against a simple delivery example. |
| Tailoring error | You knew PRINCE2 and agile separately but missed how they combine. | Write one sentence: “In PRINCE2 Agile, this is adapted by…” |
| Scenario overthinking | You chose an answer that was too extreme, too detailed, or outside the role’s authority. | Re-answer using only the facts given in the question. |
| Keyword trap | You reacted to one word and ignored the whole situation. | Underline the role, project stage, constraint, and decision needed. |
| Time pressure | You understood the topic but rushed or misread. | Practice smaller timed sets and slow down on qualifiers. |
The 3-pass correction process
| Pass | What to do | Output |
|---|---|---|
| Pass 1: Fix the answer | Read the explanation and identify the exact reason the correct option is better. | One sentence explaining the correct answer. |
| Pass 2: Fix the concept | Return to your notes or official material for that concept. | A corrected note, diagram, or flashcard. |
| Pass 3: Retest | Re-answer similar questions 24 to 72 hours later. | Confirmed improvement or repeat weak-area flag. |
7-day final review plan
Use this if your exam is in one week and you have already completed most of the content at least once. If you are starting from zero, this plan can still help, but you will need to prioritize high-yield topics and accept a narrower review.
| Day | Main goal | Study actions | Practice target |
|---|---|---|---|
| 1 | Diagnose gaps | Take a mixed diagnostic set. Build your error log. List weak areas under governance, agile, tailoring, and scenarios. | 40 to 60 mixed questions or one timed section |
| 2 | Repair governance gaps | Review PRINCE2 roles, responsibilities, decision points, controls, escalation, business case, progress, and management products as covered in your materials. | Targeted questions on roles, governance, and control |
| 3 | Repair agile gaps | Review agile behaviours, collaboration, iterative/incremental delivery, prioritization, feedback, transparency, and common agile approaches in scope. | Targeted agile concept questions |
| 4 | Focus on tailoring | Review how PRINCE2 principles, practices, processes, products, risk, change, quality, plans, and progress are adapted in agile contexts. | Scenario questions on tailoring decisions |
| 5 | Timed mock | Take a timed mock or the closest available full-length timed practice set. Do not pause. | Full timed practice |
| 6 | Explanation review | Review every missed and guessed question from the timed mock. Rebuild your final notes around repeat errors. | Short targeted sets only |
| 7 | Light final review | Review final notes, terms, roles, agile behaviours, and scenario traps. Check exam logistics and rest. | Light recall only |
7-day rules
- Stop adding new study sources after Day 4.
- Do not take a heavy mock late on Day 7 if your exam is the next morning.
- Prioritize explanation review over more question volume.
- If a topic appears repeatedly in your error log, study it before doing another mixed set.
- Your final notes should fit on 2 to 4 pages.
14-day focused plan
Use this if you have two weeks and can study most days. This plan balances review and practice without trying to rebuild the whole course from scratch.
| Day | Focus | Actions |
|---|---|---|
| 1 | Baseline diagnostic | Take a mixed diagnostic set. Sort misses into terminology, governance, agile, tailoring, and scenario judgment. |
| 2 | PRINCE2 Agile purpose | Review why PRINCE2 and agile are combined. Build a high-level map of project governance versus delivery activity. |
| 3 | Roles and governance | Review responsibilities, decision-making, project controls, escalation, and reporting. Practice role-based questions. |
| 4 | Agile fundamentals | Review iterative and incremental delivery, collaboration, transparency, feedback, self-organization where applicable, and common agile techniques in your materials. |
| 5 | Delivery approach | Compare predictive, agile, and hybrid approaches. Practice identifying when each approach is appropriate. |
| 6 | PRINCE2 tailoring | Review how practices, processes, management products, and communication may be tailored in agile environments. |
| 7 | Mixed review checkpoint | Take a timed mixed set. Spend at least as long reviewing explanations as answering questions. |
| 8 | Risk, change, and quality | Review how agile delivery affects visibility, uncertainty, change control, quality expectations, and acceptance. |
| 9 | Benefits, value, and business justification | Review how value, benefits, prioritization, and business justification are protected during agile delivery. |
| 10 | Stakeholders and communication | Review rich communication, collaboration, feedback loops, stakeholder engagement, and transparency. |
| 11 | Timed mock 1 | Take a full timed practice exam or full-length equivalent. Mark guessed questions. |
| 12 | Mock repair | Review every missed and guessed question. Create a final weak-area list. |
| 13 | Timed mock 2 or targeted timed set | If your first timed mock was stable, take another timed mock. If not, do targeted timed sets on weak areas. |
| 14 | Final review | Light recall, final notes, exam logistics, and rest. Do not add new material. |
30-day balanced plan
Use this if you are starting a structured first pass. The key is to start practice early enough that you learn how PeopleCert-style exam questions test the material.
Weekly structure
| Week | Goal | Study emphasis | Practice emphasis |
|---|---|---|---|
| 1 | Build the map | PRINCE2 Agile purpose, core terminology, governance, roles, and project structure | Short untimed sets after each topic |
| 2 | Add agile delivery | Agile concepts, behaviours, delivery methods, prioritization, feedback, collaboration, and communication | Topic-based practice |
| 3 | Integrate and tailor | Tailoring PRINCE2 in agile contexts, risk, change, quality, plans, progress, benefits, and value | Mixed scenario practice |
| 4 | Convert to exam mode | Timed mocks, missed-question repair, final notes, and recall | Full timed practice and targeted retesting |
30-day schedule
| Days | Focus | Actions |
|---|---|---|
| 1 | Orientation | Read the exam syllabus and confirm the materials you will use. Set up your error log. |
| 2-3 | PRINCE2 Agile purpose | Study why agile and PRINCE2 are combined. Summarize the difference between governance and delivery. |
| 4-5 | Roles and responsibilities | Map project-level and delivery-level responsibilities. Practice role and decision questions. |
| 6 | Governance checkpoint | Do a mixed set on project control, escalation, progress, and business justification. |
| 7 | Weekly review | Review all misses. Rewrite your weakest notes from memory. |
| 8-9 | Agile fundamentals | Review iterative/incremental delivery, feedback, transparency, collaboration, prioritization, and common agile approaches. |
| 10-11 | Agile behaviours and communication | Study behaviours and communication patterns that support agile project delivery. |
| 12 | Predictive, agile, and hybrid judgment | Practice choosing the best approach for different project conditions. |
| 13 | Topic practice | Take targeted questions on agile concepts and delivery. |
| 14 | Weekly review | Retest Week 1 and Week 2 misses. |
| 15-16 | Tailoring PRINCE2 | Review how PRINCE2 practices, processes, management products, plans, and reporting can be adapted. |
| 17 | Risk and change | Practice scenarios involving uncertainty, change, escalation, and control. |
| 18 | Quality and acceptance | Review quality expectations, acceptance, feedback, and fitness for purpose. |
| 19 | Benefits and value | Review business justification, benefits, value delivery, prioritization, and trade-offs. |
| 20 | Mixed scenario practice | Take a timed mixed set and review explanations carefully. |
| 21 | Weekly review | Update final notes and retest repeated miss categories. |
| 22 | Timed mock 1 | Take a full timed mock or full-length equivalent. |
| 23 | Mock review | Review all missed and guessed questions. Identify top 3 weak areas. |
| 24-25 | Weak-area repair | Study only the top weak areas. Use targeted practice. |
| 26 | Timed mixed set | Take a shorter timed set to confirm improvement. |
| 27 | Timed mock 2 | Take another full timed mock if ready; otherwise take two targeted timed sets. |
| 28 | Final explanation review | Review all repeated misses. Build your final 2-to-4-page notes. |
| 29 | Light recall | Review terms, roles, tailoring points, agile behaviours, and common traps. |
| 30 | Exam readiness | Confirm logistics, rest, and do only light practice if needed. |
60/90-day full preparation path
Use this if you are new to PRINCE2 Agile, have limited weekday time, or want a lower-pressure path. The main advantage is spaced repetition: you can revisit topics several times instead of trying to memorize everything late.
| Phase | 60-day cadence | 90-day cadence | Outcome |
|---|---|---|---|
| Phase 1: Setup and baseline | Days 1-5 | Days 1-7 | Materials selected, syllabus reviewed, diagnostic completed, error log created |
| Phase 2: PRINCE2 Agile foundation | Days 6-15 | Days 8-21 | Clear understanding of purpose, governance, roles, control, and project structure |
| Phase 3: Agile delivery concepts | Days 16-25 | Days 22-35 | Working knowledge of agile behaviours, iterative delivery, feedback, collaboration, and delivery approaches |
| Phase 4: Tailoring and integration | Days 26-40 | Days 36-56 | Ability to apply PRINCE2 Agile thinking to risk, change, quality, progress, value, benefits, and stakeholder scenarios |
| Phase 5: Scenario practice | Days 41-50 | Days 57-70 | Improved judgment on hybrid, agile, and predictive situations |
| Phase 6: Timed mocks | Days 51-56 | Days 71-82 | Exam timing, stamina, and explanation review |
| Phase 7: Final review | Days 57-60 | Days 83-90 | Final notes, weak-area repair, light recall, exam logistics |
Weekly rhythm for 60/90 days
| Day type | Activity |
|---|---|
| 3 study days per week | Learn or review one defined topic. End with 10 to 20 practice questions. |
| 1 practice day per week | Take a mixed set under light timing. Review explanations. |
| 1 review day per week | Retest old misses and update your error log. |
| Every 2 to 3 weeks | Take a larger timed set to check retention and timing. |
| Final 2 weeks | Shift from content learning to timed practice and explanation review. |
Long-plan checkpoints
| Checkpoint | You should be able to… |
|---|---|
| End of first quarter | Explain why PRINCE2 Agile exists and how governance and agile delivery differ. |
| Midpoint | Answer topic-based questions accurately and explain key terms without notes. |
| Three-quarters point | Handle mixed scenarios involving roles, risk, change, quality, stakeholders, and value. |
| Final two weeks | Complete timed practice calmly and repair misses quickly. |
Timed mock exam strategy
Timed mocks are useful only if you review them properly. A mock without explanation review is mostly a stamina exercise.
| Plan | When to take timed mocks | How many to aim for |
|---|---|---|
| 7-day plan | Day 5, with optional shorter timed set on Day 2 | 1 full mock plus targeted sets |
| 14-day plan | Around Days 11 and 13 | 1 to 2 full mocks |
| 30-day plan | Around Days 22 and 27 | 2 full mocks or equivalents |
| 60-day plan | Final 10 days, plus earlier larger checkpoints | 2 to 3 full mocks or equivalents |
| 90-day plan | Final 2 to 3 weeks, plus monthly checkpoints | 2 to 4 full mocks or equivalents |
Mock review checklist
After each timed mock, record:
- Questions missed because of terminology.
- Questions missed because of role or governance confusion.
- Questions missed because of agile concept confusion.
- Questions missed because of tailoring judgment.
- Questions guessed correctly but not understood.
- Questions changed from correct to incorrect.
- Topics that need same-day repair.
- Topics that can wait for later spaced review.
What to practice next
Use this table after each study session or mock.
| If your error log shows… | Practice next |
|---|---|
| Repeated role confusion | Role/responsibility mapping, escalation scenarios, and governance questions |
| Weak agile vocabulary | Short recall drills on agile terms, behaviours, delivery methods, and feedback loops |
| Weak tailoring judgment | Scenarios where PRINCE2 controls are adapted for agile delivery |
| Trouble with stakeholder questions | Communication, collaboration, transparency, and expectation management scenarios |
| Trouble with risk or change | Questions involving uncertainty, change control, prioritization, escalation, and team feedback |
| Trouble with benefits or value | Business justification, prioritization, value protection, and benefits-focused decisions |
| Good content knowledge but weak timing | Short timed sets with careful reading practice |
| Good scores but poor explanations | Fewer questions, deeper explanation review, and written reasoning for each answer |
Final-week rules
In the final week, your priority is stability, not expansion.
Do
- Review your error log every day.
- Retest previously missed questions after a delay.
- Use timed practice to confirm pacing.
- Keep final notes short and active.
- Review official terminology exactly as used in your materials.
- Check PeopleCert exam instructions, identification requirements, appointment details, and online-proctoring setup if applicable.
- Sleep properly the night before the exam.
Avoid
- Starting a new book, course, or question bank in the last few days.
- Taking repeated full mocks without reviewing explanations.
- Memorizing isolated facts without understanding how they apply.
- Treating agile as replacing PRINCE2 governance.
- Treating PRINCE2 control as preventing agile delivery.
- Studying heavily late the night before the exam.
When to stop adding new material
| Time remaining | Rule |
|---|---|
| 7 days | Add new material only if it fixes a clear syllabus gap. |
| 3 days | Stop new sources. Use only your notes, official materials, and missed-question review. |
| 24 hours | Do light recall, logistics, and rest. Avoid heavy mocks. |
Exam-readiness checks
You are closer to ready when you can do the following without notes.
| Readiness area | Check |
|---|---|
| Exam identity | You know you are preparing for PeopleCert PRINCE2 Agile Foundation (Version 2), exam code PRINCE2 Agile Foundation. |
| Governance | You can explain who controls, who manages, who delivers, and when escalation is appropriate. |
| Agile delivery | You can explain iterative delivery, feedback, collaboration, transparency, and prioritization in plain language. |
| Tailoring | You can describe how PRINCE2 elements are adapted without removing necessary governance. |
| Scenario judgment | You can identify the role, issue, constraint, and best next action in a short scenario. |
| Risk and change | You can distinguish between useful adaptability and uncontrolled change. |
| Benefits and value | You can connect delivery decisions to business justification, value, and expected outcomes. |
| Mock review | You can explain why the correct answer is best and why the distractors are weaker. |
| Timing | You can complete timed practice calmly with time to review marked questions. |
Practical next step
Choose the plan that matches your exam date, then take a diagnostic practice set before doing more reading. Use the results to build your first error log, pick your weakest PRINCE2 Agile topics, and start the daily rhythm immediately.