“We need to become agile.” You usually hear this when a project has gone off track, a competitor is moving faster, or a consultant has just sold the company on Scrum training. The problem: Agile isn't the solution to every problem. Sometimes it is the problem.
The question to ask before choosing any methodology is: What kind of work are we doing, and which approach supports it best?
Comparing the three approaches
When agile actually works
Agile works when four conditions are met:
- The goal is clear, but the path to get there is unknown.
- Customer feedback can be gathered regularly (every 1–2 weeks).
- The team can make decisions autonomously.
- Requirements can change without blowing the budget.
Agile fails in environments where the scope is fixed (public tenders), where regulatory requirements turn every sprint completion into a documentation obligation, or where the team can't handle priorities that change every day.
When traditional project management makes more sense
Traditional waterfall project management isn't outdated. It's appropriate in contexts such as:
- Construction and infrastructure: Where changes become exponentially more expensive once work has started.
- MedTech regulatory approvals: Where regulatory requirements impose sequential documentation.
- ERP implementations: Where the scope must be defined from the start.
- Production ramp-up: Where quality milestones must be met in sequence.
Hybrid: the most realistic approach
Most companies operate with a hybrid approach, and that's perfectly legitimate. A GTM launch has a traditional planning phase (defining scope, allocating resources, and setting milestones) and an iterative implementation phase (pilot, feedback, adjustments, and rollout).
The problem isn't hybrid itself. It's failing to recognize how the team actually works. If a team believes it's working in an agile way, but every requirement comes from management and no real sprints take place, that's not hybrid. It's waterfall with poor documentation.
“The best methodology isn't the most popular one. It's the one your team can actually execute with the resources it has.”
How to choose the right methodology: 5 questions
- Are the requirements fully known at the start? → Yes: traditional. No: agile.
- Can the team get customer feedback every week? → Yes: agile. No: hybrid or traditional.
- Is the budget fixed or the output fixed? → Fixed budget: traditional. Fixed output: agile.
- Are there regulatory or compliance requirements? → Yes: traditional or structured hybrid.
- How experienced is the team at working autonomously? → Experienced: agile. Inexperienced: structure first, then autonomy.
Introducing Agile without clarifying who makes the decisions. Agile only works when the team has the authority to make decisions. In other words, when it's empowered. Agile without empowerment is Scrum theater: stand-ups, sprint reviews, and no meaningful difference from how things worked before.
The methodology isn't the goal. The goal is a team that delivers, learns, and adapts. The context determines which approach gets you there. Not the latest trend.
Published June 2026