Every framework, certification, tool, and career path — explained clearly by a practising PM. No fluff. No gatekeeping.
Whether you're brand new to PM or levelling up an existing career, start with the path that fits you.
Start with the fundamentals — what a PM actually does day-to-day, the key skills you need, and how to land your first role.
Start learningCompare PMP, PRINCE2, AgilePM, CAPM and more — so you can invest in the right qualification for your career goals.
Compare certsWaterfall, Agile, Scrum, Kanban, PRINCE2 — we break down when to use each one and what the differences actually mean in practice.
Explore methodsHonest reviews of Jira, Asana, Monday, Notion, ClickUp and more — with recommendations based on team size and project type.
Find your toolA clear comparison of every major PM qualification — covering difficulty, cost, and who each one is best suited for.
| Certification | Provider | Level | Approx. Cost | Best For | Validity |
|---|---|---|---|---|---|
| CAPM | PMI | Beginner | £200–£300 | Those new to PM with no experience | 5 years |
| PRINCE2 Foundation | Axelos | Beginner | £300–£500 | UK/EU public sector, entry level | Lifetime |
| PRINCE2 Practitioner | Axelos | Mid-level | £400–£600 | Experienced PMs in structured environments | 3 years |
| PMP | PMI | Advanced | £500–£700 | Senior PMs seeking global recognition | 3 years |
| AgilePM Foundation | APMG | Agile | £300–£400 | PMs moving into Agile environments | Lifetime |
| CSM (Scrum Master) | Scrum Alliance | Agile | £1,000–£1,500 | Tech teams using Scrum sprints | 2 years |
| APM PMQ | APM | Mid-level | £400–£600 | UK professionals, broad PM knowledge | Lifetime |
Not every framework fits every project. Click any card for a full breakdown — when to use it, how to apply it, and real-world examples.
A sequential, linear approach where each phase is completed before the next begins. Clear milestones, heavy documentation.
Iterative sprints (1–4 weeks) with daily standups, sprint reviews, and retrospectives. Built for changing requirements.
A continuous flow system using visual boards to manage work in progress. No fixed sprints — work flows as capacity allows.
A process-based framework popular in the UK and government. Defines roles, responsibilities, and stages rigidly.
Agile at enterprise scale. Coordinates multiple Agile teams working toward shared business objectives.
Rooted in manufacturing, Lean focuses on eliminating waste, delivering value, and continuous improvement.
Waterfall is the original project management framework. Work flows in one direction — like a waterfall — through fixed phases: Requirements → Design → Build → Test → Deploy → Maintain. Each phase must be fully completed and signed off before the next begins.
Waterfall works best when requirements are well understood upfront and unlikely to change. Classic use cases include construction projects, government contracts, manufacturing, and compliance-driven software where the spec is locked before development starts.
A council building a new leisure centre. The scope is fixed (planning permission defines what gets built), the budget is approved upfront, and changing requirements mid-build is extremely costly. Waterfall is the obvious choice.
Construction, government, manufacturing, compliance software, fixed-budget projects
MS Project, Smartsheet, Gantt charts, RAID log, project charter
Scrum is an Agile framework that breaks work into short, fixed-length iterations called sprints (typically 1–4 weeks). Each sprint has a defined goal, a sprint backlog of tasks, and ends with a review and retrospective. Three core roles: Product Owner, Scrum Master, and the Development Team.
Scrum thrives when requirements are evolving, the team is co-located or remote-but-collaborative, and speed to market matters. It's the dominant framework in software development but increasingly used in marketing, product, and operations teams.
A fintech startup building a mobile payments app. Requirements change weekly based on user feedback. Two-week sprints allow the team to ship features fast, get user feedback, and pivot quickly without derailing a long-term plan.
Software development, product teams, startups, any team with evolving requirements
Jira, Linear, Azure DevOps, sprint boards, velocity tracker
Kanban is a visual workflow management method originating from Toyota's manufacturing system. Work items move across a board — typically To Do → In Progress → Done — with strict limits on how many items can be in progress at once (WIP limits). There are no sprints, no fixed iterations — work flows continuously.
Kanban is ideal for teams with continuous, unpredictable incoming work — IT support, marketing ops, customer service, maintenance teams. It's also used alongside Scrum in "Scrumban" hybrid approaches.
An IT helpdesk team receiving unpredictable support tickets. Sprints don't make sense (you can't plan when a server will go down). Kanban lets the team visualise all work, prioritise the queue, and ensure nothing gets stuck.
IT support, ops teams, marketing, customer service, maintenance
Trello, Monday.com, Jira (Kanban boards), Notion, ClickUp
PRINCE2 (Projects IN Controlled Environments) is a structured project management framework widely used in the UK public sector and large organisations. It defines 7 principles, 7 themes, and 7 processes — covering everything from project initiation to closure. Roles and responsibilities are explicitly defined for every participant.
PRINCE2 is well suited to large, complex projects with multiple stakeholders, regulatory requirements, and strict governance needs. It's the go-to framework for UK government, NHS, and large infrastructure programmes. If you're in the public sector, chances are PRINCE2 is expected.
An NHS Trust implementing a new patient records system. Multiple departments involved, regulatory compliance required, and a large budget with public accountability. PRINCE2's governance structure ensures clear sign-off and audit trail at every stage.
UK public sector, NHS, government, large infrastructure, regulated industries
MS Project, Smartsheet, RAID log, PID template, stage plan
SAFe is a framework for scaling Agile practices across large organisations with multiple teams. It introduces three levels — Team, Programme, and Portfolio — to coordinate Agile delivery across entire enterprises. It combines Agile, Lean, and DevOps principles into a structured operating model.
SAFe is designed for enterprises with 50+ people working on interconnected products. If you have multiple Scrum teams that need to synchronise releases and share a common roadmap, SAFe provides the coordination layer Scrum alone doesn't offer.
A major bank with 12 Scrum teams building a new digital banking platform. Each team works independently but their releases must be coordinated. SAFe's PI Planning brings all teams together to align dependencies and commit to shared quarterly goals.
Large enterprises, banks, telecoms, multiple Agile teams, complex product portfolios
Jira Align, Rally, Azure DevOps, programme board, PI planning canvas
Lean PM is derived from Toyota's Lean Manufacturing system. Its core philosophy is simple: eliminate waste and maximise value. The five Lean principles are: Define Value, Map the Value Stream, Create Flow, Establish Pull, and Seek Perfection. Everything that doesn't add value to the customer is considered waste and should be removed.
Lean works wherever there's repetitive, process-driven work that can be optimised. It's widely used in manufacturing, healthcare, logistics, and increasingly in software and services. If your team is doing the same types of tasks repeatedly and you want to get faster and more efficient, Lean thinking applies.
A hospital A&E department applying Lean to reduce patient waiting times. By mapping the patient journey from arrival to treatment, they identify that 40% of time is spent waiting for test results. Lean tools help them redesign the process to cut waiting time by half.
Manufacturing, healthcare, logistics, operations, process improvement teams
Value stream maps, Kanban boards, A3 reports, 5S checklists, Kaizen logs
Honest assessments of every major project management platform — what each is actually good for, and what it costs.
All-in-one platforms
Best for marketing & ops teams. Clean UI, strong integrations.
Highly visual, great dashboards. Popular with non-tech teams.
Feature-rich and affordable. Can be overwhelming at first.
Flexible wiki + database hybrid. Perfect for small teams.
Developer-focused
The industry standard for software teams. Powerful but complex.
Modern, fast, beautiful. The new favourite of product teams.
Scrum-friendly, less overhead than Jira. Good mid-size teams.
Free if you're already on GitHub. Basic but tight integration.
From your first PM role to the C-suite — here's what the typical trajectory looks like and what each step requires.
Supporting senior PMs on larger projects, managing small workstreams, building your toolkit. Focus on getting your CAPM or PRINCE2 Foundation here.
Leading projects end-to-end, managing stakeholders, budgets, and cross-functional teams. The PMP or PRINCE2 Practitioner gives you a significant salary boost here.
Managing multiple complex projects simultaneously, mentoring junior PMs, contributing to PMO strategy and governance frameworks.
Overseeing a portfolio of related projects, aligning delivery with strategic business objectives, managing large teams and senior stakeholders.
Setting delivery strategy at the organisational level, building PMO capability, and influencing business direction at board or executive level.
Built by a practising PM. Every template I actually use — available to download instantly, for free.