In many organizations, the discussion starts too quickly with the method: should we use Agile, Scrum, V-cycle, Kanban or hybrid? This question seems structuring, but it often comes too early.
A project management method is not a standalone solution. It is a working framework. It helps organize decisions, roles, deliverables, exchanges and follow-up. But it does not replace problem clarification, strategic arbitration or the organization’s ability to absorb change.
The real issue is not the method, but the problem to steer.
A project can fail with a perfectly applied method if the need is unclear, if stakeholders do not share the same definition of success, or if important decisions remain implicit.
Conversely, a simple framework can work very well when the scope is clear, responsibilities are assumed and arbitration takes place at the right level. The method does not create clarity by itself. It organizes it when it already exists, or reveals its absence.
Asking “which method should we use?” before asking “what problem must we solve?” often leads to imposing an attractive framework on an organization that has not yet clarified its constraints.
Agile, predictive or hybrid: it all depends on context.
A predictive approach can be relevant when the need is relatively stable, constraints are strong, dependencies are numerous and deliverables must be secured from the start.
An agile approach becomes more useful when uncertainty is high, the product must be learned progressively, user feedback matters greatly and the organization accepts regular priority adjustments.
Hybrid is not a soft compromise. It is often operational reality: some elements must be scoped, contracted and planned, while others must remain open, tested and adjusted.
The method must serve decision-making.
A useful method is a method that helps decision-making. It must make risks, dependencies, gaps, trade-offs and blocking points visible. If it mainly produces meetings, boards or rituals without clear decisions, it becomes an additional layer of complexity.
The right criterion is therefore not whether the organization is “agile” or “predictive.” The right criterion is whether the chosen framework makes it possible to better understand the situation, make better decisions and execute better.
Start with four simple questions.
Before choosing a method, clarify the nature of the project: is the need stable or uncertain? Are the deliverables known or to be discovered? Are stakeholders aligned? Can decisions be made quickly?
Then look at the organization’s actual capacity: what resources are available, what skills are critical, what arbitration is possible, and what level of steering can be sustained over time.
The right method is not the one that seems the most modern. It is the one that matches the problem, context, constraints and decision-making capacity of the organization.
Project management therefore rarely starts with a method. It starts with a clear reading of the situation: what you want to achieve, what you already know, what you still do not know, what must be arbitrated and what the organization can truly absorb.