Choosing a project management method isn’t a matter of following trends. It’s a matter of finding the right fit for the nature of your project, your organization’s constraints, and your team’s maturity. A well-chosen method reduces friction, clarifies responsibilities, and speeds up decision-making. A poorly chosen method creates exactly the problems it was supposed to solve.
This article reviews the main project management methods predictive, agile, and hybrid and offers a practical decision-making framework to help you identify the one that best fits your situation.
How a project management methodology changes your day-to-day life
A project management methodology is a framework for collaborative work. It defines who decides what, in what order, with what deliverables, and at what frequency of approval. Without a framework, a project moves forward through a series of meetings that no one keeps track of and emails that contradict previous decisions. With the wrong framework, it moves forward just as poorly only with more jargon.
Several aspects of collaborative work are directly affected by this choice.
- The approach to planning, balancing detailed upfront planning with iterative adjustments
- The division of roles and the level of autonomy for each team member
- The schedule for deliverables and validation meetings with stakeholders
- Managing unforeseen events and the cost of course corrections along the way
- Transparency regarding progress for management and sponsors
Choosing a method means deciding how your team will operate for weeks or months. This decision deserves more attention than the choice of the project management tool that will go along with it. A good tool amplifies the effects of the method for better or for worse.
Predictive methods: Waterfall, V-Model, and PERT
Predictive methods are based on an initial assumption: that the scope of the project can be defined before work begins. A comprehensive plan is established in the initial phase, the schedule and budget are set, and then the project is executed. This family of methods is suitable for projects with stable requirements and deliverables that can be precisely identified at the scoping stage.
The Waterfall method organizes the project into sequential phases. From scoping to design, from development to testing, and then to deployment, each phase must be completed before the next one begins. This framework offers strong traceability and reassures stakeholders who need long-term visibility. Its main drawback remains the cost of changes made along the way. A major adjustment discovered during the testing phase can invalidate weeks of design work. Waterfall works well when requirements do not change. A construction project, a data migration with a fixed scope, or regulatory compliance efforts are well-suited to this framework.
The V-model is a structured variation of the Waterfall model in which each design phase has a corresponding validation phase. The overall architecture is designed first, followed by the modules, then the components; testing is performed in the reverse order. This model is common in engineering, healthcare, and defense, where regulatory requirements mandate complete traceability of every decision. In Switzerland, the Hermes 2022 framework follows this approach. It serves as the official standard for IT projects of the Confederation and many cantons. Project managers working with public administrations in French-speaking Switzerland would be well advised to familiarize themselves with it. It is rarely taught outside the public IT sector, even though compliance with it often determines whether deliverables are accepted.
The PERT (Program Evaluation and Review Technique) method is more of a planning analysis tool than a comprehensive governance method. It models dependencies between tasks, identifies the critical path that is, the sequence that determines the minimum project duration and allows for the visualization of available buffers before a delay in one task causes the entire project to fall behind. It is used primarily during the planning phase of complex projects with numerous interdependencies.
Agile methods, Scrum, Kanban, and Lean
Agile methods are based on the opposite premise of predictive methods. A project’s requirements evolve as it is carried out. It is better to deliver something useful quickly and make adjustments than to wait a year to deliver a complete product that no longer meets the needs. This approach first emerged in software development before spreading far beyond the IT sector.
Scrum organizes work into short iterations called sprints, typically lasting two to four weeks. A small team ideally between five and nine people commits to a set of priority tasks, completes them, and then presents the results at the end of the sprint. This agile project management method works well when short-term needs are clear but long-term needs are less defined. It requires a team that is available, stable, and comfortable with autonomy. In a multi-project environment or when resources are shared among several teams, sprints quickly become a planned fiction. People are not available at the pace the method assumes.
Kanban visualizes the workflow on a board organized into columns: “To Do,” “In Progress,” and “Done.” It does not specify iterations but limits the number of tasks handled simultaneously to prevent bottlenecks. This approach is particularly well-suited for operational teams that manage continuous workflows rather than projects with a defined end date. A support team, a legal department, or an internal communications unit may benefit more from Kanban than from Scrum.
Lean originated in the Japanese manufacturing industry and was popularized by the Toyota Production System. It aims to eliminate anything that does not create value for the end customer, such as wait times, rework, unnecessary inventory, and steps with no impact. In practice, Lean encourages delivering as early as possible, measuring results, and eliminating efforts that do not improve the deliverable. Its limitation in service or organizational transformation projects stems from the difficulty of defining what “value” means when the deliverable is not a physical product.
Project leadership
Hybrid project management: a pragmatic third way
Hybrid project management combines a predictive planning phase with iterative execution. The scope and budget are defined upfront, following a traditional Waterfall approach, and the project is delivered in successive phases rather than all at once at the end of the project. This approach does not choose between the two methodologies; instead, it draws on what works best in each, depending on the stage of the project and the level of uncertainty.
It addresses a common reality in medium-sized organizations. Management expects a traditional project plan with a timeline, milestones, and a controlled budget. Teams, on the other hand, know that details will evolve along the way. The hybrid approach reconciles these two approaches without imposing a complete cultural shift toward Agile a shift that many organizations are not ready to make.
Hybrid project management is now the most widespread approach in transformation projects at Swiss SMEs. While there is a high degree of certainty regarding the objectives, there remains little certainty regarding the specifics of implementation. This is precisely the use case that neither pure Waterfall nor pure Scrum covers well. Recognizing this fact is not a half-hearted compromise. It is often the most clear-headed decision a project manager can make.
How to choose the right method for four situation
No single method is superior to the others in absolute terms. The right question is not “which method is best,” but “what is the nature of your uncertainty, and what does your organization actually need?” Four questions can help guide your choice.
Are the project requirements stable or likely to change? If they can be defined from the outset with a reasonable degree of precision, a predictive approach is appropriate. If they are likely to evolve as the project progresses, an agile approach will be more suitable. An honest answer to this question alone already eliminates half the options.
Is your team available full-time for this project? Scrum requires a dedicated team. In a multi-project environment or one with a variable workload, Kanban or a hybrid approach is more realistic. A team working at 30% capacity cannot keep up with the pace of a Scrum sprint without compromising quality.
Does your organization impose a specific governance framework? IT projects for Swiss public administrations often follow Hermes 2022. Companies subject to strict regulatory requirements such as those in finance or pharmaceuticals tend to favor predictive methods or PRINCE2. Ignoring this framework doesn’t make it go away; it resurfaces during audits and deliveries.
What deliverables does your management expect? If they expect a Gantt chart and a detailed workload plan, a purely Scrum approach will create unnecessary friction without any real benefit. Aligning the methodology with internal governance expectations is part of the project manager’s job not just the team’s.
An honest answer to these four questions is worth more than a certification in a trendy methodology. A well-managed project using the Waterfall method produces better results than a poorly managed project labeled “Agile.”
Develop skills in project management methods
It takes a few hours to grasp the basics of a method. Knowing how to apply it within your organization given your actual constraints, your decision-making culture, and the diversity of your team is a different matter entirely. Most project managers who “practice Agile” without formal training are actually managing a Waterfall process broken down into shorter meetings. The label changes, but the practice remains the same.
Recognized certifications allow you to acquire both technical mastery of the methodology and a common language with your peers and stakeholders.
- PMP (Project Management Professional), certified by the PMI, an international standard focused on the fundamentals of project management regardless of the method used
- PRINCE2, a structured framework for governance and control, widely used in Europe and in the public sector
- Hermes 2022, the official Swiss standard for projects of the Confederation and many cantons; rarely taught outside of government agencies but essential in that context
Beyond certifications, continuing education allows you to work on the real trade-offs that a methodology imposes in a concrete project. How do you manage a team that resists Scrum? How do you build a Waterfall plan that doesn’t become a straitjacket? How do you manage the transition between two methodologies midway through a project? The CAS in Project Leadership from HEC Lausanne Executive Education addresses these project management methods within a framework grounded in the realities of organizations, with an emphasis on the role of the project manager in a position of managerial responsibility.
