By Décio Dalke Jr. · Sep 2026 · Leia em português

World 1 of Projects, level 5: the castle

PMBOK is a guide; whoever manages chooses the method. Agile plans too. Scrum is one specific way to play. When each approach fits, and what's left of the four previous levels in any of them.

Part 5 of 5 of the series World 1 of Projects.

Predictive, agile or hybrid? — pixel-art stone castle with an orange flag

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).

World 1 of Projects series — level 5 of 5: World 1-1 · World 1-2 · World 1-3 · World 1-4 · World 1-5

The castle is where project management discussions usually start. PMBOK or agile? Scrum or waterfall? Which methodology should the company adopt?

That’s why it sits at the end of this world. Arguing about how to play before knowing the rules of the game is like picking the controller before knowing which game you’re going to play.

What is the PMBOK, and what isn’t it?

The PMBOK is the reference guide published by PMI. The 8th edition came out in November 2025, organised into six principles and seven performance domains: governance, scope, schedule, finance, stakeholders, resources and risk [1].

What it isn’t: a methodology. It brings together what the profession has learnt about what needs looking after in any project, without a step-by-step for your company’s project. How to look after it is the choice of whoever manages it.

Notice that the list of domains is, to a large extent, this whole world: scope (World 1-2), schedule, resources and finance (World 1-3), and the control that runs through all of it (World 1-4).

So what did agile actually change?

The Agile Manifesto, from 2001, is a short list of preferences. One of them: responding to change is worth more than following a plan. And the manifesto ends with a sentence almost nobody quotes: the things it values less, like the plan, also have value [2].

In other words: agile always allowed for a plan; what it said, though, is that the ability to change it when you learn something new is worth more than the plan itself.

Scrum, the best-known agile way of working, is described by its own authors as a lightweight framework, with cycles (sprints) of one month or less, and purposefully incomplete: it defines only the minimum and leaves the rest to whoever uses it [3].

What really changes is the size of the cycle. Instead of planning everything and delivering at the end, you plan the next piece, deliver it, learn, and plan the one after.

When does each approach fit?

The right question is: how much does it cost to change the scope once you’ve started?

  • Predictive (plan everything first, execute afterwards): when the scope is well known and changing it midway is very expensive. A maintenance shutdown, a construction project, an office move. You don’t discover a building’s foundations by running sprints.
  • Agile (plan and deliver in short cycles): when the scope can only be discovered by doing, and change is cheap. Software, a new product, a campaign that adjusts to the market’s response.
  • Hybrid: when the project has parts of both natures. The infrastructure planned end to end; the system that runs on top of it, in cycles.

What happens a lot is a company wanting an agile project. The full package, with sprints, backlogs, user stories. It has only an idea, “I want a logistics control system”, and not much beyond that; even so, it wants a fixed-price package. Frozen price, spot-on estimate.

Those two don’t go together. In World 1-1 we saw the three forces of a project: scope, time and resources. If I freeze one of them, the others have to stay open to vary.

Think of a multiplication. If I freeze the result at 20, I have to accept that the other two numbers can be 2 and 10, or 4 and 5. I can’t freeze it at 20 and hammer the other two into place.

The maths doesn’t add up.

What’s left of the four levels in any of them?

Everything.

  • Scope still exists. In agile it’s called the backlog, and it still needs someone to say what goes in and what stays out.
  • Breakdown still exists. A story that doesn’t fit in one cycle is a piece of the WBS that hasn’t gone down far enough.
  • The snapshot of the agreement still exists, although it changes size: instead of the whole project, it’s the commitment for each cycle.
  • Control still exists. A sprint’s remaining-work chart is a close relative of the S-curve from World 1-4.

Whoever switches methodology thinking they’ll get rid of the rules finds they’ve only swapped the controller in their hands.

What now?

In the castle, there are two ways to beat the boss: hit him with fireballs until he falls, or get past him and reach the axe at the end of the bridge. They’re different paths through the same castle, with the same rules. That’s what predictive, agile and hybrid are.

This world taught the rules. The next world in this section gets into technique: how to calculate dates with PERT and the critical path, what to do when resources call the shots more than the sequence does, how to measure output and productivity, and what to do when the client wants a fixed-scope price with open-scope deliveries.

Press play!

Quick questions

Is the PMBOK a methodology? No. It’s PMI’s reference guide to what needs looking after in any project. How to look after it is each organisation’s choice.

Does agile mean having no plan? No. The Agile Manifesto values responding to change more than following a plan, but it says in so many words that the plan also has value.

When should you use predictive or agile management? It depends on how much it costs to change the scope once you’ve started. If it’s expensive, predictive; if the scope can only be discovered by doing, agile; if the project has both natures, hybrid.

What is Scrum? An agile way of working with cycles of one month or less. Its own authors describe it as a lightweight, purposefully incomplete framework.

References

  1. PMI — PMBOK® Guide, Eighth Edition. https://www.pmi.org/standards/pmbok — accessed 2026-09-25.
  2. Manifesto for Agile Software Development (2001). https://agilemanifesto.org/ — accessed 2026-09-25.
  3. Schwaber, K.; Sutherland, J. (2020). The Scrum Guide. https://scrumguides.org/scrum-guide.html — accessed 2026-09-25.