The Methodology Wars Are Over

For 20 years, I’ve watched project professionals argue over methodologies as if they were competing religions. Waterfall purists dismissing Agile as undisciplined. Agile evangelists mocking Waterfall as outdated. Hybrid advocates trying to define a common middle ground.

Here’s what I’ve learned: they’re all correct, and they’re all wrong.

Every methodology works brilliantly in the right context. Every methodology fails spectacularly in the wrong context. The problem isn’t the methodologies themselves. The problem is how we select and apply them.

Traditionally, methodology selection has been driven by three factors, none of them universally valid:

1. Industry norms (Everyone in construction uses Waterfall)

2. Organisational preference (We’re an Agile shop)

3. Personal experience (I’ve always used this approach)

What’s missing? The actual characteristics of the project to be delivered.

AI enables something we’ve never had before: knowledge-based customisation of project delivery.

Let me explain.

Every project has a unique signature. Dozens of variables define its DNA: scope volatility, regulatory constraints, team distribution, stakeholder complexity, technical uncertainty, commercial risk, timeline pressure, and resource availability.

Manually analysing all these variables and determining the optimal methodology is overwhelming. So, we default to familiar approaches, even when they’re suboptimal.

AI can change this completely. Here’s how:

* Methodology optimisation through pattern matching. AI can analyse your project’s specific parameters and compare them against historical projects with known outcomes. It identifies which delivery approaches worked best for projects with similar characteristics. Not ‘similar industry’, similar characteristics. A regulatory-constrained healthcare project might have more in common with a financial services project than with an internal healthcare initiative. AI recognises these nuanced patterns that humans miss.

• The recommendation isn’t to use Agile or use Waterfall. A customised recommendation is made based on characteristics like your high regulatory constraint, moderate scope volatility, and distributed team structure. So, the recommendation may be a hybrid approach with fortnightly iterations, comprehensive documentation gates, and asynchronous collaboration tools, giving you the highest probability of success, based on historical factors.
• Adaptive methodology through continuous learning. Here’s where it gets genuinely powerful: AI can monitor your project’s actual progress and recommend adjustments to your methodology. You start with an Agile approach because the scope seemed flexible. Three months in, regulatory requirements crystallise, introducing significant documentation and approval overhead. Traditional Agile struggles with this. You share this in a query, and AI analyses this shift. It suggests introducing stage-gate reviews while maintaining iterative development for non-regulated components.

You’re not abandoning your methodology; you’re adapting it to evolving reality.

• Resource optimisation through algorithmic assignment. Methodology is pointless without effective execution. One of the most time-consuming PM activities is resource allocation, matching people to tasks based on skills, availability, dependencies, and development goals. AI can optimise this in ways that are impossible manually. It considers hundreds of variables, including individual skill profiles, current workload, task dependencies, historical productivity on similar work, and learning-curve estimates. What would take you days of spreadsheet manipulation and negotiation, AI can calculate in seconds. More importantly, it can continuously re-optimise as conditions change. Note: Data on individuals is not something you want to share with an AI tool that can share it with other users. This technique should be utilised only if you have an in-house AI repository.
• A word of caution: AI provides optimisation, not understanding. I need to be crystal clear about something: AI methodology recommendations are only as good as the data they’re trained on and the constraints you provide. AI can identify the statistically optimal approach based on historical data. It cannot tell you that your CFO will never approve iterative budgeting. It cannot tell you that your organisational culture is fundamentally resistant to empowered teams. It cannot tell you that your executive sponsor expects detailed upfront documentation regardless of project suitability. These contextual factors, organisational politics, cultural norms, and stakeholder expectations require human interpretation. AI augments your decision-making; it doesn’t replace it. Thus, your role evolves from “methodology implementer” to “methodology architect.” You use AI to understand options and trade-offs, then apply your contextual knowledge to make the final call.

The Competitive Advantage

Project professionals who can leverage AI for methodology recommendations and adaptive execution will deliver better outcomes with less waste. Your competitors are still debating Waterfall versus Agile. You’re using AI to design precisely calibrated delivery approaches that adapt to reality.

That’s not just a skill advantage. That’s a career-defining capability.

Want to learn more? Enrol in my Bond University Microcredential course entitled Ai-Enabled Complex Project Delivery. Here is a discount code you can use when you sign up for an April session – AiCPDApril