By Alisdair Blackman
Over the years, I’ve encountered countless leaders who champion a single project methodology as gospel – often dismissing alternatives despite claiming broad experience. Whether it’s Agile, Waterfall, or a bespoke hybrid, the truth is: no one method guarantees success.
What many overlook is that beneath the surface, the fundamentals remain consistent. Tasks, risks, dependencies, tools, and environmental sensitivities don’t vanish with a change in delivery model. Success and failure are not dictated by methodology – they’re shaped by leadership, clarity, and execution.
Having worked across Agile, Waterfall, hybrid, and even loosely defined delivery models, here are five lessons I’ve learned:
1. Collaboration & Communication Are Everything
SCRUM meetings alone don’t build great projects. True collaboration requires ongoing care, coordination, and support. Over-scheduling meetings doesn’t equal engagement – it often stifles it.
Effective communication is dynamic, flexible, and inclusive. It thrives on open dialogue, stakeholder engagement, and a willingness to adapt. Projects are fluid; your approach should be too.
2. Agile Still Needs BA Fundamentals
There’s a myth that Agile projects don’t require business analysis. I disagree. Planning, defining business needs, documenting requirements, and validating outcomes are essential – regardless of methodology.
Agile may distribute these tasks differently, but the need for clarity and structure remains. Good BA practices are not a burden – they’re a backbone.
3. Techniques Transcend Methodologies
Core techniques – requirements gathering, prioritisation, change management, risk mitigation – are universal. Agile may favour user stories and iterative planning, while Waterfall leans on upfront definition. But both aim to deliver meaningful outcomes.
The difference lies in timing and format, not in the value of the techniques themselves.
4. Stop Polarising Agile and Waterfall
Agile and Waterfall aren’t enemies. Agile is a mindset – one that values adaptability, rapid feedback, and iterative delivery. It doesn’t seek to replace Waterfall, but to offer an alternative lens for solving problems.
Both have merit. The key is choosing the right tool for the right context.
5. Keep Calm & Talk to Your Stakeholders
Agile may look and feel different, but change doesn’t need to be disruptive. Strong facilitation and confident leadership are critical when shifting approaches. Keep stakeholders informed, engaged, and focused on outcomes – not just process.
Final Thought
Methodologies are frameworks – not magic bullets. The real differentiator is how well you lead, communicate, and adapt. Whether Agile, Waterfall, or hybrid, success lies in your ability to unify teams, clarify goals, and deliver value.
