Project Manager | Driving Clean Energy Innovations for a Sustainable Future| Canadian Nuclear Laboratories Ontario, Canada
Agile is often portrayed as the ultimate solution for all projects—but is it really?
The truth is, methodology should fit the context, not the trend. Some projects thrive on structure, others on flexibility. Blindly chasing Agile can create chaos instead of value.
What do you all think—are we too focused on methodology labels instead of outcomes? How do you decide what works best for your projects?
Agile is great, but it’s not the magic fix for every project. Different projects need different approaches. Some work better with a structured plan, while others need the flexibility Agile offers. If you try to force Agile onto the wrong kind of project, it can cause more headaches than progress.
At the end of the day, it's not about sticking to a method—it's about what actually helps you get the job done and deliver value. So when it comes to choosing the right method, I think it’s all about what fits best with the team, the project, and what you're trying to achieve. Saving Changes...
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
Agree that methodology should follow context, not trends. I’ve seen teams struggle when they try to “go Agile” without the right culture, governance, or stakeholder mindset to support it. The key is situational agility, understanding when to apply iterative practices and when a more predictive approach ensures control and clarity. What matters most isn’t the label, but whether the approach drives value, alignment, and sustainability for that specific project.
...
1 reply by Zakaria Botros
Nov 06, 2025 1:11 AM
Zakaria Botros
...
Thank you for your input — I really like the term “situational agility.” It perfectly captures the balance between structure and adaptability. Do you recall any examples where applying situational agility changed the output or even reshaped the direction of a project?
Unfortunately, "Agile" has become a buzzword that means different things to different people. Often people think of it as short iterations in a Scrum type format. "Waterfall" has also taken on a meaning of purely predictive. I often try to avoid the labels altogether and simply describe the approach to prevent people forming negative impressions based on what they think the terms mean from bad past experiences where someone tried to force a square peg into a round hole.
Often, the preferred approach depends on the significance of errors, and the physics of change. In projects where critical parts of the product are mechanical, the cost and time to implement changes may be cost or time prohibitive placing more importance on getting it right the first time. It's more difficult to change poured concrete than it is to revise lines of code. Likewise, ensuring that software avoids issues affecting human safety is more important than an annoying blinking pixel. The first might require a lengthy requirements verification process before going live, while the pixel might be another nuisance added to the backlog. Saving Changes...
Agile and Waterfall are not opposites or alternative "methodologies". Agility is a set of ideas about ways of working and organization. The word "Waterfall" is really too overloaded to be worth talking about - for example do you mean the waterfall SDLC model or do you just mean predictive planning? The waterfall SDLC model is not particularly relevant or helpful in the context of modern software engineering. Predictive planning on the other hand is very relevant and is certainly practiced by agile teams using agile ways of working. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
As somebody that was part of the genesis of agile and agility let me say this. 1-Too many people and mainly too many organizations (PMI included) contribute to generate a big misunderstanding that jeopardizes the work of lot of people like me that try to implement agile in organizations as a competitive advantage. 2-this confusion is expressed into your post: agile and waterfall are not matter of comparision. Agile is an approach (like Lean) while waterfall is a life cycle. You can use Agile with waterfall life cycles. Saving Changes...
Project Manager | Driving Clean Energy Innovations for a Sustainable Future| Canadian Nuclear Laboratories Ontario, Canada
Nov 04, 2025 8:47 AM
Replying to Lissette Indhira Pimentel Sosa
...
Agree that methodology should follow context, not trends. I’ve seen teams struggle when they try to “go Agile” without the right culture, governance, or stakeholder mindset to support it. The key is situational agility, understanding when to apply iterative practices and when a more predictive approach ensures control and clarity. What matters most isn’t the label, but whether the approach drives value, alignment, and sustainability for that specific project.
Thank you for your input — I really like the term “situational agility.” It perfectly captures the balance between structure and adaptability. Do you recall any examples where applying situational agility changed the output or even reshaped the direction of a project? Saving Changes...
Andrew BallSenior/Head of PMO| a3g LtdAshford, United Kingdom
the world of project delivery cannot exist on one methodology or approach, each has virtues and each have weaknesses. For overarching programmes waterfall sit sbest, it manages the dependencies across deliveries and with a high level of certainty in adoption. the solution is what the business needs and is evolutionary. Agile sits in a fluid world, changing to meet needs so is perfect for low level initiatives and delivering technological solutions as part of the wider programme. Add any number of different approaches in this classification. what however remains the imperative is the value add the outcome provides, not the way to achieve it. Programme risks sit large and are managed at this level, will incorporate project/workstream items but will demonstrate the RoI through strong and clear governance. shortcuts by their very nature introduce uncertainty which must be managed or will bring the endeavour crashing down with watsed budget, watsed effort and reputation damage. in summarty, all approaches work in the right context, apply what is appropriate not what is easy..................
All or nothing thinking is a big risk to project success. Leadership and influencers outside the profession, without any experience, solve problems using the tools and methods comfortable and familiar to them, which may fight proven project practices they have never seen in the operational side. Insiders without the benefit of knowledge and experience in an immature organization do what they're told. Everyone is seeking a shortcut to done and every magic bullet advertised. AI is the next one despite the ethical and environmental damage. No one thing is a magic cure for immaturity, poor practices, thin understanding, and blind simplicity. The job for PMs is harder than ever before because we need so many tricks in our toolbox now and there is no shortcut to learning and doing.
...
1 reply by Zakaria Botros
Dec 20, 2025 10:22 AM
Zakaria Botros
...
Well said—and I agree with much of this. All-or-nothing thinking is exactly the trap behind many “Agile vs. Waterfall” debates. Methods are tools, not beliefs.
Project Manager | Driving Clean Energy Innovations for a Sustainable Future| Canadian Nuclear Laboratories Ontario, Canada
Nov 21, 2025 9:30 AM
Replying to Sonya Calef
...
All or nothing thinking is a big risk to project success. Leadership and influencers outside the profession, without any experience, solve problems using the tools and methods comfortable and familiar to them, which may fight proven project practices they have never seen in the operational side. Insiders without the benefit of knowledge and experience in an immature organization do what they're told. Everyone is seeking a shortcut to done and every magic bullet advertised. AI is the next one despite the ethical and environmental damage. No one thing is a magic cure for immaturity, poor practices, thin understanding, and blind simplicity. The job for PMs is harder than ever before because we need so many tricks in our toolbox now and there is no shortcut to learning and doing.
Well said—and I agree with much of this. All-or-nothing thinking is exactly the trap behind many “Agile vs. Waterfall” debates. Methods are tools, not beliefs. Saving Changes...
I agree, no method fits every project. Agile works well when change is expected, while Waterfall suits stable, regulated, or well-defined work. The real focus should be on outcomes and risk, not labels, choose what fits the project context, or even combine approaches when needed.
Community Champion
