Project Management Framework vs Methodology: Differences and Examples

Project Management Framework vs Methodology: Differences and Examples

A project management framework is a flexible structure of principles, stages, and guidance that a team tailors to each project. A project management methodology is a prescriptive system of practices, procedures, and rules that dictates steps, roles, and tools. PMBOK Guide and Scrum are frameworks. PRINCE2, Waterfall, and Six Sigma are methodologies.

Sources use the 2 terms interchangeably, which creates confusion on exams and in PMOs. This article draws the line by 1 test: prescriptiveness. It covers the differences, 8 named examples, a selection method, and the way the 2 combine.

What is the difference between a project management framework and a methodology?

A framework gives structure and leaves decisions to the team. A methodology gives instructions and removes decisions from the team. Frameworks are tailored. Methodologies are followed. The amount of prescribed detail separates the 2.

The table below compares them across 9 attributes.

Attribute	Framework	Methodology
Definition	A set of principles, stages, and guidance	A system of practices, techniques, procedures, and rules
Prescriptiveness	Low: the team fills the gaps	High: the method answers what, who, how, and when
Flexibility	High: tailored per project	Low: deviations need approval
Roles and responsibilities	Described in general terms	Defined with authority levels
Templates and tools	Suggested	Supplied
Documentation load	Light to moderate	Moderate to heavy
Best fit	Variable scope, innovation, software	Regulated, high-risk, repeatable work
Examples	PMBOK Guide, Scrum, SAFe	PRINCE2, Waterfall, Six Sigma DMAIC
Typical owner	Standards body or community	Organization or PMO

PMI defines a methodology as a system of practices, techniques, procedures, and rules used by those who work in a discipline. The definition names rules and procedures. A framework names neither.

What is a project management framework?

A project management framework is a structure of principles, life cycle stages, and good practices that guides how a project runs. It stays high-level, so the team selects tools, templates, and sequencing. Frameworks adapt to the project instead of dictating its steps.

A framework supplies 3 elements: a life cycle, a control cycle, and a toolbox of templates. The life cycle runs through 5 phases: initiating, planning, executing, monitoring and controlling, and closing.

Four frameworks anchor the field:

• PMBOK Guide (PMI): a standard of generally recognized good practices. The 7th Edition (2021) uses 12 principles and 8 performance domains. The 8th Edition, released in late 2025, consolidates to 6 principles and 7 performance domains.
• Scrum: a lightweight framework for complex adaptive work. The Scrum Guide defines 3 accountabilities (Scrum Master, Product Owner, Developers), 5 events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and 3 artifacts (Product Backlog, Sprint Backlog, Increment).
• Scaled Agile Framework (SAFe): a framework that scales Agile across multiple teams and portfolios.
• Predictive, adaptive, and hybrid approaches: 3 delivery frameworks that set how much planning happens before work starts.

The PMBOK Guide shows why the label matters. It tells a PMO which good practices exist. It does not define the risk impact threshold in dollars, the approval authority levels, or the templates. The organization supplies those. A PMO that “implements the PMBOK” has adopted a framework and still owns the job of building a methodology.

What is a project management methodology?

A project management methodology is a prescriptive system that defines the processes, roles, workflows, templates, and governance for delivering a project. It answers 5 questions: what to do, who does it, how, when, and under whose oversight.

Methodologies suit work where consistency and control matter more than speed of change. Examples include:

• Waterfall: a sequential method with 5 phases (initiation, planning, execution, monitoring and control, closure) and approval gates between them.
• PRINCE2: a process-based method built on 7 principles, 7 themes, and 7 processes. It originated in UK government project work and requires a defined project board and stage controls.
• Six Sigma (DMAIC): a data-driven method with 5 phases: Define, Measure, Analyze, Improve, Control.
• Lean: a method that removes waste and drives continuous improvement.
• Kanban: a visual method that limits work in progress on a board.

Critical Path Method (CPM), Critical Chain Project Management (CCPM), and Program Evaluation and Review Technique (PERT) sit 1 level lower. They are scheduling techniques that a methodology or framework calls on. Treat them as tools, not as methodologies.

Why do sources classify Scrum, Agile, and PMBOK differently?

Sources disagree because they sort by origin, not by prescriptiveness. Scrum is a framework because it forces the team to decide how to do the work. PMBOK is a framework because it leaves implementation to the organization. Agile is a mindset defined by 4 values and 12 principles.

Three classification disputes recur:

• Scrum: Ken Schwaber describes Scrum as a framework that provides an environment in which complex work gets done. Scrum prescribes 5 events but leaves engineering practice open.
• PMBOK: PMI describes the guide as generally accepted good practice. Practitioners such as the author of “Why the PMBOK is not a methodology” argue that it lacks roles, templates, and performance criteria.
• Agile: The Agile Manifesto (2001) states 4 values. The Manifesto is neither a framework nor a methodology. Scrum, Kanban, and Extreme Programming (XP) are the frameworks and methods built on it.

Apply the prescriptiveness test to any item. If the document tells the team what to do, in what order, with which template, it behaves as a methodology. If it tells the team what to consider, it behaves as a framework.

What are examples of project management frameworks and methodologies side by side?

The 8 most-used examples split into 3 frameworks, 4 methodologies, and 1 mindset. The table classifies each by type, origin, and defining components.

Name	Type	Origin	Defining components
PMBOK Guide	Framework	PMI	12 principles and 8 performance domains (7th Edition)
Scrum	Framework	Schwaber and Sutherland	3 accountabilities, 5 events, 3 artifacts
SAFe	Framework	Scaled Agile, Inc.	Agile at team, program, and portfolio level
PRINCE2	Methodology	UK government	7 principles, 7 themes, 7 processes
Waterfall	Methodology	Software engineering	5 sequential phases with gates
Six Sigma	Methodology	Motorola	DMAIC, 5 phases
Lean	Methodology	Toyota Production System	Waste elimination
Agile	Mindset	Agile Manifesto, 2001	4 values and 12 principles

How do you choose between a framework and a methodology?

Choose a methodology when requirements are fixed, regulation is heavy, and repeatability is the goal. Choose a framework when requirements evolve, stakeholders collaborate daily, and the team needs room to adapt. Score the project on 6 factors.

Follow these 6 steps:

1. Assess project complexity and risk. High-risk work favors a methodology.
2. Measure requirement stability. Locked scope favors predictive methods, and shifting scope favors adaptive frameworks.
3. Check regulatory and contractual demands, such as audit trails and formal sign-offs.
4. Evaluate team experience. A team new to Agile needs coaching before it carries a framework’s decision load.
5. Confirm stakeholder expectations for documentation and involvement.
6. Match the industry norm: construction and government lean on methodologies, and software teams lean on frameworks.

Can a project use a framework and a methodology together?

Yes. Organizations layer them: a framework supplies the structure, a methodology supplies the procedures, and techniques supply the calculations. Scrum runs inside SAFe, and a PMO builds its own methodology on top of PMBOK Guide practices.

Three combinations appear in practice:

• PMBOK Guide plus an in-house methodology: the PMO converts general good practice into mandatory templates, gates, and approval levels. Study the PMBOK Guide and other PMI standards to see which standards a PMO draws from.
• Scrum inside SAFe: teams run Sprints while the enterprise coordinates through Program Increments.
• Predictive plan with adaptive delivery: a fixed budget and milestone schedule wraps iterative development. Hybrid project management formalizes this blend.

Each layer answers a different question. The framework answers “how do we think about this project?” The methodology answers “which steps do we follow?” The technique answers “how do we calculate the schedule?”

Which one does the PMP exam test?

The PMP exam tests approach selection, not memorized labels. The 2026 exam content outline puts roughly 60% of questions in agile and hybrid contexts and asks candidates to pick the right approach for a scenario.

Candidates meet predictive, agile, and hybrid scenarios in the same exam. The question stems describe a project and ask which approach fits. The framework-versus-methodology distinction sharpens that choice. A scenario with fixed scope and regulatory sign-offs points to a methodology. A scenario with evolving requirements points to an adaptive framework.

Build this judgment with instructor-led practice. A PMP boot camp from Project Management Training Institute drills approach-selection scenarios across predictive, agile, and hybrid cases.