Predictive, agile or hybrid: how to choose your project approach

One of the most important decisions in a project is made before it even starts: which approach you are going to use. The PMBOK 7 recognizes three of them, and it does not crown any one as the best. The best is the one that fits your project. Here is the real difference and how to decide.

Predictive

The predictive approach, sometimes called waterfall, plans the full scope up front and executes it in sequential phases. It works when you know well what you have to build and it is unlikely to change.

A typical example: a civil construction project or a migration with stable requirements. Its strength is predictability. Its weakness is rigidity: if the scope changes a lot, the plan suffers.

Agile

The agile approach delivers in short cycles, learns from each delivery and adjusts course. It works when there is high uncertainty, when the client discovers what they want as they see it, or when technology changes quickly.

A typical example: a new digital product. Its strength is adaptation. Its weakness is that it requires available clients and mature teams, and it is hard to commit to a fixed date and cost from day one.

Hybrid

The hybrid approach combines the two. A stable part is managed in a predictive way, and an uncertain part is managed in an agile way. It is the most common option in practice, because almost no real project is one hundred percent predictable nor one hundred percent exploratory.

A typical example: implementing a system with a fixed infrastructure (predictive) and an interface that is refined with the user (agile).

How to choose

Do not marry a trend. Ask yourself these questions:

• How clear is the scope? Very clear and stable, predictive. Vague and changing, agile.
• How often can you deliver value? If you can deliver in useful chunks, agile suits you.
• How available is the client? Agile needs their constant participation.
• What does the environment demand? Rigid contracts, audits or regulation can push you toward predictive.
• How mature is the team? Agile performs best with autonomous, disciplined teams.

The honest answer is almost always a tailored hybrid. That, once again, is tailoring: you adapt the approach to the project, not the project to the approach.

How it shows up on the exam

The exam will give you a scenario and options that represent different approaches. The key is in the context clues: uncertainty, delivery frequency, type of client. There is no correct approach in the abstract, only the correct one for that case. Read carefully before you choose.

Join the waitlist

At The PM Architect we explain the three approaches with real cases and examples of when to use each one. The books will be free: leave your email on the home page and we’ll let you know when they’re available.