The adaptive approach
The adaptive approach to project management is a collaborative, iterative approach that aims to develop products or projects in iterations, each one delivering value to users. Unlike predictive approaches, the adaptive approach focuses on delivering value rapidly and continuously, while fostering collaboration between team members.
The Scrum method is often used in the adaptive approach, where the project is divided into iterations called "sprints". Each sprint lasts from one to four weeks and has a specific result to achieve. The development team collaborates with the Scrum Master and Product Owner to plan, design, develop and test product features during each sprint.
One of the fundamental principles of the adaptive approach is to remain open to changes, rather than freezing the scope at the start of the project; the team can reprioritize them as and when value is created.
An example of an adaptive approach: software development. Functionalities are worked on as the project progresses, even if it means reprioritizing them as the need arises. Some may be added to better meet needs, others abandoned because their value is no longer proven.
In short, the adaptive approach to project management is iterative, collaborative and promotes the continuous delivery of value. It enables us to better respond to changing customer needs, and to achieve results.
The predictive approach
The predictive approach to project management is an approach that aims to plan in detail, and to execute and monitor the project plan based on established forecasts and estimates. In a predictive approach, the project is generally planned in detail, defining all deliverables, resulting activities, deadlines, costs and resources required, to name but a few. Throughout the project, repositories will be monitored to identify the need to request adjustments.
This approach is particularly well suited to projects whose objectives and specifications are well defined from the outset, and for which it is possible to accurately estimate the resources required and the timescales for completion. However, it can run into difficulties when requirements change frequently.
An example of a predictive approach: the construction of a bridge. Constraints are numerous and not easily removable. What's more, an iterative approach is unrealistic: once the concrete has been poured, it's hard to go back. Not to mention the fact that construction has no choice but to follow stages in a predetermined order: design, mock-up, construction (and for the latter, too, there's a logical sequence: piers first, decks next), and so on.
In short, the predictive approach to project management is based on a detailed plan and forecasts drawn up in advance. It is suitable for projects where requirements are stable and well understood, and where it is possible to plan and estimate the various aspects accurately.
Reality and the volatile environment in which we live lead us to see project management as a strategy for achieving corporate objectives. Which explains why the Hybrid approach is gaining ground!
The hybrid approach
Hybrid project management is an approach that combines adaptive tools with those typically used in the predictive approach. Depending on the organization, the project team, the type of project, etc., the hybrid approach can be adapted to create value. The hybrid approach enables us to adapt according to value creation.
In a hybrid project, some parts of the project can be managed adaptively, while other parts can follow a more predictive approach. For example, initial planning, identification of objectives and key deliverables can be carried out using a predictive approach, while task execution can be managed iteratively.
The hybrid approach is used when projects have complex requirements and need highly structured governance.
Conclusion
The project manager's role remains a key one, as he or she is responsible for the successful delivery of the project, whatever the preferred approach. The good news is that the PM has a wide range of tools at his or her disposal to achieve this. It's up to him or her to see what serves the project best.
To find out more :
