TWRT Image
Home » TWRT » Project Management Methodologies: Scrum, Kanban, PMBOK, Waterfall, and Hybrid

Project Management Methodologies: Scrum, Kanban, PMBOK, Waterfall, and Hybrid

By / / 8-minute read

Introduction

Methodology = the way you organize, plan, and execute projects.

Choosing the right methodology is just as important as choosing the right tool. An inappropriate methodology = chaos, delays, and frustration.

This article compares the four main ones:

  • Waterfall: Sequential, with full planning at the outset
  • PMBOK: Traditional, with a focus on processes and documentation
  • Scrum: Agile, iterative, team-driven
  • Kanban: Continuous, flow, pull-based

One more bonus: Hybrid Agile (a combination of the two).

Quick Overview

Methodology Philosophy Rhythm Planning Flexibility Best For
Waterfall Sequential (linear) Slow 100% upfront Cancellation (expensive change) Fixed-price projects (construction)
PMBOK Processes + Documentation Medium 70–80% upfront Average (gates allow for changes) Corporate, Compliance
Scrum Iterative, time-driven Quick 10% upfront + 90% in installments High (changes with each sprint) Development, innovation
Kanban Continuous flow, pull Quick Minimum Very high (changes constantly) Support, Operations, Maintenance

Waterfall in Depth

What is

Waterfall = the project flows “top-down” like a waterfall. Each phase is fully completed before the next one begins.

Requisitos → Design → Desenvolvimento → Testes → Deploy → Suporte
(2 meses)  (1 mês)    (3 meses)      (1 mês)  (1 dia)  (forever)
↓          ↓          ↓              ↓       ↓
Completa  Completa   Completa      Completa Completa

Features

✧ Advantages:

  • Clear planning (you know exactly what to do)
  • A reliable estimate (if planned properly)
  • Excellent documentation
  • Ideal for projects with fixed requirements

❗ Limitations:

  • Change is expensive (finding an error in testing = having to redo everything)
  • Customer feedback comes late (only upon delivery)
  • High risk (it all depends on proper planning)
  • It doesn't work if the requirements change

When to Use

✅ Construction, hardware, government projects (fixed requirements)
✅ Complex integrations with legacy systems
✅ When change is impossible (irrevocable final delivery)

❓ Software development (always changing)
❓ Startups (frequent pivots)
❓ When users don't know exactly what they want

Real-Life Example

Projeto: Construir novo prédio (escritório)

Waterfall funciona:
Arquitetura → Engenharia → Construção → Finalização → Entrega
Requisito: "Prédio com 5 andares, 100 salas, 2 elevadores"
Mudança (ex: "quer 3 elevadores agora?") = muito caro, refaz tudo

Se usasse Scrum:
Sprint 1: Funda 1 andar
Sprint 2: Constrói andar 2, cliente vê e fala "muda as janelas"
Sprint 3: Janelas mudadas, cliente vê outro problema...
= Projeto levaria MUITO mais tempo

Moral: Para construção, Waterfall faz sentido.

PMBOK in Depth

What is

PMBOK = “Project Management Body of Knowledge.” A methodology developed by the PMI that focuses on processes, documentation, and governance.

There are 10 areas of knowledge:

  1. Integration
  2. Scope
  3. Schedule
  4. Cost
  5. Quality
  6. Appeal
  7. Communication
  8. Risk
  9. Acquisition
  10. Stakeholder

Features

✧ Advantages:

  • Accepted in corporations (global standard)
  • Certification (PMP = career)
  • Well-defined processes
  • Excellent for large, multi-phase projects
  • Clear Governance

❗ Limitations:

  • Cumbersome (a lot of paperwork)
  • Slow (many processes)
  • It isn't agile (it doesn't work well with rapid changes)
  • High implementation cost

When to Use

✅ Corporate projects > R$ 1M
✅ Multiple teams, multiple stakeholders
✅ Compliance / regulatory (requires documentation)
✅ Industry (aerospace, defense, pharma)

❌ Startups (overhead demais)
❌ Equipes pequenas (< 10 pessoas)
❌ Inovação rápida (Scrum é melhor)

Real-Life Example

Projeto: Implementar SAP em multinacional

PMBOK funciona:
- Charter bem-definido
- 10 áreas de processo documentadas
- Risk register (muitos riscos em SAP)
- Stakeholder management (CEO, CFO, CIO, todos envolvidos)
- Comunicação formal (atas de reunião, aprovações)

Se usasse Scrum:
- SAP tem muitos requisitos
- Seria complexo refatorar a cada sprint
- Implementador SAP quer planejamento claro

Moral: Para SAP, PMBOK faz sentido.

Scrum in Depth

What is

Scrum = an agile methodology focused on rapid iteration (sprints), customer feedback, and team self-organization.

Cycle: Planning → Sprint (1–4 weeks) → Review → Retro → Repeat

Features

✧ Advantages:

  • Quick feedback (the client sees results every sprint)
  • Flexible (priorities change with each sprint)
  • Motivation (the team sees steady progress)
  • Innovation (experiment, learn, pivot)

❗ Limitations:

  • Inaccurate estimate (at first)
  • Minimum documentation (user stories, not a 100-page specification)
  • Requires a dedicated Product Owner
  • It can get chaotic without discipline

When to Use

✧ Software development (core use case)
✧ Startups (things change quickly, feedback is needed)
✧ Innovation (exploring new markets)
✧ When requirements aren't 100% clear

❌ Projects with completely fixed requirements
❌ Large corporations (very rapid change causes chaos)
❌ When the client is unable to participate (dedicated PO)

Real-Life Example

Projeto: App mobile de delivery

Scrum funciona:
Sprint 1: Login + busca de restaurantes
Cliente testa, fala: "Quero filtro de categoria"
Sprint 2: Filtro adicionado
Cliente: "Quero carrinho de compras"
Sprint 3: Carrinho
...

Agilidade = cada sprint atualiza direção baseado em feedback

Se usasse Waterfall:
Especificaria TUDO no início (login, busca, filtro, carrinho, pagamento, histórico, review, etc.)
Entregaria 4 meses depois
Cliente: "Isso não é o que eu queria..."
= Retrabalho massivo

Moral: Para app, Scrum faz sentido.

Kanban in Depth

What is

Kanban = “visual board” with continuous flow. There are no sprints; work flows constantly.

Based on a “pull” approach (people take on work when they have the capacity), not a “push” approach (someone assigns work).

TO-DO         IN PROGRESS    IN REVIEW    DONE
(Backlog)     (max 3)        (max 2)      (Completed)

[Task A]      [Task D]       [Task G]     [Task I]
[Task E]       [Task H]     [Task J]
[Task B]
[Task C]      [Task F]

Features

✧ Advantages:

  • Simple (visually appealing, easy to understand)
  • Continuous flow (no downtime between sprints)
  • Continuous delivery (does not accumulate work)
  • Adaptable (changes priorities without “disrupting” the sprint)

❗ Limitations:

  • No explicit deadline (when will it end?)
  • Velocity is variable (there is no sprint)
  • Difficult to explain to executives (“When will this end?”)
  • Requires strict WIP limits (otherwise it turns into chaos)

When to Use

✅ Support / Help Desk (tickets come in constantly)
✅ Operations / Maintenance (ongoing demand)
✅ When you need to respond quickly to changes
✅ No strict deadline

❌ Projects with a fixed deadline (you need to know “when”)
❌ When you need to coordinate multiple teams (sprints help)
❌ Product development (requires phasing)

Real-Life Example

Projeto: Suporte técnico (help desk)

Kanban funciona:
Tickets chegam constantemente
Time pega do backlog quando tem capacidade
WIP limit = 5 (não mais de 5 tickets simultâneos)
Ticket é resolvido, vai para DONE, time pega próximo

Fluxo é contínuo, nada fica esperando muito tempo

Se usasse Scrum:
Sprint 1: Selecionamos 20 tickets
Sprint 2: Mas 30 tickets novos chegaram...
Fila de espera cresce
= Não funciona bem

Moral: Para suporte, Kanban faz sentido.

Hybrid Agile

What is

It combines the best of two or more methodologies. Example:

Scrum with Waterfall:

  • Planning and Design (Waterfall: 2 sprints, well planned)
  • Development (Scrum: iterative, multiple sprints)
  • Testing (Waterfall: separate phase)
  • Deploy (Waterfall: Coordinated)

Kanban with Scrum:

  • Sprint Goals (Scrum)
  • Visual Flow + WIP Limit (Kanban)

When to Use

✅ Large corporations with multiple teams
✅ When part of the process is fixed (design) and part is flexible (development)
✅ When you need documentation (PMBOK) + agility (Scrum)

Real-Life Example

Projeto: Novo produto (SaaS)

Hybrid Agile:
Fase 1 (Waterfall): Discovery + Design (cliente co-cria, bem definido)
Fase 2 (Scrum): MVP development (10 sprints, feedback constante)
Fase 3 (Scrum): Scaling (mais features, mais sprints)
Fase 4 (Kanban): Suporte (bugs + melhorias, contínuo)

Moral: Real projects are never 100% one methodology.

Decision Matrix

                    Requisitos Claros?
                  SIM            NàƒO
            ┌──────────────────────────┐
    Projeto    │  WATERFALL  │   SCRUM    │
Fixo       │  (ou PMBOK) │  Híbrido   │
│             │            │
Mudanças   │   PMBOK     │   SCRUM    │
Frequentes │  (com gates)│            │
│             │            │
Contínuo   │   KANBAN    │   KANBAN   │
(Help desk)│             │            │
└──────────────────────────┘

When to Use Which

Quick Pick (1 question)

Q: Are there requirements in your project that might change?

→ YES = Scrum or Kanban
→ NO = Waterfall or PMBOK

Q: Does your project have a fixed deadline?

→ YES = Scrum or Waterfall
→ NO = Kanban

Q: How many people?

→ < 10 = Scrum ou Kanban
→ > 50 = PMBOK ou Hybrid

Common Mistakes

Mistake 1: “Let’s use Scrum for everything”

❗ Scrum doesn't work for support (you need Kanban).
Scrum doesn't work for construction (you need Waterfall).

✧ Choose based on the nature of the project.

Mistake 2: Implementing the wrong methodology

❓ “Let’s go Agile!” → Implements Scrum without a Product Owner.
Result: Chaos (lack of prioritization).

✧ If you're using Scrum, hire a dedicated Product Owner.

Mistake 3: Changing the methodology midway through the project

❌ “We started with Waterfall; now we’re going to use Scrum.”
Result: Replanning, delays.

✧ Make your choice right from the start; commit to it.

Checklist

  • [ ] Are the requirements clear? (YES/NO)
  • [ ] Does the project have a fixed deadline? (YES/NO)
  • [ ] Team size? (# of people)
  • [ ] How often do you change it? (never/rarely/sometimes/often)
  • [ ] Sector / industry? (construction/software/operations/other)
  • [ ] Methodology selected based on a matrix
  • [ ] Team trained in the methodology
  • [ ] Documented processes (using the chosen methodology)
  • [ ] Configured tools (Jira for Scrum, Trello for Kanban, etc.)

Quick Comparison (Table)

Appearance Waterfall PMBOK Scrum Kanban
Planning 100% upfront 70% upfront 10% upfront Minimum
Change Man Custosa (gates) Cockroach Free
Documentation Heavy Heavy Lightweight Minimum
Speed Slow Average Quick Quick
Feedback In the end By gates Every sprint Continuous
Ideal Team Sequential Corporate Cross-functional Flexible
Timeline Predictable Controlled Variable Continuous
Complexity Upfront Check-in (cases) Average (sprints) Low (visual)

FAQ

Q: What is the “best” methodology?

A: None. It depends on the project. Scrum is popular in the tech industry, but it doesn't work for everything.

Q: Can I combine different methodologies?

A: Yes (Hybrid). But be consistent—don't change it halfway through the project.

Q: Is the PMBOK obsolete with Agile?

A: No. Large corporations use PMBOK. Agile is a framework; PMBOK is a body of knowledge.

Final CTA

Choosing the right methodology is the first step. If you're unsure which one to use for your project, schedule a 45-minute session to help you decide. Otherwise, download the decision matrix and make your choice today.

Upcoming readings:
Implementing Scrum | How to Implement Project Management in 30 Days

Related Content

author's avatar
See Full Bio

Related Articles

Scroll up