The four frameworks at a glance
The video introduced the decision matrix. This reading unit deepens each framework with its key characteristics, roles and use cases — as a reference guide for your practice.
Scrum
Best suited for
Product and software development with high complexity and evolving requirements. Teams of up to 10 people (Scrum Guide 2020) who can work in a self-organised manner.
Core characteristics
- Sprints: Fixed iterations of 1–4 weeks with a clear Sprint Goal
- Artefacts: Product Backlog, Sprint Backlog, Increment
- Events: Sprint Planning, Daily Scrum, Sprint Review, Retrospective
- Roles: Product Owner, Scrum Master, Developers
Strengths & limitations
| Strengths | Limitations |
|---|---|
| Fast feedback through short cycles | Scaling across multiple teams is complex |
| Clear role accountability | Requires a stable, dedicated team |
| Transparency through artefacts | Less suited for ongoing operational processes |
Kanban
Best suited for
Continuous delivery, support processes, maintenance tasks and anywhere work arrives at varying rates — without fixed sprints.
Core characteristics
- Kanban board: Visualises the workflow through stages
- WIP limits: Cap parallel work per column
- Pull principle: New tasks are pulled when capacity is available
- Metrics: Cycle time, lead time, throughput, CFD
Typical use cases
- IT operations and support teams
- Marketing teams with continuous content output
- HR processes with variable intake rates
- As a complement to Scrum at team level (“Scrumban”)
AgilePM®
Best suited for
Projects with a clear budget and deadline where scope needs to remain flexible. Especially strong for business change projects, not purely technical product development.
Core characteristics
- MoSCoW prioritisation: Must / Should / Could / Won't — scope is managed flexibly
- Timeboxing: Time, budget and quality are fixed; scope is the variable
- Project lifecycle: Pre-Project → Feasibility → Foundations → Evolutionary Development → Deployment → Post-Project
- Roles: Executive Sponsor, Business Visionary, Business Ambassador, Project Manager, Technical Coordinator, Business Analyst, Solution Developer, Solution Tester
AgilePM® project phases
| Phase | Content | Key artefact |
|---|---|---|
| Pre-Project | Validate idea, secure sponsor | Terms of Reference |
| Feasibility | Business case, high-level solution check | Feasibility Assessment |
| Foundations | Architecture, roles, rough plan | Business Foundations |
| Evolutionary Development | Iterative delivery in timeboxes | Evolving Solution |
| Deployment | Transition solution into operation | Deployed Solution |
| Post-Project | Measure benefit realisation | Benefits Assessment |
PRINCE2 Agile
Best suited for
Organisations with existing PRINCE2 governance that want to introduce agile delivery methods at team level. Combines classical project controls with an agile delivery approach.
Core characteristics
- Governance: Retains all PRINCE2 processes (Starting Up, Initiating, Controlling, Managing, Closing)
- Delivery: Teams work with Scrum or Kanban within the project structure
- Management Stage Plans: Control via stage boundaries with gate reviews
- Flexibility: Agile delivery decoupled from classical project management
Framework quick comparison
| Criterion | Scrum | Kanban | AgilePM® | PRINCE2 Agile |
|---|---|---|---|---|
| Iterations | Fixed sprints | Continuous flow | Timeboxes | Stages + sprints |
| Scope | Flexible | Flexible | Flexible (MoSCoW) | Flexible |
| Governance | Low | Low | Medium | High |
| Certification | PSM / CSM | KMP | AgilePM® Practitioner | PRINCE2 Agile Practitioner |
Key takeaways
- Scrum and Kanban are team-focused delivery frameworks without their own project governance
- AgilePM® suits projects with fixed budget/time constraints and flexible scope
- PRINCE2 Agile is the right choice for organisations that want to retain PRINCE2 governance
- No framework is universal — the choice depends on project context, team and governance requirements