Search on website

What Are Agile, Scrum and Waterfall in Project Management? A Beginner’s Guide
  • July 23, 2026
  • News
What Are Agile, Scrum and Waterfall in Project Management? A Beginner’s Guide

If you’ve looked at a Project Management job ad recently, you’ll have seen the same three words come up time and time again: Agile, Scrum and Waterfall. They’re often listed together as though they’re interchangeable — and they’re not. One is a mindset, one is a specific framework built on that mindset, and one is a traditional, sequential way of running work that predates both.

Employers don’t just want someone who can name them. They want someone who knows which approach suits which project, and why. Here’s what each one actually is.

Waterfall: plan first, then build

Waterfall is the traditional approach, and it’s named for the way work flows downward through fixed stages, each one signed off before the next begins:

  • Requirements
  • Design
  • Build
  • Test
  • Deploy
  • Maintain

Its strength is certainty. Because everything is planned up front, you know at the outset what the project will deliver, what it should cost and when it should finish. Documentation is thorough and progress is easy to report.

Its weakness is the flip side of the same coin. Waterfall assumes you know what you need before you start and that those needs won’t change. When requirements shift halfway through — as they often do in software — going back is expensive. You also don’t get anything usable until near the end, so problems can stay hidden for months.

It still makes complete sense for construction, manufacturing, regulated industries and anything where requirements are genuinely fixed. Nobody pours the foundations of a building and then decides to iterate on the number of floors.

Agile: adapt as you go

Agile emerged as a response to those limitations. In 2001, seventeen software practitioners published the Agile Manifesto, setting out a different set of priorities:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

The crucial word is “over.” Agile doesn’t say planning and documentation are worthless — it says that when you have to choose, favour the first item.

In practice, that means breaking a large project into small pieces and delivering them in short cycles, usually one to four weeks. At the end of each cycle you have something that works, however small. You show it to the customer, gather feedback, and let that shape the next cycle. Instead of one enormous plan that must survive contact with reality, you get dozens of small course corrections.

One thing to be clear on: Agile is a mindset, not a method. It tells you what to value, not what meetings to hold. That’s where Scrum comes in.

Scrum: the most widely used Agile framework

Scrum turns Agile principles into a specific, repeatable way of working. When a job ad mentions Agile experience, Scrum is usually what’s meant in practice.

Work is organised into sprints — fixed-length cycles, most often two weeks, in which the team commits to delivering a defined set of work. Everything else supports that rhythm.

The three roles:

  • Product Owner — owns the backlog, decides what matters most, represents the customer
  • Scrum Master — not a boss but a facilitator, removing obstacles and protecting the process
  • Development Team — builds the product and self-organises how the work gets done

The four ceremonies:

  • Sprint planning — agrees what the team will take on
  • Daily stand-up — a fifteen-minute check-in on progress and blockers
  • Sprint review — demonstrates completed work to stakeholders
  • Retrospective — asks what went well, what didn’t, and what changes next sprint

The three artefacts:

  • Product backlog — everything that might be built, prioritised
  • Sprint backlog — what’s being built right now
  • Increment — the working product at the end of the sprint

None of this is complicated on paper. What makes Scrum hard is the discipline: protecting the sprint from interruptions, keeping the backlog genuinely prioritised, and treating retrospectives as more than a box-ticking exercise.

So which one should you use?

It depends on how much uncertainty you’re dealing with.

Waterfall suits projects where:

  • Requirements are stable and well understood
  • Regulation or contracts demand detailed documentation
  • The sequence of work is physically fixed
  • Stakeholders need a firm date and price from the start

Agile and Scrum suit projects where:

  • Requirements are likely to evolve
  • You can get real feedback from users along the way
  • The team is small enough to collaborate closely
  • Delivering something usable early beats getting everything right first time

In reality, many organisations run a hybrid — Waterfall-style planning and governance at programme level, with Agile delivery inside the teams. Learning to read a project and pick the right approach, rather than applying one method to everything, is what separates a competent project manager from a genuinely good one.

Why it matters for your career

Project management skills travel further than almost anything else in tech. These frameworks are used in software, finance, healthcare, construction, marketing and product development, which means they open doors across industries rather than locking you into one.

They’re also increasingly expected of people who aren’t project managers at all. Developers, testers, designers and analysts all work inside sprints, attend stand-ups and contribute to retrospectives. Understanding why the process works the way it does makes you a stronger member of any team — and it’s often the first step towards leading one.


Want to put these frameworks into practice? Our Project Management course covers Agile, Scrum and Waterfall in depth, along with how AI is reshaping project delivery. Classes are delivered live online by a Senior Project Manager with real corporate experience, and you’ll complete a technical project in all three methodologies to demonstrate your new skills. Check out the details in the Courses Page.