Log in Get started
Guides

14 Project Management Methodologies and How to Choose One

B

Brett Harned• Updated Nov 17, 2026

A project management methodology is a set of principles, practices, and rules that shapes how a team plans, runs, and finishes a project. It decides whether work moves in fixed phases, short cycles, or a steady flow.

Knowing where project management methods came from helps you decide how to adapt them to your work today. This guide covers traditional, Agile, change management, and process-based methodologies, plus how to choose among them.

What is a project management methodology?

A methodology is a complete way of working with defined phases and rules, like Waterfall or PRINCE2. A framework is a lighter structure your team fills in, like Scrum. A standard, like the Project Management Institute’s (PMI) PMBOK Guide, describes good practice you tailor into any method. For the basics, start with what project management is.

Real projects rarely run one method in pure form. Ask which layer each method governs: the master schedule, the weekly plan, or the daily task flow.

Project management methodologies compared

The 14 project management methodologies in this guide handle sequence, change, and risk differently. Use this table to build a shortlist.

Method

Family

How work moves

Works best when

Waterfall

Traditional

Fixed phases, each handing off to the next

Scope and sequence are clear up front

Critical Path Method (CPM)

Traditional

Along the longest chain of dependent tasks

The finish date is fixed

Agile

Agile

Short cycles with feedback after each

Requirements will change

Scrum

Agile

Sprints of 1 month or less

A small team builds in increments

Kanban

Agile

Cards move across status columns

Work arrives continuously

Extreme Programming (XP)

Agile

Short releases with constant testing

Software requirements shift often

Adaptive Project Framework (APF)

Agile

Iterative stages with scope reviewed each stage

The goal is clear, the path less so

Event Chain Methodology (ECM)

Change management

Models risk events and their schedule effects

Schedule risk needs formal analysis

Extreme Project Management (XPM)

Change management

Fast cycles; plan and deliverable can change

Projects are short and uncertain

PRiSM

Change management

6 phases measured against sustainability impact

Sustainability is a requirement

Lean

Process-based

Cuts steps that don’t add value

Waste and rework eat the budget

Last Planner System

Process-based

Pull plan, lookahead, weekly commitments

Field work depends on trade handoffs

Six Sigma

Process-based

Measures and removes causes of defects

A repeatable process needs consistent quality

PRINCE2

Process-based

Controlled stages overseen by a project board

Governance and documentation are required

Which project management methodology is best for your project?

When it comes to project management methodologies, no method is “better” than another. Do what works for your team, your stakeholders, and your project itself. Whatever you choose, outline it with your team, and make sure everyone understands it and is on board. After all, the key to success is communication and clear expectations, not a process map or plan.

You don’t have to feel tethered to one way of working, either. A prescribed method may not work the way you want it to, and you need the right mix of people, budget, and deadline to make any method work as intended. Understand the options, then adapt them to your situation.

Hey, you might find that parts of Agile work for your team, but not all of them—and that's okay too. Whatever you do, don’t overthink your process. Try something new, adjust when you see the need, and focus on solid communications and delivering quality work.

If you’re not sure which method, or which parts of one, will work for you, think through these questions:

  • What is the intended outcome of your project?

  • Is it a product you’ll create? An experience? A specific deliverable?

  • What are the goals of the project?

  • Who needs to be involved in the project based on your answers above?

  • How do the people you’d like to assign to the project like to work?

  • Is anyone certified or really, really hardcore about sticking to a methodology?

  • If you’re working with a client, do they subscribe to a methodology?

  • Are you aware of how they work, and how will their way of working impact your team?

  • Are there any outside factors you need to take into account when planning? (Think about dependencies, project or client values, etc.)

  • What is already working for your team? What is working for your clients? Also, what isn’t working?

Match the method to the work

Your answers usually point to a starting method. Use these defaults:

  • If scope and sequence are fixed: Use Waterfall and protect the finish date with CPM.

  • If requirements will change: Run Scrum sprints or a Kanban board.

  • If field work depends on trade handoffs: Plan each week with the Last Planner System.

  • If stakeholders need formal control and sign-offs: Look at PRINCE2.

  • If defects or rework drive your costs: Borrow from Six Sigma or Lean.

On a residential build, a general contractor (GC) might set the master schedule in a Gantt chart with Waterfall phases and CPM. Each Monday, the superintendent and trade leads hold a Last Planner meeting to commit to that week’s work.

The same pairing works for any team: one method for the long-range plan, another for the weekly rhythm.

Traditional project management methodologies

Some projects—or even industries—require work to run in sequence. If you’re in construction or a similar field, where finishing specific tasks in order gets you to a finished product by a set date and within budget, traditional PM methods are worth mastering.

Traditional PM methodologies work well for industries that rely on a well-defined process to get work done. These may include construction, manufacturing, print design and production, marketing, editorial content, and IT, just to name a few.

Let’s take a closer look at 2 traditional methodologies you might want to use for your projects.

The Waterfall method

The Waterfall model was first described by Winston W. Royce in 1970. He wrote a scientific article that contained his personal views on software development and showed examples of why this process doesn’t work as well as more iterative approaches. But the Waterfall method does work in some industries. Here’s why.

Waterfall is certainly among the most widely known and practiced PM methodologies. The key ingredient in running a Waterfall project is to complete a task and hand it down to be used, or built on, in the next task or phase. That takes a fair amount of planning and requirement-gathering before work begins. Without it, steps can be missed, left incomplete, or happen out of order, and any change to the requirements can change the scope.

It’s easy to plan a project this way, but as soon as change occurs, you’ll be faced with scope changes, confusion, and pushed-out deadlines. Waterfall is known for the handoff—allowing resources to work in silos. It works in some places, less in others.

It has worked quite well for software development projects, though many teams have moved on to more modern approaches. Over time, other industries adopted it, finding that preplanning and clear requirements help them plan out steps, tasks, and resources to meet project timelines and budgets.

For residential and small commercial GCs, Waterfall phases match the job: permits, foundation, framing, rough-ins, inspections, finishes, and punch list. Each inspection is a gate, so mark it as one of your project milestones.

In a TeamGantt Gantt chart, you link those phases with dependencies. When you drag a task to a new date, its dependent tasks move with it. Save a baseline before the job starts to compare planned vs. actual dates later.

Critical Path Method (CPM)

The Critical Path Method involves a lot of steps and analysis, but the idea behind it is simple. When done properly, this method can provide great clarity into a project’s tasks and how long it will take to complete.

This project modeling technique was developed in the late 1950s by Morgan R. Walker of DuPont and James E. Kelley, Jr., of Remington Rand, who were working on similar project approaches. It has since been modified and is generally applied to any approach that breaks a project into several work tasks, displays them in a flow chart, and then calculates the project duration based on estimated durations for each task.

In essence, the method works like this:

  1. Map out all of the project’s tasks.

  2. Define what needs to finish before each task starts.

  3. Estimate how long each task will take.

  4. Calculate the longest path of tasks to the end of the project, plus the earliest and latest each task can start without making the project longer.

That’s how you determine what’s critical and what can be delayed (there can be more than one critical task). Essentially, you prioritize tasks so the most important work gets done first.

You’ll find the Critical Path Method used for many types of projects, including construction, software development, research, engineering, and even product development.

CPM also has deep roots in construction. When work on the former World Trade Center Twin Towers in NYC got underway in the mid-1960s, the Port Authority used CPM to help expedite it. The American Society of Civil Engineers’ Geo-Institute calls it one of the first uses of CPM on a large-scale civil engineering project.

On a home build, the critical path often runs through inspections and long-lead materials like windows, trusses, or cabinets. In TeamGantt, you can highlight the critical path on your Gantt chart or filter the view to show only critical tasks.

Agile methodologies

Agile methodologies are based on the mindset that self-organizing software development teams can deliver value through iteration and collaboration. The Agile Manifesto for Software Development was formally developed in 2001 by 17 practitioners and is based on a core set of values focused on delivering value and collaborating with customers. The four values are:

  • Individuals and interactions over processes and tools

  • Working software over comprehensive documentation

  • Customer collaboration over contract negotiation

  • Responding to change over following a plan

While Agile originated with software developers, any industry with some level of uncertainty can use Agile project management. For example, you may also find Agile approaches in product and service companies, digital agencies, marketing teams, distribution, automobile design, and design and engineering.

Over time, several Agile approaches have been developed, tested, and revised—just like the methodology itself. Below, you’ll find information about various Agile methodologies to research and try with your team. You might even come up with innovative ways to combine Waterfall with Agile for a hybrid approach, like using a Gantt chart to manage your Agile projects.

Scrum

Scrum is one of the simplest Agile methods in use today. There’s some confusion over who “invented” it, but we like it because it lets teams get work done in iterative sprints without the added complexity that some methodologies introduce. For the official definition, look to Ken Schwaber and Jeff Sutherland, who created Scrum and wrote the Scrum Guide.

When practicing Scrum, a team self-organizes around central roles that suit them: Scrum Master, Product Owner, and Developers. The Product Owner sets the vision and priority for the project, and the Scrum Master removes blockers so the Developers can get work done quickly. The 2020 edition of the Scrum Guide calls these 3 roles “accountabilities.”

Scrum calls for “ceremonies” (meetings for the uninitiated) to keep things on track. These include daily stand-ups, sprint planning, sprint reviews, and sprint retrospectives.

There’s an art to finding the right pace for a team, but Scrum does a really nice job of setting pace and expectations at the start of the project—and at each sprint. Test whether the roles and ceremonies work for your team, and adapt as you go. You can keep refining until your customers are happy.

Kanban

In 1953, Toyota adapted supermarket inventory control logic to its machine shop and used a “signboard” or “billboard,” which is the literal translation of the Japanese word “Kanban.”

This visual approach puts time and resources aside and focuses on tasks. Kanban helps teams decide what to produce, when to produce it, and how much of it to produce. If you’ve used a tool where cards move through stages to show where work stands, you’ve used a Kanban board.

Many Agile teams use Kanban boards to remain transparent about where their work stands in process. The visual management of the board allows teams to quickly point out and understand project obstacles, discuss them, and collaborate on ways to get past them. You’ll find a lot of teams working on digital projects using Kanban methods to manage their workflow.

In TeamGantt, the Board view shows each task as a card grouped by status. Those same tasks stay on your Gantt chart, so board users and timeline watchers see one plan.

Extreme Programming (XP)

Want to take your method to the next level...or the extreme? Well, check out XP, which was created by software engineer Kent Beck in the 1990s during his work on a payroll project at Chrysler. This Agile methodology is intended to improve quality by responding quickly to change. If you’re working on projects that have shifting requirements and continuous feedback, and know change can happen—and is normal—Extreme Programming might be just for you.

XP describes 4 basic activities that are performed within the software development process that allow for change and rapid revision: coding, testing, listening, and designing. Teams organize in shorter sprints and can immediately change course on work in progress or planned.

Adaptive Project Framework (APF)

This one may resonate for PMs who know they have to adapt their methodology to the project’s goals. With APF, you document project requirements, functions, sub functions, and features before determining project goals. The team then operates in iterative stages rather than sprints, but stakeholders can change the project scope at the start of each stage. So, truly, you adapt to the project—and its people.

Change management methodologies

Risks are inherent in all projects. You just know something will come up, and you want to prepare for them. These methodologies are meant for the PM folk who are hyper-focused on what could pull a project off the rails and come up with stable ways to get it back under control—or just roll with it and make sure the project gets done!

Event Chain Methodology (ECM)

If Critical Path wasn’t enough for you, you may want to take a look at ECM. The 6 principles of ECM make up a technique that is focused on identifying risks and their potential effects on a project’s schedule. Think of it this way: The ECM PM is living in doomsday.

Everything is a risk, and they know how to handle it. On one hand, it makes the team comfortable. On the other, it can be sort of gloomy to always think about the worst that can happen. After all, your control ends somewhere, right?

Extreme Project Management (XPM)

XPM is all about embracing change and altering project plans, requirements, resources, budgets, and even the final deliverable to meet changing needs.

Most projects that follow XPM are shorter in nature. This isn’t the type of method to use on a long project that carries the risk of dragging out for months and months. Rather, it's fast-paced and requires short cycles of work and openness to feedback and iteration that can evolve the original intent of the work.

PRiSM (Projects Integrating Sustainable Methods)

PRiSM was developed by GPM Global for managing change focused on sustainability, or using existing organizational resources to reduce negative environmental or social impacts. It follows 6 principles that are derived from the UN Global Compact’s Ten Principles. This is serious process work that can make our lives better in major ways, and it’s typically used for large-scale real estate development or construction and infrastructure projects that may result in adverse environmental effects.

If you bid public or infrastructure work, watch for sustainability requirements in the bid documents, since PRiSM’s 6 phases (per GPM) run past handover.

Process-based methodologies

New ways of working pop up every so often and catch on. Some are seen more as business processes than methods, but they have the potential to grow into them, which is how many of the methodologies above began. Not all of these will apply to you, but you might lift an idea from one and apply it to your own work.

Lean

Lean methodology is focused on removing unneeded steps, resources, and budget in order to deliver a product.

If you’re in the digital space, you might have seen talk of Lean UX, which applies Lean methods to user experience work. UX projects have traditionally carried lots of deliverables (sitemaps, wireframes, flow diagrams, content inventories, taxonomies, and more). Lean UX puts the design of the experience first, with less emphasis on deliverables.

Builders apply the same thinking through Lean construction, which targets waiting and rework between trades and gave rise to the Last Planner System.

Last Planner System

The Last Planner System is a Lean construction method where the people closest to the work commit to each week’s plan. It grew out of research and field practice by Glenn Ballard and Greg Howell, who went on to found the Lean Construction Institute (LCI). LCI frames the system as 5 conversations: should, can, will, did, and learn.

The system starts with pull planning, where the team works backward from a milestone to agree on handoffs. A lookahead a few weeks out makes work ready by clearing constraints like late materials or pending inspections. Trade leads then commit to a weekly work plan, and the team tracks percent plan complete (PPC): the share of commitments finished as promised.

Six Sigma

Six Sigma is a disciplined, data-driven methodology developed by an engineer at Motorola that has been adopted by many large organizations focused on manufacturing. It seeks predictable process results to improve the quality of the final product by following a set of steps and removing the cause for defects.

A Six Sigma process is one in which 99.99966% of all opportunities to produce some feature are statistically expected to be free of defects. That’s quality assurance—and profitability!

PRINCE2 (PRojects IN Controlled Environments)

PRINCE2 was developed for the UK government and is now used all over the world. With this methodology, the project is tightly controlled and planned before it begins, with clearly structured stages.

The approach leaves very little room for questions. It’s based on 7 principles, 7 practices, and 7 processes, with direction on very specific documentation. The PM’s role is a bit different, too: the PM handles basic activities like scheduling, while an appointed project board handles resourcing, goal setting, and the team.

Project management methodology FAQs

What are the main project management methodologies?

The main project management methodologies are Waterfall, Agile (including Scrum and Kanban), Lean, the Critical Path Method, and PRINCE2. In practice, many teams blend 2 or more into a hybrid.

What’s the difference between Agile and Waterfall?

Waterfall runs work in a fixed sequence of phases, with each phase finished before the next begins. Agile delivers work in short cycles and adjusts the plan after each one based on feedback.

Can you combine project management methodologies?

Yes. For example, a general contractor might run the master construction schedule with Waterfall and CPM, then plan each week with the Last Planner System.

Is PMBOK a methodology?

No. The PMBOK Guide is a PMI standard of good practice that you tailor your own method from.

Which project management methodology works best for construction?

\Waterfall plus CPM works well for the master schedule because construction phases and inspections follow a fixed sequence. For week-to-week field coordination, add the Last Planner System.

Which methodology is best for small teams?

Kanban or a light hybrid usually fits small teams, since both add structure without extra roles or meetings. Add more process only when handoffs start slipping.

Plan your next project your way

Map phases, dependencies, and handoffs in one Gantt chart your whole team can follow.