P2A. Themes: Plan (Free Preview)

This is a preview lesson. Please purchase the course to access all lessons.

Based on AXELOS PRINCE2 Agile® material. Reproduced under licence from AXELOS. All rights reserved.


  1. Is it OK to have a high-level plan prepared in the beginning of an Agile project?
  2. “Out PMO and customer expect us to provide them with iteration plans in the beginning of the project.” What’s your opinion about this situation?
  3. What’s the usual replacement for Gantt Charts in Agile? What’s the biggest difference between that concept and Gantt Charts.
  4. Which plans are formal, and which are informal in PRINCE2 Agile?
  5. Shall we use CPM (Critical Path Method) with our Product Backlogs?
  6. What does “planning just-in-time” mean?
  7. Which of the following teams (that work on different projects) has a higher performance?
    • Team A: velocity=120 SP/Sprint, 9 developers
    • Team B: velocity=100 SP/Sprint, 7 developers
  8. What’s the advantage of using effort-based units such as Story Points instead of time-driven ones?
  9. Because of successful Retrospectives, our productivity is much higher now, compared to the beginning of the project. Do we need to re-estimate the old items?

Show the answers

  1. Yes, as long as it’s high-level enough, and we allow adaptation for the details. The system won’t be an extreme adaptive one though.
  2. It blocks Agility.
  3. Backlogs. PRINCE2 Agile allows Gantt Charts for high-level plans (e.g. Project Plan). Backlogs are suitable when the items are not dependent, and Gantt Charts for items that have dependencies.
  4. Project Plan is formal, release plan and iteration plan are informal, and Stage Plans can be formal or informal based on the project.
  5. No. CPM is about analyzing activities based on their dependencies. Product Backlogs contain pieces of product instead of activities, and they are not dependent on each other.
  6. Planning as late as possible, to avoid assumptions and allow adaptation.
  7. This information is not enough to say. They can have different environments, they might be working on completely different projects, and finally, they are probably using different references for their Story Points. Story Points are not comparable between projects and teams.
  8. Increases productivity by preventing blame and useless controls.
  9. Not if they have been estimated in Story Points; they are self-correcting: the changes will be applied when you use Velocity to interpret the Story Points.

Back to: PRINCE2 Agile® Practitioner