Another team meeting. Another slide comparing agile ceremonies to gantt charts. Another round of the same argument: should we "go agile," stay with the traditional plan, or land somewhere in between? The conversation is treated like a fork in the road - pick the right one and the project succeeds, pick wrong and it doesn't.
The data doesn't support that. Research from PMI's Pulse of the Profession finds that organizations have shifted toward flexible, fit-for-purpose project delivery practices, blending traditional predictive techniques with agile methodologies depending on what best suits the project and stakeholders.
And here's the part that should reframe the whole debate: project performance is roughly equal whether a team uses predictive, hybrid, or pure agile frameworks — provided the approach is applied with skill.
The Methodology Debate
For years this argument had real stakes. Waterfall dominated for decades - sequential phases, heavy documentation, fixed scope.
Agile arrived as a rebellion against exactly that rigidity, promising iteration and responsiveness.
Then hybrid emerged as the synthesis nobody planned but everyone backed into: take the governance and predictability of one, the adaptability of the other, and apply whichever fits the work in front of you.
The numbers show how far that shift has gone. PMI's Pulse of the Profession 2024 found predictive approaches still hold a commanding lead at 44%, with hybrid now the second most commonly used approach at 32%, while pure agile use actually fell two percentage points to 26%. Meanwhile hybrid adoption increased a striking 57.5% over three years, climbing from 20% of organizations in 2020 to 31.5% in 2023.
(https://www.pmi.org/blog/project-management-embraces-the-fit-for-purpose-approach)
Put those together and the picture is clear: this isn't a two-sided debate anymore. It's three approaches coexisting, chosen project-by-project rather than defended as ideology.
The Data that Undercuts the Debate Entirely
Here's where it gets interesting. If hybrid is surging and agile is dipping, you'd expect performance data to show hybrid teams pulling ahead. It doesn’t.
Teams succeed or struggle at similar rates regardless of which label sits on their process - the deciding factor is how well any given approach is executed, not which one was chosen.
That's a harder pill to swallow than "switch frameworks and your problems go away," because it means the fix isn't a new tool or a new certification. It's discipline - in planning, in communication, in following through on whatever process you already committed to.
The scale of the underlying problem makes this urgent. The average project performance rate across organizations sits at 73.8%, meaning roughly one in four projects fails to meet its business goals - and that failure rate isn't concentrated in one methodology camp. It shows up in waterfall, agile and hybrid projects alike.
(https://www.pmi.org/learning/thought-leadership/future-of-project-work)
What "Skill" and "Execution" Actually Mean in Practice
"Execution" can sound like a vague consulting word, so it's worth breaking into things we can actually audit.
Real-time visibility into project status. This is the single most damning statistic in the data. Nearly half of respondents - 47%, say they don't have access to real-time project KPIs, and half spend one day or more each month manually collating project status information by hand.
No methodology fixes that. A team running perfect two-week sprints with no visibility into actual progress is no better off than a waterfall team updating a status report once a quarter.
Realistic planning and estimation. Whether your unit of planning is a phase gate or a sprint, the discipline is the same: basing timelines on evidence rather than optimism.
Team enablement. This is one of the more actionable findings in the research. Organizations providing three or more enablers - coaching, training on new methodologies, and communities for sharing knowledge - reported notably higher project performance, while organizations lacking those enablers were more likely to encounter scope creep and budget overruns. That's a controllable input. Most teams could add a coaching cadence or a knowledge-sharing habit far more easily than they could reconsider their entire methodology.
Actually following the process you chose. This is the quiet killer. Half-running agile - daily standups that are really status reports, sprints with no real retro, a backlog nobody grooms - produces worse outcomes than a strict waterfall team that actually respects its phase gates. The failure isn't the framework. It's the half-commitment.
Methodology Does Still Matter
None of this means methodology is irrelevant - that would overcorrect the point. Predictive approaches still make sense where compliance, fixed budgets, or contractual milestones demand documentation and sign-off. Agile still makes sense where requirements will keep shifting and early, frequent feedback is more valuable than upfront certainty. Hybrid exists precisely because most real projects have both kinds of work inside them.
Methodology is the container. Execution is what fills it. A well-run waterfall project will beat a poorly run agile one every time, and the reverse is just as true. Choosing the right container matters - but it's a one-time decision made at the start of a project. Execution is a decision made every day of it.
A Practical Self-check
If methodology isn't the lever to pull, here's what to check instead. Hold your current project up against these questions rather than asking which framework you should be using:
- Do we have real-time visibility into project status, or are we manually reconstructing it each week?
- Are we consistently delivering on time, on budget, and on scope — regardless of which framework we're nominally following?
- Where are we half-following our own process? Which ceremonies or phase gates have become theater rather than substance?
- Are we investing in coaching, training, and knowledge-sharing, or assuming the framework alone will carry the team?
None of these questions require picking a side in the agile-versus-waterfall argument. That's the point.
To Conclude
The methodology conversation stays popular because it's concrete and debatable - you can argue about frameworks in a meeting and feel like you've made progress.
Execution quality is a harder conversation, because it's about discipline rather than doctrine, and nobody enjoys auditing their own follow-through. That's exactly why it's the conversation worth having.
Skip the framework debate this week. Instead run your current project through the four questions above.
Good luck
