Last Updated on 21 September 2023 at 22:57
So, there I was, with my tier 1 customer bank, locked in a battleground about project management methodologies.
- On one side, you’ve got Waterfall — the project purist of the “if it ain’t broke, don’t fix it” approach.
- On the other, Agile — the Silicon Valley blitzscaling strategy that’s all about “move fast and break things”.
But choosing between Waterfall and Agile is like choosing between a scalpel and a Swiss Army knife. Each has its place in the right environment, but sometimes, in the wild with nobody to help you, what you need is a tool that can do both.
The Good, The Bad, and The Ugly of Waterfall
Waterfall is like the granddaddy of project management.
This methodology is the Swiss watch of project management — structuring requirements, great design, meticulous implementation, and so on. But let’s be real; it is also very rigid.
Once you’re locked into a phase, good luck trying to pivot.
It’s like being on a train that only goes one way without a stop, and there’s no getting off until you reach the last station. Except for the emergency brackets.
The Good: Predictability.
Waterfall is the comfort food of project management. You know what you’re getting, and you know when you’re getting it. It’s the go-to for industries that can’t afford to mess around — think aerospace, healthcare, fintech, and anything that involves the phrases “regulatory compliance” and “security”.
The Bad: Inflexibility.
Once you’ve committed, you’re in for the long haul.
It’s like a seven-course meal in a very expensive restaurant where you can’t skip until the dessert, no matter how much you want to. It is like looking at a bureaucratic nightmare, too. Of course, it is possible to change course, but you better have a good reason — and the C-level deciders into your pocket.
The Ugly: Resource Intensiveness.
Waterfall demands a lot upfront. It is like a high-maintenance relationship; it demands a lot of time, attention, and yes, money. Very much of it.
Agile: The Silicon Valley Fashion
Agile is all about adaptability. It is fast, and it is built for the ever-changing landscape of the 21st century — making it up as you go along. It is the jazz improvisation of whatever fashionable business strategy. But it is not the panacea it is often made out to be.
The Pros: Adaptability.
Agile is the chameleon of project management.
New requirements ? No problem.
Market conditions changed overnight ? No problem.
Agile pivots faster than a politician.
The Cons: Ambiguity.
Agile’s flexibility can be its Achilles’ heel.
Without a defined endpoint, you are in a perpetual state of “almost there” — which can be a hard sell to the C-suite folks who want to see a finished product, not a “work in progress” with a “never-ending soon” as a delivery timeline.
When Agile Becomes Fragile
So, you want to switch from Waterfall to Agile ?
Prepare for a culture shock.
It is not just about changing processes but about changing mindsets.
Bad news: this transition is going to take some time and a lot of training.
And, again, money.
Agile demands a different skill set. It is like asking classical pianists to become jazz improvisers without any training. Besides, there is a misalignment of business goals that sometimes clash with the corporate strategy. Especially if you’re in a regulated industry like finance or healthcare.
Mixing Agile with Waterfall
Here is where the hybrid model, the yin and yang of project management, comes into play. Think of it as a cake with the chocolatey structure of Waterfall and the creamy flexibility of Agile.
The cherry on the cake is the best of both worlds, and this is how you can win at software development and project management.
- But in a hybrid model, governance is not just a nice-to-have word on a presentation for the C-Suite but the invisible person that guides operations.
- You also need Standard Operating Procedures (SOPs).
- Your KPIs should be your North Star, guiding you through the fog of project complexity. In a hybrid model, you need KPIs for both Waterfall and Agile phases. It is like having both a speedometer and an altimeter when you’re piloting a plane: both are needed for different reasons.
- And don’t forget the feedback loops — that is how you go from good to great. In a hybrid model, feedback loops are your continuous improvement engine. They are what it takes to evolve from version 1.0 to 2.0 and beyond.
In the end, it’s not about choosing between Waterfall and Agile; but about knowing when to use each. It is about understanding that structure and flexibility are not mutually exclusive but are, in fact, two sides of the same coin.
So, the next time someone tries to sell you on the “one true methodology”, remember: the most innovative solutions often come from combining the best of both worlds.
FinTech Wealth Management expert with 30 years of successful track record, from Unicible/BCV to Odyssey and Temenos, plus hundreds of important banks across EMEA, APAC, and NAM.
► Background — from C-language code to C-suite in 30 years
• WealthSuite Triple’A Temenos TAP Plus expert
• crisis & change management
• complex multi-level project – program – portfolio management
• process architecture & governance, process optimization, BPO
• financial services software engineering FS FinTech
Career start as an innovative software engineer in startups ► to strategic advisory & turnaround for Tier1 & Tier2 Banks at senior C-level.
• T-shaped mastery of the latest key technologies, business, and operational practices in retail banking, asset management, core banking, PMS.
• Keen focus on improving productivity, client retention, and revenues through expertise in Program Management, Process Governance, and Optimized Delivery, augmented by know-how in complex issue resolution and value-driven E2E end-to-end implementations.
Temenos Practitioner accredited across WealthSuite and FrontOffice domains (FO, PM, TTI). Certified modules include Scripts & Formats, Implementation Methodology (T3TIM), Channels PM, APA Attribution, Constraint Management, Order Management, Data Security, WealthSuite Portfolio Management, and T24 Triple’A Interface. The Practitioner status anchors Didier’s capacity to operate as a Transformation Director, bridging certified product mastery with execution governance and program recovery.
Disclaimer —
The views and opinions expressed in this publication are those of the author, Didier Debbaut, and do not represent the views, positions, or policies of Temenos AG, its affiliates, clients, or partners. All information is shared in good faith and in the spirit of professional exchange, as part of an open, constructive contribution to the FinTech and WealthTech community.
Any technical references, opinions, or analyses are based solely on publicly available information and the author’s independent field expertise. They are offered for general informational and educational purposes only.
No confidential, proprietary, or non-public information related to Temenos products, clients, or business operations is disclosed or implied.
© Didier Debbaut — All rights reserved.
Learn when to choose High Availability, Fault Tolerance, or Disaster Recovery in Azure. Didier Debbaut maps costs, risks, and execution trade-offs.
Mixing #Agile with #Waterfall ? Think of it as a cake with the chocolatey structure of Waterfall and the creamy flexibility of Agile. The cherry on the cake is the best of both worlds, and this is how you can win at #software #development and #project #management.
The debate between Agile and Waterfall is not a zero-sum game. Each methodology has its merits and drawbacks, and the choice between the two is often dictated by the specific requirements and constraints of a project or program. However, for projects that demand both structure and flexibility, a hybrid approach can offer a balanced solution.
In practice, it is not about choosing between Waterfall and Agile; it’s about knowing when to use each. Structure and flexibility are complementary and not mutually exclusive. So, the next time someone tries to sell you on the “one true methodology”, remember: the most innovative solutions often come from combining the best of multiple worlds. It’s not about only waterfall or agile, but a lot of other methodologies, too.
Our latest publication explore the complex world of FinTech, focusing on the role of DevOps. Written by Didier Debbaut and Elena Debbaut, both experts in Software Wealth Management and Turnaround & Crisis Management, the piece aims to offer a comprehensive and nuanced understanding of DevOps’ strategic imperatives in the FinTech sector.
