Project management methodologies are structured ways of running a project from start to finish. With so many to pick from, it is tempting to look for the best one. PMI’s research suggests that is the wrong search: its 2024 Pulse of the Profession report found that project teams perform equally well using predictive, hybrid, and agile approaches. The more useful question is which method fits the project in front of you.
This guide covers 12 project management methods, what each is for, and where it tends to break. It then gives six questions that narrow the choice and applies them to three sample projects.
- What is a project management methodology?
- 12 project management methodologies compared
- Predictive methods
- Agile and adaptive methods
- Process improvement methods
- Hybrid project management
- How to choose a methodology: 6 questions
- Three sample projects
- Common mistakes when choosing
- Tracking work in actiTIME under any method
- FAQ
What is a project management methodology?
A project management methodology is the defined set of principles and practices a team follows to deliver a project. It covers how work gets organized and who decides what, along with how progress gets checked. The words around it are used loosely, so here is how this guide uses them:
- Methodology: a fairly complete way of running a project, such as PRINCE2.
- Framework: a lighter structure you fill in yourself, such as Scrum.
- Approach: a broad family, such as predictive, agile, or hybrid.
- Method or technique: a specific tool used within any of these, such as the critical path method.
Many articles, including this one, use “methodology” as the general term, and project management frameworks are usually listed alongside full methods. For specific tools and techniques, see our guide to project management tools and techniques.
12 project management methodologies compared
| Methodology | Best for | Where it breaks |
|---|---|---|
| Waterfall | Fixed requirements, costly late changes | Requirements that shift |
| Critical path method | Many dependent tasks and a hard date | Poor duration estimates |
| PRINCE2 | Governance and clear stage approvals | Small projects, if not tailored |
| PMBOK Guide | A shared standard across an organization | Used as a step by step recipe |
| Agile | Evolving requirements, frequent feedback | No customer access or fixed scope |
| Scrum | Product work in fixed cycles | Constant urgent interruptions |
| Kanban | A steady stream of requests | Fixed date projects with no limits set |
| Scrumban | Teams moving from Scrum to flow | Unclear rules from both sides |
| Extreme Programming | Software with changing requirements | Work outside software |
| Lean | Removing waste from repeated work | One off projects |
| Six Sigma | Reducing defects in a measurable process | Work with no process data |
| Hybrid | Fixed outer limits with flexible work inside | Unclear rules on which part uses what |
Predictive methods
Predictive methods define scope, schedule, and cost up front and then work to that baseline. They suit projects where the end result is known and changing course late is expensive.
1. Waterfall
In Waterfall, work moves through sequential phases such as requirements, design, build, test, and delivery, and each phase finishes before the next starts. You get predictability, but problems found late are costly to fix. See our full guide to the waterfall model.
2. Critical path method
The critical path is the longest chain of dependent tasks, and it sets the shortest possible project duration. A delay on that chain delays the finish date, while other tasks have some slack. Think of it as a scheduling technique rather than a full methodology, and one that depends on good estimates. Our critical path template shows the layout.
3. PRINCE2
PRINCE2 is a structured method now maintained by PeopleCert, built on principles, practices, and processes. Its seven principles include managing by stages and managing by exception, so senior people step in only when a stage goes outside agreed limits. Another principle is to tailor the method to the project, which is easy to forget on a small one.
4. PMBOK Guide
The PMBOK Guide is often listed as a methodology, but PMI describes it as defining the global standard for project management. In practice it is a body of knowledge and a common language, so an organization still has to decide how to apply it.
Agile and adaptive methods
Adaptive methods expect requirements to change, so they deliver in small pieces and adjust based on feedback.
5. Agile
Agile is a set of values more than a method. The Manifesto for Agile Software Development from 2001 favors, among other things, responding to change over following a plan, and customer collaboration over contract negotiation. Scrum, Kanban, and Extreme Programming are ways of putting those values into practice. Our guide to agile project management has more.
6. Scrum
Scrum organizes work into Sprints of one month or less, with a Product Owner, a Scrum Master, and Developers, as set out in the Scrum Guide. A team building a product that benefits from regular review is a good match, though Scrum struggles when urgent work keeps breaking into the Sprint. Our article on the Scrum process goes further.
7. Kanban
Work in Kanban sits on a board with a limit on how much can be in progress, and new work is pulled in when there is capacity. With no fixed cycles, it fits teams that handle a steady flow of requests, such as support, marketing, and operations. Our guide on what Kanban is includes how to calculate a WIP limit.
8. Scrumban
As the name suggests, Scrumban takes Scrum’s roles or regular reviews and adds Kanban’s board and WIP limits. It can work for teams that find Sprints too rigid but want to keep some rhythm. Agree which rules you are keeping, or you may end up with the meetings of one and the discipline of neither.
9. Extreme Programming
Extreme Programming, or XP, is an agile method for software teams, and it relies on engineering practices such as pair programming, writing tests first, and frequent small releases. Teams facing changing requirements are a good fit, though most of its practices have no direct equivalent outside software.
Process improvement methods
These two come from manufacturing and aim at improving a repeated process more than delivering a one off project, though improvement work can also be run as a project.
10. Lean
Lean grew out of the Toyota Production System and focuses on delivering value while removing waste, such as waiting, rework, and work nobody needs. In project work, it shows up as smaller batches and fewer handoffs.
11. Six Sigma
Six Sigma uses data to reduce defects and variation. Its best known structure, DMAIC, runs through define, measure, analyze, improve, and control, and ASQ describes it as a structured approach to improving existing processes. Because it needs a measurable process, it fits operations better than creative work. For software, see our list of Six Sigma tools.
Hybrid project management
12. Hybrid
Hybrid project management combines predictive and agile practices, for example a fixed budget and milestones around sprints of design and build. According to PMI, hybrid adoption rose from 20% in 2020 to 31.5% in 2023, and its Pulse research shows comparable project performance regardless of the approach used. PMI’s explanation is that organizations are getting better at matching the approach to the project, which it calls fit for purpose.
The risk with hybrid is vagueness. Write down which parts of the project are fixed and which can change, and who decides when one affects the other.
How to choose a methodology: 6 questions
Budget and team size matter, but neither points to a method on its own. The six questions below are more useful: answer them for your project and see which names keep appearing.
| Question | If yes | If no |
|---|---|---|
| 1. Are the requirements clear and unlikely to change? | Waterfall, PRINCE2 | Scrum, Kanban |
| 2. Is a late change very expensive, as in construction? | Waterfall, critical path | Scrum, XP |
| 3. Can you deliver useful pieces early? | Scrum, Kanban | Waterfall, with milestones |
| 4. Does work arrive as a stream of requests? | Kanban | Scrum or a predictive method |
| 5. Must scope, price, and date be fixed in a contract? | Waterfall or hybrid | Any adaptive method |
| 6. Is the goal to improve a repeated process? | Lean, Six Sigma | A project method |
Treat the table as a starting point, because the final call still takes judgment. If your answers split evenly between predictive and adaptive methods, the project probably suits a hybrid approach. Team experience matters too, since a method nobody on the team has used carries its own risk.
Three sample projects
Here is how the questions play out on three illustrative projects.
| Project | Answers that decide it | Choice |
|---|---|---|
| Office fit out | Clear requirements, late changes costly, nothing useful until the end | Waterfall with critical path scheduling |
| New mobile app | Requirements will change, early releases possible | Scrum |
| Marketing team requests | A stream of small jobs, no single end date | Kanban |
A client website at a fixed price sits between these. The contract fixes scope, price, and date, while the design benefits from feedback, so a hybrid fits: contract milestones outside, short review cycles inside.
Common mistakes when choosing
-
Choosing by fashion
A method that suits a software company may not suit a construction firm. Start from the project.
-
Using one method for everything
PMI’s fit for purpose finding argues for matching the approach to each project. A company can run Waterfall in one team and Kanban in another.
-
Adopting the ceremonies without the idea
Daily stand ups do not make a team agile if requirements are still frozen and feedback never arrives.
-
Applying a heavy method to a small project
Tailor it. PRINCE2 makes tailoring one of its principles for this reason.
-
Switching method mid project without a reason
If delivery is slipping, check the estimates and the scope first. A new method will not fix either on its own, and scope changes are a common cause, as our guide to scope creep explains.
Tracking work in actiTIME under any method
actiTIME does not impose a methodology. It records tasks, deadlines, estimates, and hours, and you organize them the way your method requires. A Waterfall team can set deadlines and compare estimated with tracked time in the Estimated vs. Actual Time Report, while a Kanban or Scrum team can work from the Kanban board with custom workflow statuses. Either way, tracked hours give you real numbers for the next estimate.
FAQ
What are the top 5 project management methodologies?
There is no official ranking, but Waterfall, Agile, Scrum, Kanban, and Lean appear on many lists. PRINCE2 is also common, with an established presence in the UK, Europe, and Australia.
What are the four types of project management methodologies?
There is no standard set of four. A practical grouping is predictive methods, agile or adaptive methods, process improvement methods, and hybrid approaches, which is how this guide is organized.
What are the 5 basics of project management?
The five usually named are initiating, planning, executing, monitoring and controlling, and closing. These are stages of project work rather than a methodology, and our guide to the project management process covers them.
Which project management methodology is best?
None is best in general. PMI’s 2024 research found that teams perform equally well with predictive, hybrid, and agile approaches. Pick the one that fits the project and that your team can apply well.
What is the difference between a methodology and a framework?
A methodology is usually more complete and prescriptive, while a framework gives a lighter structure that the team fills in. The terms are often used interchangeably, so check what a source means by them.
Match the method to the project
There are plenty of project management methodologies, and no winner among them. Use the six questions to find a shortlist, then tailor what you pick and be clear about which parts of the project are fixed. When it is done, review how it went with real numbers before the next project starts.
To get those numbers from your team’s work, start a free trial of actiTIME. It runs for 30 days with every feature included, and afterward you can keep the permanent free version for teams of up to 3 users.
