Skip to content
Tutorials Center
My learning

Topics

Lesson 32 of 41 ยท Agile and Scrum

Choosing a Methodology

Compare waterfall, agile, Kanban, PRINCE2 and hybrid project approaches, learn their strengths and limits, and score which methodology fits your project, with Python.

There is no best project methodology, only a best fit for a given project, team and organization. Choosing well starts with knowing what each approach assumes about the work. This lesson compares the main families and gives you a simple way to pick one, or to blend them.

The main families

Four common approaches

Waterfall Sequential phases with sign-offs.
Agile Short cycles, feedback and change.
PRINCE2 Governed stages and business case.
Hybrid Plan like predictive, build like agile.

Each fits a different level of uncertainty.

1 / 2

Waterfall (predictive)

Work flows through phases: requirements, design, build, test, deploy, maintain. Each phase is complete and signed off before the next begins. It produces thorough documentation and a clear budget and schedule, and suits projects where requirements are known and stable, change is costly (construction, manufacturing, regulated hardware) and the team may be geographically spread.

Its weakness: the customer sees the product late, so misunderstandings are discovered when they are most expensive to fix, and late changes are painful.

Agile (adaptive)

Covered in the previous lessons: agile principles, Scrum and Kanban. Best when requirements are unclear or likely to change and when the customer can collaborate frequently. Weaknesses: harder to promise a fixed scope, date and price; needs engaged customers and empowered teams.

PRINCE2

PRINCE2 (PRojects IN Controlled Environments) is a process-based method widely used in the UK, Europe and public sector. It organizes a project into stages controlled by a project board, driven by a business case that is checked at every stage gate. Its seven principles include continued business justification, defined roles, management by stages, management by exception (the board only gets involved when tolerances are exceeded), a focus on products and tailoring to the project. It is not agile or waterfall by itself: PRINCE2 can host agile delivery inside its stages (PRINCE2 Agile).

PMBOK and the PMI view

The PMBOK Guide is a body of knowledge, not a method: it describes performance domains and principles and the PMP exam is based on it. The current edition places predictive, agile and hybrid approaches under one framework.

Hybrid

Many real projects combine approaches: a predictive frame (a fixed budget, milestones, governance) with agile delivery inside (sprints, backlog). For example, a hospital builds a new building (predictive) while the IT team builds the patient app (agile). Or a product team runs Scrum while the organization budgets annually.

Lean and Six Sigma

Lean removes waste (waiting, rework, handoffs) to maximize value; Kanban is a Lean tool. Six Sigma reduces variation using data (DMAIC: Define, Measure, Analyze, Improve, Control). Both inform quality work (see quality management).

Side-by-side

Aspect Waterfall Agile PRINCE2
Planning Detailed, up front Rolling, per iteration Stage plans plus project plan
Change Formal change control Welcome; reprioritize Controlled by tolerances and board
Customer involvement At phase gates Continuous Board and user reps at stages
Delivery One big release Frequent increments Products per stage
Documentation Heavy Lean Defined product descriptions
Risk Managed through plans Reduced by feedback Risk register and stage reviews
Best for Stable requirements Uncertain requirements Governed, multi-party projects

A simple way to choose

Ask five questions about the project, and score each from 1 (stable, predictable) to 5 (volatile, uncertain):

  1. How well are the requirements known?
  2. How likely are they to change?
  3. How costly is a mistake or late change?
  4. Can the customer give frequent feedback?
  5. How experienced is the team with this kind of work?

Low total scores point to predictive; high scores point to agile; the middle suggests hybrid.

Python Methodology fit score

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The scoring is a conversation tool, not a law. The important thing is that the team discusses why a project looks volatile or stable.

Comparing delivery profiles

One advantage of each approach is when the project spends money versus when it delivers value. A quick model:

Python Money spent versus value delivered by month

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice the cumulative value, not only the total. If the project is cancelled in month 6, the agile project has delivered something; the waterfall project has delivered nothing.

Tailoring and contracts

Rarely adopt a method "by the book". Tailor it to the context: keep the parts that solve your problems and drop ceremonies that add no value. Also, align the contract: fixed-price contracts fit predictive scope; time-and-materials or "fixed budget, variable scope" contracts fit agile work.

Common patterns of hybrid: water-scrum-fall (predictive requirements and release, Scrum build), stage-gated agile (agile in each stage, gates for funding), and scaled agile frameworks (SAFe, LeSS, Scrum of Scrums) for many teams. Scaling frameworks add coordination: shared backlogs, program increments, dependency boards. Start without them; add them when coordination pain is real.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which project is the best fit for a predictive approach?

    Stable, well-understood requirements and costly change favor predictive methods.
  2. 2. In PRINCE2, 'management by exception' means:

    Authority is delegated within tolerances; only deviations are escalated to the project board.
  3. 3. A hybrid approach typically combines:

    Hybrid keeps governance and milestones but delivers iteratively.
  4. 4. Which is a weakness of a pure waterfall approach?

    Late feedback means late discovery of misunderstandings, and changes then cost more.

Summary

  • Waterfall, agile, PRINCE2 and hybrid differ in how they handle planning, change and feedback.
  • Fit depends on requirement stability, cost of change, customer availability and team experience.
  • PRINCE2 and PMBOK are frameworks or bodies of knowledge that can host agile delivery.
  • Tailor methods, align contracts and add scaling only when coordination hurts.

Next: Project Management Tools