Popular project management methodologies

From information technology to marketing, teams operating across a diverse range of industries and disciplines rely on project management methodologies to deliver for their organizations.

While project management methods are widely used, there’s no one-size-fits-all solution. Rather, there are dozens of different ways to manage projects. If you want to set the stage for the success of your project while also ensuring that your time and resources are used efficiently, it’s vital that you choose the right management framework.

With that in mind, here’s an overview of 23 of the best project management methodologies. Armed with this information, you’ll be able to identify the approach that best serves your business.

This post will also touch on the following topics:

• What a project management methodology is
• 23 popular project management methodologies
• How to choose a project management methodology

What is a project management methodology?

A project management methodology is a set of tools and guidelines that help you organize projects in a way that optimizes efficiency and performance.

More specifically, a given project management method helps you more easily manage a project by providing a repeatable series of steps and principles. The goal of any framework is to promote collaboration, increase operational efficiency, keep the project on budget, and enhance the quality of the final deliverable.

23 popular project management methodologies

While there are many methodologies within project management, the following are some of the most well-known.

1. Waterfall methodology

Alternatively referred to as the software development life cycle (SDLC), the Waterfall method is a linear approach to project management. In this methodology, each phase of work “cascades” into the next.

When using this approach, project managers connect each task to the previous one with a dependency, meaning teams can’t move on to the next piece of work unless they’ve addressed outstanding tasks. This approach promotes collaboration and ensures that the team stays focused on the task at hand.

Who should use it? Because of the Waterfall method’s thorough, detail-oriented nature, this technique is best suited for large teams working on big projects involving multiple clients and stakeholders.

2. Agile methodology

The Agile methodology is one of the most commonly used project management frameworks, surpassing even Waterfall in popularity. However, it isn’t actually a formal methodology but a principle that focuses on speed, agility, collaboration, and iterative processes. Typically, teams will apply the Agile concept to a specific project management methodology, such as Kanban, Scrum, Crystal, or Extreme Programming.

You may find that using a hybrid approach that combines Agile and another framework is the best project management strategy for your team. As such, it’s important to use flexible project management software that can handle a variety of methods, including a singular Agile framework or multiple techniques.

Who should use it? Marketing teams find Agile appealing, as it provides more flexibility and promotes better creativity than more rigid frameworks like Waterfall.

3. Kanban methodology

The Kanban methodology uses a “Kanban board” to visualize project backlogs. Agile teams frequently use the Kanban framework to track project progress and avoid bottlenecks.

Traditionally, project managers built Kanban boards using physical items, such as bulletin boards or whiteboards. Today, Kanban boards are created using digital tools that allow users to drag assignments from column to column as the team completes assignments.

Kanban is a very loosely defined methodology, meaning teams can adapt it to their needs. This attribute also makes it a great pairing with Agile.

Who should use it? Kanban is a good fit for teams of any size, especially if the group is composed of hybrid or remote workers.

4. Scrum methodology

Short bouts of work known as “sprints” are a foundational component of the Scrum methodology. Each sprint lasts one to two weeks and involves a team of no more than 10 people.

Scrums are run by a Scrum master, who is tasked with leading daily meetings, overseeing sprints and sprint retrospectives (work recaps), and presenting demos to stakeholders. Like Kanban, the Scrum methodology is often used with Agile principles.

Who should use it? Any team that’s using or has considered adopting Agile principles should try the Scrum methodology.

5. Critical Path Method

The Critical Path Method (CPM) is a framework for identifying and scheduling key tasks within a long-term project. Project managers use CPM to create task dependencies, identify project goals, and track progress toward those objectives.

The core function of this framework is to help managers map out milestones and deliverables so they can meet important deadlines.

Who should use it? The CPM framework is best suited for small-to-midsize teams. Its simplistic approach may not be a good match for complex projects.

6. Lean project management methodology

The Lean project management methodology prioritizes eliminating waste via its simple framework.

Under the traditional Lean methodology popularized by Motorola and Toyota, “waste” referred to physical materials. Today, waste refers to any practice that consumes resources but doesn’t add value, any task that over-taxes existing resources (including team members), or overproduction in general.

Who should use it? Lean is an excellent methodology for teams that frequently encounter efficiency challenges. Using Lean to reduce waste will have a major impact on big companies, but it can also benefit smaller organizations.

7. Six Sigma methodology

Six Sigma is primarily used for quality-management purposes. It isn’t a methodology in the traditional sense but rather a philosophy designed to support continual procedural improvement and remove product defects.

Six Sigma is often combined with the Agile framework or the Lean methodology. These hybrids are known as Agile Six Sigma and Lean Six Sigma, respectively.

Who should use it? Six Sigma aligns well with organizations that have at least several hundred employees and want to remove waste from projects to increase profitability.

8. Critical Chain Project Management methodology

The Critical Chain Project Management (CCPM) methodology is a more detailed variation of CPM. In addition to providing a breakdown of each piece of work, CCPM also sets specific time constraints for each task.

CCPM makes it apparent when a piece of work is exceeding the amount of time allotted to it. This framework also incorporates resource-leveling principles, which quickly resolve large workloads by distributing tasks across the team.

Who should use it? CCPM can be a good option for large and small teams alike and is most effective for resolving project efficiency issues.

9. Event Chain Methodology

Event Chain Methodology (ECM) acknowledges that any number of outside events or factors can impact a project’s progress.

ECM strives to account for and manage these factors so project leaders can meet important deadlines and stay on budget. As inevitable hurdles arise during the project lifecycle, managers can update their ECM strategy as needed to stay on track.

Who should use it? Teams that have struggled to meet deadlines or have had projects derailed by external factors may want to consider the ECM framework.

10. Extreme Programming methodology

The Extreme Programming (XP) methodology is designed for fast-paced projects facing stringent deadlines. XP features short development cycles and a large number of releases. This approach optimizes productivity and yields quick turnarounds on deliverables.

XP’s core values include feedback, respect, communication, simplicity, and courage. The framework encourages team members to take calculated risks and pursue project objectives.

Who should use it? The Extreme Programming framework can be applied with results to small or midsize teams facing tight deadlines. It should be used sparingly, however, as the rigorous nature of the method can lead to burnout.

11. Crystal methodology

Like the Agile framework, the Crystal methodology focuses on team members, not processes and tools. By prioritizing interactions between individuals, Crystal promotes collaboration and team chemistry to optimize productivity.

The Crystal methodology assigns defined time spans to each bout of work. After each round, the project manager gathers feedback from the team and makes adjustments to avoid bottlenecks.

Who should use it? The Crystal methodology is good for small teams that want a lightweight, customizable framework.

12.Feature Driven Development methodology

Feature Driven Development (FDD) also borrows heavily from the Agile framework. FDD works in repetitive rotations while prioritizing features that the client is looking for in the final deliverable.

The FDD methodology includes five steps:

1. Develop a model.
2. Build a feature list.
3. Plan by feature.
4. Design by feature.
5. Build by feature.

After each rotation, the team repeats the above steps to optimize the final product and add on must-have features.

Who should use it? The FDD methodology is a good fit for teams that tend to work with highly involved clients.

13. Dynamic Systems Development Method

Dynamic Systems Development Method (DSDM) also incorporates many Agile principles. However, it distinguishes itself by calling for time, quality, and cost requirements to be defined before work gets underway.

Once work begins, the DSDM framework prioritizes tasks into four categories — musts, shoulds, coulds, and won’t-haves. Tasks can be recategorized to meet project deadlines.

Who should use it? DSDM is a good match for teams that want the flexibility of Agile but are also required to define cost, quality, and time constraints in the project brief.

14. Adaptive Software Development methodology

As the name implies, the Adaptive Software Development methodology is designed for technology developers. It recognizes that processes must be continuously adapted and modified to align with the work that needs to be completed.

The Adaptive Software Development method is based on three cyclical steps — speculate (plan), collaborate (balance changing external factors and work), and learn (gather feedback and implement changes).

Who should use it? This framework should be employed by software development teams that need a relatively simple yet adaptable set of processes to facilitate project completion.

15. Rational Unified Process methodology

Rational Unified Process (RUP) consists of three foundational elements — roles (who’s involved in a project), work products (what’s being created), and tasks (units of work assigned to a role).

RUP also features four phases — inception (developing a raw project idea and evaluating its viability), elaboration (defining clear project objectives and identifying what resources you will need), construction (completing the software development project), and transition (beta testing, gathering feedback, and optimizing the user experience).

Who should use it? The Rational Unified Process methodology is well-suited for managing smaller projects and organizing compact teams. Due to its simplistic nature, it can be difficult to adapt to larger, enterprise-level projects that involve bigger teams and multiple stakeholders.

16. PRINCE2 — PRojects IN Controlled Environments methodology

PRojects IN Controlled Environments (PRINCE2) was developed by the UK government. Based on the Waterfall methodology, PRINCE2 is comprised of seven core principles:

1. Starting the project
2. Directing the project
3. Initiating the project
4. Controlling the project
5. Managing delivery of the project
6. Managing the stage boundary
7. Closing the project

Due to its rigidness, it’s best suited for large, big-budget undertakings as opposed to more fast-paced projects.

Who should use it? PRINCE2 is a great approach for large-scale IT projects that involve multiple stakeholders.

17. Scrumban methodology

Due to Kanban’s loosely defined framework, it can be — and often is — combined with Agile. But recently, project managers have begun combining Kanban with Scrum, creating the hybrid Scrumban methodology.

Scrumban uses sprints to quickly achieve tasks and frequent meetings to promote collaboration. However, it also includes a project board to visualize work and help keep team members apprised of upcoming deadlines.

Who should use it? Scrumban may be a good fit for teams that need a way to visualize work but like the concept of dividing a project into short bouts of work.

18. Adaptive Project Framework methodology

Alternatively referred to as “Adaptive Project Management” (APM), the Adaptive Project Framework (APF) accounts for unknown factors that can emerge during a project. It’s designed to help teams prepare for the unexpected and respond in a way that keeps the project on task and under budget.

The APF methodology features five phases:

1. Project scope
2. Cycle plan
3. Cycle build
4. Client checkpoint
5. Final review

Who should use it? The APF methodology supports collaboration with stakeholders and ensures that they’re satisfied with the final results. It’s a good fit if your stakeholders are highly involved.

19. New Product Introduction methodology

The New Product Introduction (NPI) methodology is a multistep strategy for taking a product from concept to market-ready deliverable.

The NPI framework involves frequent assessments throughout the project lifecycle to verify that it’s progressing as planned. Representatives from each department will participate in these reviews, as will the stakeholders.

Who should use it? The New Product Introduction methodology is effective for managing large teams that may have conflicting interests, goals, and ideas. The frequent reviews help achieve synergy across departments and teams to yield a higher quality deliverable.

20. Package-Enabled Reengineering methodology

The Package-Enabled Reengineering (PER) framework helps businesses revamp existing processes or products.

PER facilitates business transformation by giving a different set of team members the opportunity to redesign processes and past project deliverables.

Who should use it? Businesses should use the PER approach if they need to completely overhaul core products, services, or processes. It isn’t a good fit for incrementally optimizing existing systems.

21. Outcome Mapping methodology

Outcome Mapping (OM) shifts the focus away from deliverables and instead prioritizes measuring the impacts or outcomes of a project.

The Outcome Mapping framework was created by the International Development Research Center (IDRC) as a means of gauging the efficacy of social projects. It’s primarily used to modify behavior to achieve desired outcomes.

Who should use it? If your project’s top priority involves modifying behavior rather than producing deliverables, you should consider using the MP methodology.

22. Rapid Application Development methodology

Designed to facilitate faster software development, the Rapid Application Development (RAD) methodology is based on the Agile framework. Under this framework, developers rapidly release software iterations, gather feedback, and apply that information to improve the deliverable.

The RAD methodology allows developers to present clients with a functional model (albeit an imperfect one) much sooner. By doing so, they can gather vital feedback from the stakeholder and ensure that the final product aligns with their expectations.

Who should use it? Your team should consider the RAD methodology if you have an experienced team of software developers, prioritize speed, and want to keep the client directly involved in the project.

23. Project Management Body of Knowledge methodology

The Project Management Body of Knowledge (PMBOK) methodology was created by the Project Management Institute. This set of principles and best practices outline core development processes that are a staple of any project. The framework outlines five project management phases, which are:

1. Initiation
2. Planning
3. Execution
4. Performance
5. Closure

One caveat of the PMBOK is that it isn’t as detailed as many other project management methods, meaning you’ll need to prioritize tasks on your own. However, the freedom to prioritize tasks on your own can be advantageous, such as if your team is working on nontraditional or nonlinear projects.

Who should use it? The PMBOK methodology can serve as a standalone project management tool for small teams working on relatively straightforward tasks. However, it should be paired with a more comprehensive framework if you’re working on a complex project.

Now that you know what options you have regarding project management methodologies, it’s time to find the right framework for your organization.

How to choose a project management methodology

Numerous factors combine and interact to determine which project management method is the best fit for a particular team and organization. Here are some variables you should be mindful of when exploring different methodologies:

1. Client or stakeholder collaboration. If a client or stakeholder is going to be closely involved, you’ll need a more flexible framework, as they’ll likely suggest last-minute changes to the project. Conversely, if your client will be involved minimally, a rigid framework can provide the guidance your team needs to expedite operational efficiency and streamline tasks.
2. Flexibility. Ensure that your methodology provides the necessary flexibility for the project’s scope to change after work has begun. Some methods are rigid enough to prevent anyone, including the stakeholder, from changing the scope or goals once work has started. If you want to keep the scope or objectives from evolving mid-project, choose a stringent methodology. Conversely, more flexible methods allow your team to alter course, which is beneficial if you work with dynamic goals.
3. Timeline. If you are working under tight time constraints, you need a fast-paced methodology that will keep everyone on task and apprised of upcoming deadlines. However, if you are prioritizing product quality above all else and have the room to stretch deadlines, you can leverage a looser project methodology.
4. Risk tolerance. Taking on any project involves incurring some degree of risk. However, large, big-budget endeavors involve significantly more risk to your team and the organization. Smaller projects often have more leeway to explore out-of-the-box solutions. Choosing the right methodology will help your team mitigate risks and protect stakeholders’ interests.
5. Budget. Some methodologies require you to set and closely monitor your budget for the entire project lifecycle, whereas others offer some degree of flexibility. If you might need additional resources mid-project, make sure your methodology leaves room to pull in more funding or team members.
6. Team size. Consider whether your team is small and compact or large and scattered across multiple departments. Some methodologies are especially effective at managing small teams, whereas others are better suited for organizing large, multidisciplinary groups.

By considering these factors, you can quickly rule out project management methodologies that are a poor fit for your team and shift your attention to frameworks that are aligned with your goals. In doing so, you stand to acquire a better defined and more well-organized view of your project, boost team morale, and enhance efficiency exponentially.

Streamline project management with Adobe Workfront

Learning about project management methods can help you find the right one for your projects. After familiarizing yourself with the various frameworks available, choose a project management methodology that aligns with your business goals and industry-specific needs.

Once you’ve selected a methodology, the next step is to optimize its efficiency by pairing it with intuitive project management software, such as Adobe Workfront.

Workfront unifies your teams and empowers your brand to deliver personalized customer experiences at scale. From IT initiatives to marketing campaigns, you can run any business project with Workfront. As a customizable solution, you can customize your Workfront experience to align with your chosen project management methodology.

Schedule a Workfront product tour or watch our overview video to learn more.