PRINCE2® Agile (version 2) Foundation — Lesson 1: Foundation Principles, Business Case, Organization, People, and Context

Learning Objectives

• Explain the roles, information, criteria, dependencies, and decision points governing agile mindset and PRINCE2 concepts.
• Implement or assess business justification, project roles, and project context using controlled evidence and acceptance criteria.
• Evaluate the condition where the planned agile mindset result cannot be trusted because PRINCE2 concepts scope, ownership, or prerequisite evidence is incomplete and select a proportionate corrective response.

Detailed Topics

• agile mindset applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• PRINCE2 concepts applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• business justification applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• project roles applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• project context applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.

Instructor Demonstration

The instructor traces a project board and delivery team using Foundation guidance to control a changing initiative while preserving business justification and clear accountability. The walkthrough connects frameworks, processes, tools, decisions, and evidence captured in the Foundation project brief, stage plan, decision log, and tailored management-product set. It also tests the exception where the planned agile mindset result cannot be trusted because PRINCE2 concepts scope, ownership, or prerequisite evidence is incomplete.

Hands-On Exercise

Complete a controlled PeopleCert-aligned exercise covering Foundation Principles, Business Case, Organization, People, and Context and preserve the verified result in the Foundation project brief, stage plan, decision log, and tailored management-product set.

1. Confirm scope, roles, criteria, prerequisites, information sources, dependencies, and acceptance conditions.
2. Execute the service, project, portfolio, risk, Lean, or operational workflow while recording decisions and evidence.
3. Test normal behavior, one boundary condition, and the stated exception using a controlled scenario.
4. Document findings, corrections, ownership, retest criteria, communication, and operational handover.

Scenario Analysis

• Identify which role, process, objective, control, information source, or decision most strongly influences agile mindset.
• Compare two defensible responses and explain service, project, quality, risk, operational, and business trade-offs.
• Determine how the Foundation project brief, stage plan, decision log, and tailored management-product set should be approved, retained, reviewed, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check scope, criteria, ownership, data quality, process sequence, policy alignment, version compatibility, dependencies, status, and evidence separately. Treat “the planned agile mindset result cannot be trusted because PRINCE2 concepts scope, ownership, or prerequisite evidence is incomplete” as a hypothesis until records, interviews, configurations, calculations, and retest outcomes confirm the cause.

Validation Checklist

• Required roles, processes, criteria, controls, information, approvals, and dependencies are present.
• The Foundation project brief, stage plan, decision log, and tailored management-product set connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, documentation, communication, and operational handover are complete.

Lesson Outcome

Learners can apply Foundation Principles, Business Case, Organization, People, and Context, explain the resulting service, project, quality, risk, or operational behavior, and defend the outcome through the Foundation project brief, stage plan, decision log, and tailored management-product set.