Project Management Frameworks: Five Approaches and How to Choose

Choosing a project management framework is not a matter of finding the most fashionable label. It is a design decision: how will the team plan, deliver, review and control work in the conditions it actually faces?

The terminology can be confusing. Waterfall, Scrum, Kanban, Lean and the Critical Path Method are often grouped together as project management frameworks, but they do not all perform the same job. One may shape the project life cycle, another may organise a team's work, and another may help build the schedule.

This guide compares five widely used approaches and techniques, explains when each is useful and shows how to combine them without creating an incoherent process.

A project management framework provides enough structure for people to make consistent decisions about project work. Depending on the context, it may define stages, roles, events, controls, artefacts, workflows or decision rules.

In everyday business language, “framework”, “methodology” and “method” are often used interchangeably. For practical selection, however, it helps to distinguish the level at which each concept operates.

This distinction prevents a common mistake: treating every option as a mutually exclusive system. A predictive project can use Lean principles and CPM scheduling. A Scrum team can also use Kanban practices to improve flow.

1. Predictive or Waterfall Delivery

Waterfall is a common name for a linear, predictive life cycle. The team aims to understand the scope early, plan the sequence of work and move through defined stages, with changes assessed through a controlled process.

A strong fit when:

• the required output can be defined with reasonable confidence;
• work has clear technical or contractual dependencies;
• formal approvals, audit evidence or stage gates are important;
• the cost of late change is high.

Construction packages, infrastructure work and regulated implementations may use predictive elements because sequence, assurance and contractual control matter. Predictive does not have to mean excessive documentation; governance should still be tailored to the project's risk and complexity.

Main risk: early plans may create false certainty. If customer needs or the solution are still emerging, locking detailed scope too soon can make learning slow and change expensive.

2. Scrum

Scrum is an Agile framework for complex work. A Scrum Team works towards a Product Goal and delivers a usable Increment through time-boxed Sprints. Its accountabilities, events and artefacts create regular opportunities to inspect results and adapt.

A strong fit when:

• the problem is complex and the solution must develop through learning;
• stakeholders can provide frequent feedback;
• a stable, cross-functional team can deliver increments;
• the work can be prioritised around product value.

Scrum is most useful when the organisation supports its core design rather than adopting only the vocabulary. Daily meetings alone do not make a team Agile, and a list of tasks is not necessarily a Product Backlog.

Main risk: using Scrum where the team cannot produce meaningful increments or where decision-makers are unavailable. It also becomes ineffective when every Sprint is interrupted by unmanaged urgent work.

For a deeper explanation of iterative delivery, see LOTC's guide to Agile project management.

3. Kanban

Kanban is a strategy for optimising the flow of value through a process. Teams define and visualise their workflow, actively manage work items and improve the flow. Work-in-progress limits are especially valuable because they expose bottlenecks and discourage starting more work than the system can finish.

A strong fit when:

• work arrives continuously rather than in planned batches;
• priorities can change frequently;
• the team needs to reduce waiting time and congestion;
• an existing process should improve without a wholesale reorganisation.

Service operations, maintenance, support, compliance reviews and mixed-demand teams often benefit from Kanban. It can also complement Scrum by helping a team understand flow within and across Sprints.

Main risk: treating the board as the method. Visualising tasks helps, but improvement requires explicit workflow policies, active management and meaningful flow measures—not simply moving cards between columns.

4. Lean Thinking

Lean is a management philosophy centred on customer value, the value stream, flow, pull and continuous improvement. It asks teams to see work end to end, remove activity that does not contribute value and improve the system rather than optimise isolated departments.

A strong fit when:

• delays and hand-offs are reducing delivery performance;
• the organisation needs to remove waste and simplify a process;
• customer value is poorly connected to day-to-day activity;
• improvement must extend across several teams or functions.

Lean can influence any project approach. For example, a predictive programme can map its approval value stream, while a Scrum team can use Lean thinking to reduce queues between development, testing and release.

Main risk: reducing Lean to a cost-cutting exercise. Removing capacity without improving the system can increase queues, risk and rework rather than create value.

5. Critical Path Method (CPM)

The Critical Path Method is a scheduling technique, not a complete delivery framework. It models activity durations and logical dependencies to identify the longest path through the schedule. A delay on that path can delay the planned project completion date unless corrective action changes the schedule logic or duration.

A strong fit when:

• activities have significant dependencies;
• a committed completion date must be tested;
• planners need to understand schedule sensitivity and float;
• several contractors, work packages or technical sequences must be coordinated.

CPM is particularly relevant to engineering, construction, shutdowns, events and complex implementation schedules. It can support predictive or hybrid delivery and can sit above iterative team-level plans.

Main risk: assuming the calculated path is realistic without checking resource availability, calendar constraints, estimates and schedule logic. A technically correct network can still be an unreliable management plan if its inputs are weak.

Start with the characteristics of the work, not the preference of the project manager.

1. How stable are the requirements?

When the output and acceptance criteria are well understood, predictive planning may provide useful control. When the team needs experimentation and feedback to discover the right solution, an adaptive approach such as Scrum is more suitable.

2. Is the work project-based or continuous?

Scrum works around goals and increments delivered through Sprints. Kanban is often a better starting point for a continuous stream of requests, incidents or small changes that cannot wait for the next planning cycle.

3. Where is the main delivery constraint?

If congestion, waiting and hand-offs are the problem, use Kanban and Lean practices to examine flow. If the main risk is a network of time-dependent activities, CPM can reveal which sequence currently governs the completion date.

4. What level of governance is required?

Contracts, safety, public accountability and regulation may require baselines, approvals and traceable change control. These needs do not automatically exclude Agile delivery. A hybrid model can retain governance at programme level while teams deliver and learn iteratively.

5. Can the organisation support the chosen approach?

A framework cannot compensate for unavailable decision-makers, fragmented teams or incentives that reward local performance over project value. Check sponsorship, skills, decision rights, team capacity and access to customers before designing the process.

Hybrid project management combines linear and iterative elements according to the work. It should be a deliberate operating model, not a collection of ceremonies and documents inherited from several methods.

Consider a regulated organisation launching a new customer portal:

• programme funding, procurement and assurance may follow predictive stage gates;
• a product team may use Scrum to test and deliver customer-facing features;
• an operational team may use Kanban for defects and service requests;
• Lean analysis may simplify the approval value stream;
• CPM may coordinate infrastructure, data migration, training and the final cutover.

These practices are not competing for one label. Each addresses a different management need. The important questions are who makes decisions, how work moves between layers, which artefacts are authoritative and how changes affect the overall plan.

The PMP exam does not require candidates to treat five named frameworks as a fixed syllabus. PMI's PMP Examination Content Outline effective from July 2026 applies predictive, adaptive/agile and hybrid approaches across all three exam domains. It also expects candidates to assess project needs and recommend an appropriate development approach.

For PMP preparation, focus on situational judgement:

• recognise whether the environment is predictive, adaptive or hybrid;
• understand why the approach fits the project's uncertainty and constraints;
• select practices and artefacts that support the situation;
• tailor governance without removing necessary control;
• understand how a decision affects people, process and business value.

The current outline indicates that approximately 40% of exam items represent predictive approaches, while the remaining 60% are divided between adaptive/agile and hybrid approaches. Candidates should always check the latest official PMP Examination Content Outline before building a study plan.

• Choosing by popularity: a well-known framework is not automatically suitable for the work.
• Confusing a technique with a delivery system: CPM strengthens scheduling but does not define roles, governance, risk management or stakeholder engagement.
• Copying ceremonies without purpose: stand-ups, boards and Sprints must support decisions and value delivery.
• Ignoring organisational constraints: the theoretical fit fails if the team lacks capacity, authority or stakeholder access.
• Creating accidental hybrid delivery: combining every document and ceremony increases overhead unless interfaces and decision rights are clear.
• Refusing to tailor: neither predictive nor Agile practice should be applied mechanically when the context requires proportionate adaptation.

Understanding labels is useful; applying them to scope, schedule, risk, stakeholders and delivery decisions is what builds professional capability.

LOTC's Project Management Fundamentals course introduces the project life cycle and core management practices. Teams can also explore LOTC's wider range of project management courses to find training suited to their responsibilities and delivery environment.

1. What is the best project management framework?

There is no universal best framework. Predictive delivery suits relatively stable work that needs structured control; Scrum supports complex product work and frequent feedback; Kanban helps continuous flow; Lean improves end-to-end value; and CPM analyses schedule dependencies. Many organisations use a deliberate hybrid.

2. Is Agile a project management framework?

Agile is better understood as a family of values, principles and adaptive ways of working. Scrum is a specific Agile framework. Kanban can support Agile delivery, but it is a flow strategy rather than a synonym for Scrum.

3. Is Waterfall a framework or a methodology?

Waterfall commonly describes a linear or predictive life-cycle approach in which work progresses through planned stages. Organisations may build their own governance framework and detailed methodology around that approach.

4. Can Scrum and Kanban be used together?

Yes. A Scrum Team can retain Scrum's accountabilities, events and artefacts while using Kanban practices and flow measures to improve how work moves through the system.

5. Is the Critical Path Method a project management framework?

No. CPM is a scheduling technique used to model dependencies and identify the sequence that determines the planned completion date. It can be used within predictive or hybrid project delivery.