AgilePM Project Delivery Foundation Training Course

Course overview

Projects rarely fail because teams lack effort; they fail when delivery decisions are delayed, priorities shift without control, and governance is either too weak or too heavy for the work. AgilePM provides a disciplined project-management framework for organisations that need to deliver usable business outcomes quickly while retaining clear roles, planning controls, risk management and senior stakeholder oversight. This course helps project professionals apply AgilePM in environments where iterative delivery must coexist with budgets, deadlines, suppliers and formal decision-making.

Participants learn the AgilePM lifecycle, principles, roles, products and management practices derived from the DSDM Agile Project Framework. They practise shaping a viable project through a Pre-Project and Feasibility view, defining Foundations, prioritising requirements with MoSCoW, planning timeboxes, managing iterative development, and controlling risks, issues, quality and change. The course also addresses facilitation, stakeholder communication, empowered teams, governance checkpoints and the practical distinction between fixed time and cost versus variable scope.

Delivery combines instructor-led explanation with a sustained project case study. Teams produce an AgilePM project pack containing a Prioritised Requirements List, Solution Development Team plan, Delivery Plan, Timebox Plan, risk log, stakeholder communication approach and benefits-focused deployment plan. Participants leave with a certificate of completion and a practical reference set they can adapt for a live project, giving managers visible evidence of methods that can be applied after the course.

The course is best suited to practitioners who already contribute to projects and now need a structured agile delivery approach rather than a purely team-level agile method.

Course objectives

By the end of this course, participants will be able to:

• Apply the AgilePM lifecycle from Pre-Project through Deployment and Post-Project review
• Define AgilePM roles, responsibilities and governance decision points for an iterative project
• Create a Prioritised Requirements List using MoSCoW prioritisation and acceptance criteria
• Develop a Foundations baseline covering business case, solution outline, architecture and delivery approach
• Plan increments and timeboxes using Delivery Plans, Timebox Plans and team capacity assumptions
• Facilitate collaborative workshops to resolve requirements, risks, dependencies and delivery decisions
• Control project risk, issues, quality and change while protecting agreed time and cost constraints
• Produce an AgilePM project delivery pack for use with sponsors, teams and operational stakeholders

Benefits of attending

Target competencies

Who should attend

• Project Managers — who need to govern iterative delivery without losing control of scope, risk, budget and deadlines
• Programme Managers — who coordinate multiple initiatives and need consistent agile project controls across workstreams
• PMO Managers — who design delivery assurance, reporting and governance standards for agile projects
• Business Analysts — who define, prioritise and validate requirements with business and delivery teams
• Product Owners — who make scope and priority decisions within timeboxed project delivery
• Delivery Managers — who lead cross-functional teams through releases, dependencies and operational handover

Requirements and prerequisites

Participants should understand the basic language of project delivery, including scope, schedule, budget, stakeholders, risks, issues and business cases. Experience contributing to a project team, coordinating work, gathering requirements or supporting project reporting is strongly recommended. Familiarity with iterative or agile ways of working is useful but not essential; the course explains AgilePM terminology and the DSDM lifecycle from first principles. Participants should be comfortable reading simple project plans and working in small groups. No previous AgilePM qualification, formal PRINCE2 training, Jira experience or software-development background is required.

Training methodology

The course uses short instructor-led sessions to introduce each AgilePM practice, followed by guided application to a realistic business change project. Participants work in delivery teams to define a project vision, negotiate MoSCoW priorities, build Foundations, plan increments and run a simulated timebox review. Facilitated discussions examine trade-offs between scope, quality, risk and governance. Templates based on AgilePM products are completed throughout the week, then consolidated into an end-of-course application plan identifying how each participant will introduce selected practices on a current or upcoming project.

Course outline

Day 1: AgilePM principles, lifecycle and project roles

• AgilePM purpose and its relationship to the DSDM Agile Project Framework
• The eight AgilePM principles and their management implications
• AgilePM lifecycle phases from Pre-Project to Post-Project
• Business, management, solution development and solution deployment roles
• Project governance in an agile delivery environment
• The business case and the concept of a clear business need
• AgilePM products, baselines and information radiators

Workshop: Teams analyse a business change case and produce a project vision, initial business case and role allocation for an AgilePM initiative.

Day 2: Feasibility, Foundations and prioritised requirements

• Pre-Project objectives and project mobilisation decisions
• Feasibility assessment of business, technical and organisational viability
• Foundations phase objectives and the baseline at the end of Foundations
• Prioritised Requirements List structure and requirement identifiers
• MoSCoW prioritisation rules for Must, Should, Could and Won't Have requirements
• Acceptance criteria and quality expectations for requirements
• Solution Architecture Definition and Development Approach Definition

Workshop: Teams create a Foundations outline and a MoSCoW-prioritised requirements list with acceptance criteria for the case-study solution.

Day 3: Planning increments and managing timeboxes

• Incremental delivery strategy and deployment cadence
• Delivery Plan purpose, content and planning horizons
• Timebox anatomy: kick-off, development, review and close-out
• Timebox Plan creation using objectives, activities, resources and acceptance criteria
• Estimating at project, increment and timebox levels
• Team capacity, dependencies and resource coordination
• Daily coordination and visible progress tracking

Workshop: Teams build a Delivery Plan and detailed Timebox Plan, then test whether their Must Have scope fits the available capacity.

Day 4: Control, collaboration and quality in delivery

• AgilePM risk management across the lifecycle
• Issue management, escalation routes and empowered decision-making
• Change control through prioritisation rather than uncontrolled scope growth
• Quality management, testing strategy and acceptance practices
• Facilitated workshops and collaborative modelling techniques
• Stakeholder engagement and communication planning
• Tracking progress with Timebox Reviews and project-level reporting

Workshop: Participants run a simulated Timebox Review, update a risk and issue log, and agree corrective actions with a sponsor panel.

Day 5: Deployment, benefits and workplace application

• Deployment phase activities and readiness criteria
• Incremental release, user adoption and operational handover
• Benefits assessment and continued business-case management
• Post-Project review and lessons learned capture
• Tailoring AgilePM for regulated, supplier-led and hybrid projects
• Integrating AgilePM with PRINCE2 governance and organisational PMO controls
• Personal AgilePM implementation planning for a live project

Workshop: Each participant consolidates the case-study artefacts into an AgilePM delivery pack and drafts a 30-day application plan for their workplace.

Tools & standards covered

AgilePM Handbook, DSDM Agile Project Framework, Jira, PRINCE2

A typical training day

Live online deliveries follow the same structure in the East Africa Time zone, with shorter screen blocks and longer breaks.

What the fee includes

How you can take this course

Certification

Participants who complete the full five days receive the Skillset Development Certificate of Completion, stating the course title, course code, dates and delivery format — suitable for professional-development records and employer reimbursement.

Frequently asked questions