18 Project Management Methodologies All Project Managers Should Know: A Guide

There are many different project management methodologies to choose from, most of which fall into three project management frameworks: Waterfall, Agile, and Lean. Each project management framework, and the individual project methodologies within them, are designed for different project types and working styles.

Choosing the most suitable methodology is the first critical step to ensuring a successful project. It’s just as essential as assembling a skilled and reliable team. Which project framework or methodology you should choose will depend on your project’s goals as well as the industry you’re operating in. For instance, the flexibility of Agile methodologies is well-suited for software teams, while construction and manufacturing teams may prefer a more traditional Waterfall approach.

In this article, I will help you better understand the three main project management frameworks as well as the 15 most popular project management methodologies that sit within them. This will help you identify the ideal framework and methodology for any project you have in the pipeline.

Table of Contents Table of Contents

1. Key Takeaways
2. 18 Project Frameworks and Methodologies: An Overview
3. What is a Project Management Methodology and a Project Management Framework?
4. The Three Main Project Management Frameworks: Waterfall, Agile, and Lean
5. 1. Waterfall Project Framework
6. 2. Agile Project Management Framework
7. 3. Lean Project Framework
8. The 15 Most-used Project Management Methodologies
9. 1. PRINCE2 Methodology
10. 2. Kanban Methodology
11. 3. eXtreme Programming (XP) Methodology
12. 4. Critical Path Methodology
13. 5. Scrum Methodology
14. 6. Six Sigma Methodology
15. 7. Project Management Body of Knowledge (PMBOK)
16. 8. Scrumban Methodology
17. 9. Adaptive Project Framework Methodology
18. 10. Critical Chain Project Management (CCPM)
19. 11. Integrated Project Delivery (IPD)
20. 12. Outcome Mapping
21. 13. New Product Introduction
22. 14. Package Enabled Reengineering (PER)
23. 15. Rapid Application Development (RAD) Methodology
24. How to Implement a New Project Management Methodology
25. Conclusion
26. FAQs
27. References

Show Full Guide

Table of Contents

1. Key Takeaways
2. 18 Project Frameworks and Methodologies: An Overview
3. What is a Project Management Methodology and a Project Management Framework?
Show Full Guide
4. The Three Main Project Management Frameworks: Waterfall, Agile, and Lean
5. 1. Waterfall Project Framework
6. 2. Agile Project Management Framework
7. 3. Lean Project Framework
8. The 15 Most-used Project Management Methodologies
9. 1. PRINCE2 Methodology
10. 2. Kanban Methodology
11. 3. eXtreme Programming (XP) Methodology
12. 4. Critical Path Methodology
13. 5. Scrum Methodology
14. 6. Six Sigma Methodology
15. 7. Project Management Body of Knowledge (PMBOK)
16. 8. Scrumban Methodology
17. 9. Adaptive Project Framework Methodology
18. 10. Critical Chain Project Management (CCPM)
19. 11. Integrated Project Delivery (IPD)
20. 12. Outcome Mapping
21. 13. New Product Introduction
22. 14. Package Enabled Reengineering (PER)
23. 15. Rapid Application Development (RAD) Methodology
24. How to Implement a New Project Management Methodology
25. Conclusion
26. FAQs
27. References

18 Project Frameworks and Methodologies: An Overview

Here’s a table overview of the three main project management frameworks followed by the 15 distinct project methodologies we’ll look at on this page, for a quick-glance overview.

Note that if you’re still in the need of a platform to help you manage your projects effectively, take a look at my frequently updated guide to the best project management software.

What is a Project Management Methodology and a Project Management Framework?

A project management methodology is a set of principles, rules, and processes for planning, coordinating, and completing a project.

The terms “methodology” and “framework” are often used interchangeably, but in the case of project management, there’s an important distinction.

• Framework: The overall philosophy of the management approach, such as agile, lean, or waterfall.
• Methodology: The set of instructions for implementing the framework. For example, scrum is a popular agile methodology, and PRINCE2 is a well-known waterfall methodology.

Each project management methodology offers a different approach to dealing with common project problems such as delayed timelines, budget overspends, and miscommunication.

Think of a methodology as a project “recipe” that defines the resources, timings, and processes you should follow to deliver the desired results.

So, in the same way that chefs offer various approaches to making the perfect cupcake, project management methodologies all provide different ways of achieving the same project goals.

monday.com

monday.com - Popular Comprehensive Project Management Software

monday.com - Popular Comprehensive Project Management Software 10+ Project Views Generous Free Plan Powerful Workflow Automation

9.7/10 Read Review monday.com

VISIT SITE

The Three Main Project Management Frameworks: Waterfall, Agile, and Lean

In this section, you can learn more about the project management methodologies or frameworks that you think would be most suitablefor your project goals. For each one I’ve written up a description and some examples of the kinds of projects, industries, or teams they’re best suited to.

1. Waterfall Project Framework

The Waterfall project framework is one of the most traditional, linear project management approaches. In this model, a project flows through a series of predefined stages in a specific order. Think of it like water flowing down a waterfall, hence its name. As water flows in a linear, continuous direction, it does not go backward or stagnate.

This means that Waterfall project management is not the best fit for flexible, iterative processes. Instead, it suits structured projects where each task can only be completed once the foundations have been laid in previous stages. This method emphasizes thorough planning and documentation before starting the actual work.

Who Should Use a Waterfall Project Approach

The Waterfall approach is ideal for industries where project phases must be clearly defined and strictly followed. It is well-suited for construction, manufacturing, and engineering projects, where a precise plan is necessary to ensure structural integrity.

These types of projects are often costly, leaving little room for flexibility once the production process has begun. An illustrative example is building a house, where construction cannot begin until the foundations are in place, and once construction begins, it is hard to backtrack. As a result, the Waterfall approach contrasts with the Agile framework, which embraces continuous feedback and adaptation. Tools commonly used by Waterfall project managers include Gantt charts and features such as proofing and task dependencies.

Waterfall Project Methodologies

• PRINCE2 Methodology: Process-driven with defined stages.
• Critical Path Methodology (CPM): Focuses on identifying key project tasks.
• Project Management Body of Knowledge (PMBOK): Comprehensive framework often used in Waterfall projects.
• Critical Chain Management (CCPM): Focuses on managing resource constraints.
• Integrated Project Delivery (IPD): Often used in construction projects with a collaborative approach.
• Outcome Mapping: Focuses on tracking results, often with a more traditional approach.
• New Product Introduction (NPI): Structured, linear approach for product launches.
• Package Enabled Reengineering (PER): Reengineering business processes, typically with a Waterfall approach.

2. Agile Project Management Framework

The polar opposite of Waterfall is the Agile framework. It’s an iterative and flexible project management model that accommodates frequent revision throughout the duration of the project. Instead of following a linear route, Agile breaks projects into digestible chunks called ‘sprints’, typically lasting 1-4 weeks. During each sprint, a working product is developed and completed. Following the sprint, there will be a round of feedback and review before kicking off the next iteration, where edits will be implemented.

An Agile approach values collaboration, adaptability, and continuous improvement. Agile teams welcome feedback from both internal and external stakeholders and focus on quickly responding to change rather than sticking to a pre-determined schedule and list of deliverables.

Who Should Use an Agile Project Approach

Based on its accommodation for quick adjustments and constant feedback, an Agile approach suits marketing, research and development, and software development. In fact, it was initially designed for the latter. It suits any industry that is dynamic and fast-paced and perhaps doesn’t rely so much on tangible materials and building work. For this reason, its more suited to tech and IT vs. construction and manufacturing, which requires stricter adherence to regulations, budgets, and prior planning.

Agile Project Methodologies

• eXtreme Programming (XP) Methodology: Agile methodology focused on high-quality coding.
• Scrum Methodology: Uses short iterations called sprints.
• Kanban Methodology (also in ‘Lean’): Often used in Agile settings for continuous delivery.
• Scrumban Methodology: Combines elements of Scrum and Kanban.
• Adaptive Project Framework (APF): Adapts project scope based on feedback.
• Adaptive Project Framework Methodology: Same as APF, focusing on adaptability.
• Rapid Application Development (RAD) Methodology: Prioritizes rapid prototyping and feedback.

3. Lean Project Framework

The clue to Lean methodology is in its name: it focuses on maximizing value by minimizing waste. It was originally developed in manufacturing, specifically at Toyota. Lean aims to streamline processes, improve efficiency, and eliminate unnecessary activities that don’t add value. It’s often used in conjunction with Six Sigma to enhance both efficiency and quality. It emphasizes continuous improvement, motivating employees to find and eliminate inefficiencies in their work and respond proactively to user feedback.

Who Should Use a Lean Project Approach

Lean is an ideal methodology for mid-sized or large teams in industries like manufacturing and service industries that need smooth processes and waste reduction.

Its drawback is that its focus on efficiency, productivity, and value-adding activities may not always leave room for innovation, flexibility, and creativity, which is sometimes where great discoveries are made and certainly a requirement for more dynamic teams and projects.

Lean Project Methodologies

• Kanban Methodology (also in ‘Agile’): Focuses on visualizing workflow and reducing waste.
• Six Sigma Methodology: Focuses on process improvement and waste reduction.

The 15 Most-used Project Management Methodologies

Here’s a closer look at the project methodologies that I’ve categorized into the three primary project frameworks above.

1. PRINCE2 Methodology

PRINCE2 (Projects IN Controlled Environments) is a structured project management model and practitioner certification program. It divides projects into manageable stages and heavily focuses on thorough planning, defining clear roles, and controlling risks with a five-step management procedure.

PRINCE2 also requires the justification for running the project to be regularly reviewed and recommends that a clear structure of accountability is maintained throughout the project. The specific methodology provides a structured approach to managing risks, quality, and control mechanisms, emphasizing the need for decision-making at every stage. If you want to follow this project management methodology, you can train to be PRINCE2-certified by studying online or in person.

PRINCE2 Project Approach Examples

PRINCE2’s meticulous approach suits projects in regulated industries such as government, the public sector, healthcare, finance, and large enterprises with complex projects. Its attention to structure and accountability makes it a good fit for managing mid-large teams, where roles and responsibilities can otherwise become blurry. On the other hand, its structured and formal nature may be too restrictive for smaller, more Agile teams that may appreciate more space for experimentation in their approach to project management.

2. Kanban Methodology

Under the umbrella of the Agile framework, Kanban is a visual workflow management system that helps teams manage their ongoing tasks. Kanban boards visually depict tasks as they move through different stages, such as “To Do,” “In Progress,” and “Done.” The goal is to ensure that work flows smoothly and efficiently by limiting the number of tasks in progress at any given time.

This allows teams to focus on completing tasks before starting new ones and allows project managers to keep track of status without having to manually check in with individual team members. This helps keep teams on track by being conscious of the share of workload across members and alerting managers of any delays so that deadlines can be adjusted accordingly.

Kanban Project Approach Examples

As part of the Agile framework, Kanban is a methodology that is suitable for flexible, fast-paced teams that require constant monitoring and adaptability, such as software or IT teams. Kanban boards are highly intuitive and provide a clear project management method for the entire team to understand project and task status. However, they may lack structure and time-based planning. When compared to a Gantt chart, Kanban boards offer a lower level of complexity and less focus on rigid deadlines. This makes them less suitable for projects where fixed deadlines are important for successful delivery.

3. eXtreme Programming (XP) Methodology

eXtreme Programming (XP) is another software development methodology under the Agile framework umbrella that emphasizes customer satisfaction, teamwork, and frequent releases of functional software. XP promotes technical excellence and encourages continuous customer feedback to be taken on board to adapt the project accordingly. A project following the XP methodology involves practices like pair programming, test-driven development (writing tests before coding), and continuous integration (regularly merging code changes) with the ultimate goal of improving the quality of code.

eXtreme Programming (XP) Project Approach Examples

The larger Agile framework, and XP in particular, is suitable for small to mid-sized software development teams that need to adapt quickly to changing requirements. It does require a high level of technical expertise and discipline, which can prove challenging for those with less coding experience but will ultimately improve skills over time.

Additionally, XP requires customer feedback to improve the product, so this may be out of reach for platforms that have not yet been launched and do not have a user base.

4. Critical Path Methodology

The Critical Path Methodology (CPM) is a Waterfall-style technique used in project management to zone in on the most important tasks that must be completed in order to finish a project on time. These tasks, known as the “critical path,” are dependent on each other and must be completed in sequence in order for the project to be successfully delivered.

Critical paths help project managers identify which tasks are flexible and which are not, allowing for more realistic scheduling that can be stuck to. By focusing on the critical path, project managers can make sure that the project stays on track and is completed within the required timeframe.

Critical Path Project Approach Examples

As a Waterfall technique, CPM works best for industries where meeting deadlines and managing resources are critical, such as in construction, engineering, and large-scale infrastructure projects. However, it may be too strict and detailed for smaller projects or those where linear progression and dependencies are less important, such as in creative teams.

5. Scrum Methodology

Scrum is another Agile framework that breaks down projects into smaller, manageable sprints, usually lasting 2 to 4 weeks. Scrum emphasizes collaboration, accountability, and iterative progress toward a well-defined goal. Teams will meet every day in short “stand-up” meetings to discuss progress and address any roadblocks. Scrum involves specific roles, including the Scrum Master (who facilitates the process), the Product Owner (who represents the stakeholders), and the Development Team (who does the actual work). Scrum is designed to provide rapid delivery of a product while remaining flexible to change.

Scrum Project Approach Examples

As an Agile methodology, Scrum works well in software development and IT, but it’s not limited to that. Scrum generally works best with small to medium-sized teams in fast-paced industries requiring rapid product development cycles and collaboration. Since it uses a lot of new terminology, those unfamiliar with Scrum may take some time to adjust to the new framework. This could hinder project progress unless leadership guides the team through the process.

6. Six Sigma Methodology

Six Sigma is a methodology created by an engineer at Motorola in 1986 to make products work optimally by identifying mistakes or problems in processes. The goal is to identify anything that goes wrong and fix it so that the same mistake doesn’t happen again. It’s all about making sure things are done the same way every time, without errors, to save time and make things more efficient. Six Sigma uses a set of quality management tools and statistical methods, often represented by the DMAIC (Define, Measure, Analyze, Improve, Control) cycle.

Six Sigma Project Approach Examples

Six Sigma is widely used in manufacturing but can be applied in any industry that requires high levels of quality control and efficiency, such as manufacturing, healthcare, and finance. That said, it can be overly rigid and slow in environments that require flexibility and rapid changes.

7. Project Management Body of Knowledge (PMBOK)

Rather than a specific methodology, PMBOK (pronounced “Pimbok”) is a comprehensive set of project management standards, best practices, and guidelines developed by the Project Management Institute (PMI). The PMI also offers the CAPM and PMP certifications, which are two of the most widely recognized credentials for professional project managers.

Since PMBOK is a rather broad document, project managers can tailor it to their needs and preferences. It covers five process groups: initiation, planning, execution, monitoring, and closing. It also includes 10 knowledge areas, such as risk management, cost management, and stakeholder management, providing a thorough structure for managing any type of project.

PMBOK Project Approach Examples

PMBOK is highly adaptable and can be used in any industry, from IT to construction. It’s especially beneficial for experienced project managers handling large projects who need additional structure. However, it requires extensive knowledge and may be too detailed for smaller projects or teams, and the CAPM and PMP qualifications require time and money if you want to be fully versed in PMBOK.

8. Scrumban Methodology

Scrumban is a hybrid of two earlier-mentioned Agile methodologies: Scrum and Kanban. It allows teams to visualize their work on a Kanban board while maintaining Scrum’s iterative approach and structured planning. Scrumban aims to improve flexibility while retaining some of Scrum’s original time-boxed planning elements, such as sprint retrospectives and daily stand-ups.

Scrumban Project Approach Examples

Scrumban, an Agile approach, is great for software development, IT, and marketing. It also works well for small to medium teams that need adaptability and structured workflows across various industries. Projects that require a bit more structure and rigid planning, like construction or engineering, may be better suited to a non-agile methodology.

9. Adaptive Project Framework Methodology

APF is designed for projects with uncertain or evolving requirements. It focuses on breaking down projects into small cycles that allow for constant adaptability and feedback. The methodology is based on learning from previous cycles and making adjustments to the project plan as it unfolds. Unlike traditional methods, APF embraces open-ended uncertainty and change, allowing teams to adjust based on feedback or shifting priorities.

Adaptive Project Approach Examples

APF is best for projects where the end goals are unclear, unfixed, or likely to change. This includes R&D, IT, and software development. Since APF embraces continuous adaptation, APF is not suitable for highly structured or regulated industries.

10. Critical Chain Project Management (CCPM)

Critical Chain Project Management (CCPM) is a project management methodology that focuses on ensuring that people and tools are available when they’re needed. It expands on CPM by identifying the critical path/chain, a sequence of dependent tasks that determines the project timeline. By looking at the most important tasks that control how long the project will take, project managers can ensure that resources are ready for those tasks.

To avoid delays, extra time (called buffers) is added to the schedule so unexpected problems won’t slow down the whole project. This helps keep everything on track and ensures a timely project completion.

CCPM Project Approach Examples

CCPM is ideal for resource-heavy industries like manufacturing or engineering, where precise resource management and time sensitivity are crucial. That said, it can be overly detailed and rigid for smaller projects or industries that don’t face significant resource constraints.

11. Integrated Project Delivery (IPD)

Integrated Project Delivery (IPD) is a project management approach that champions collaboration by bringing together all key stakeholders—such as the project owner, architects, engineers, and contractors—early in the process. The goal is to promote synchronized working from the start and reduce inefficiencies and miscommunications that occur when different teams work in isolation. IPD relies on shared responsibility, with everyone involved in both the risks and rewards of the project’s outcome. In simple terms, everyone’s success depends on everyone else doing a good job.

IDP Project Approach Examples

IPD obviously suits projects with multiple players involved, such as large-scale construction, engineering, architectural, or real estate projects. It works best for projects where early involvement of all stakeholders pays off, rather than an internal team completing all of the work in isolation and then presenting it to external stakeholders at the end, with an ‘us and them’ mentality. While collaborative work can be very productive, it can be a lot to co-ordinate for a project manager, on top of resource and deadline management, so it is maybe not ideal for projects with rigid resource constraints to stick to.

12. Outcome Mapping

Outcome Mapping is a project management approach that focuses on the behavioral changes you want to achieve rather than just the activities you plan to do. It emphasizes understanding how different actions help drive desired outcomes and helps teams track their progress toward those outcomes.

Outcome Mapping Project Approach Examples

This approach is particularly useful for projects that aim to influence behaviors, attitudes, and relationships. It is best suited for social development projects, public health campaigns, environmental awareness initiatives, education, and NGOs rather than teams only focused on generating tangible outputs like product development or construction projects.

13. New Product Introduction

If you’re working on launching an entirely new product, a New Product Introduction (NPI) may be for you. It is a structured process for bringing a new product to market that involves planning, designing, developing, and launching. NPI typically follows stages like idea generation, product design, prototyping, testing, and manufacturing, ensuring that all departments work together toward a successful product launch.

New Product Introduction Project Approach Examples

Any teams working on bringing a new product to market, like manufacturers, consumer electronics, and automotive teams, can benefit from following the NPI structure. As is the nature of developing a brand-new product, NPI can be a lengthy and expensive process, with prototyping, testing, and market research all being part of the cycle. That said, it’s all part and parcel of industries that need to meet regulations and market standards.

14. Package Enabled Reengineering (PER)

Package Enabled Reengineering (PER) is a method that uses pre-built solutions or software packages to improve business processes. Rather than designing a custom solution from scratch, PER looks for existing solutions that can be adapted to meet the organization’s needs. This speeds up operations and increases the chances of a successful outcome.

PER Project Approach Examples

PER is a cost- and time-efficient route for implementing ERP systems, improving business processes, and modernizing IT systems. It is common in industries such as retail, finance, and healthcare. One drawback is that adapting existing systems may not exactly fit unique business needs, but there may be potential for adjustment and personalization.

15. Rapid Application Development (RAD) Methodology

Rapid Application Development (RAD) is a fast-paced approach to developing software or applications. It focuses on quick prototypes and iterative development, allowing teams to gather user feedback early and often, making it easier to make changes and improvements during the development process.

Instead of spending a long time isolating themselves in the planning and designing phases, RAD teams quickly develop prototypes and test them with users to gather feedback. This feedback is then used to refine the product, resulting in a final product that meets user needs in a much shorter time frame than traditional development methods.

RAD Project Approach Examples

RAD is considered an Agile methodology, so it’s ideal for software development, web design, app development, and any small to mid-sized teams that require fast iterations and high user involvement to do their best work. However, the lack of initial planning and early incorporation of user feedback will not suit all teams. Particularly teams in construction or engineering, who are better off with a more traditional Waterfall approach.

How to Implement a New Project Management Methodology

monday.com

monday.com - Popular Comprehensive Project Management Software

monday.com - Popular Comprehensive Project Management Software 10+ Project Views Generous Free Plan Powerful Workflow Automation

9.7/10 Read Review monday.com

VISIT SITE

Implementing your chosen methodology is a challenging task, especially if you’re inheriting a new team or an existing team that favors a different approach.

Cultural shifts of this kind may not happen quickly or easily, but there are a few project management best practices you can follow to ensure a smooth transition.

Conclusion

The variety of project management methodologies can be overwhelming at first, but in reality, there are only three fundamental frameworks to choose from:

1. Agile — If the customer is flexible and doesn’t know the best way to solve their problem, prioritize this approach.
2. Lean — Use lean frameworks to eliminate waste and improve efficiency in any project.
3. Waterfall — Use this approach if the customer has clear objectives, strict deadlines, and expects regular progress reports.

Once you’ve chosen the right project management methodology for you, the next step is to ensure you have the best project management software to put everything together. With the right methodology and tools in hand, your project is sure to be a success.

FAQs

Alice Martin

Senior Writer

• 

Alice Martin

Senior Writer

Alice Martin has five years experience as a writer before joining Techopedia in 2024. After completing an interdisciplinary degree in Liberal Arts and Sciences at the Universiteit van Amsterdam, she began writing in the arts and music industries. Driven by a love of research and analysis, Alice turned her attention towards all things software and technology. She now offers expert advice in these fields to help readers make informed decisions.

All Articles by Alice Martin