The term Waterfall, as you mentioned, stands behind the Project Managers’ work methodology, based on already established rules, in which everything is performed step by step.
A clearly charted plan of action is followed, everything is described in heavy documentation and contractual relations between all parties, and in reality the participants in this project do not have the freedom to deviate in any way from the set plan. If there is a roadblock or something that is not planned and spelled out in the step-by-step plans, then it takes a tremendous amount of time and resources to resolve that issue. Everything must be amended both documentarily, with all approvals from all parties, and procedurally along the Waterfall chain. Reference: “Waterfall and Agile project management practices“, https://securityinformationeventmanagement.com/waterfall-and-agile-project-management-practices/
The Agile methodology of work is the exact opposite – here each Project Manager has the freedom to use the available resource in a way that he considers most appropriate in the given situation. Agile means being flexible. Depending on the project, the direction of development may change during its implementation, as various studies and tests may be conducted in parallel and, based on their results, a different direction may be taken. In two words, it is a flexible work model in which the role of the Client is much greater. In the course of work, the Client takes an active part in the process, approves current changes, and expresses an opinion. In this way, the time for the realization of a project can be shortened, as well as its costs. Reference: “Waterfall project management and Agile product management approaches“, Reference: “Waterfall project management and Agile product management approaches“, https://projectmanagers.wpdevcloud.com/waterfall-project-management-and-agile-product-management-approaches/
Scrum is how the Agile ideology is implemented. In the Scrum methodology, teams develop the project in discrete time intervals, completing small parts of the entire project. The work is visible at all times to everyone involved in the entire process. The client can revise individual parts of the project, evaluate them or make changes during work. Then everything turns again – cyclicality.
Both Waterfall and Scrum methods have their pros and cons and it largely depends on what the project is, who the Client is, and how good the Project Manager is to choose the right method of work. Reference: “Agile methodologies and Waterfall project management“, https://projectmanagers.business.blog/2023/01/14/agile-methodologies-and-waterfall-project-management/
Some Project Managers work better under established and written rules, and the Clients themselves feel better when everything is accurately described in the documentation. They outsource the project and expect to see the result without being involved in the overall process.
Other Project Managers prefer the opposite approach – to involve the Client in the entire process to get as close as possible to the desired result. They feel more secure when they have the freedom to make a U-turn at any moment, for the sake of the bottom line. Here, however, if the Project Manager is not used to such a method of work, he can easily get lost on the way and create a little chaos, which in turn will lead to an undesirable final result, time delay, or gaps in the overall implementation of the project.
More Agile vs Waterfall project management
- “Using Waterfall and Agile project management methodologies“, mpmu.org/using-waterfall-and-agile-project-management-methodologies/
- “Agile and Waterfall in project management practices and processes“, polyscm.com/agile-and-waterfall-in-project-management-practices-and-processes/
- “Similarities and differences between Agile and Waterfall project management”, w-europe.org/similarities-and-differences-between-agile-waterfall-projectmanagement/
- Agile vs Waterfall: The Difference Between Methodologies, libraryofmu.org/agile-vs-waterfall-the-difference-between-methodologies/
- “Waterfall, Agile, Scrum and Kanban methodologies”, stc-montreal.org/waterfall-agile-scrum-and-kanban-methodologies/
- “Agile and Waterfall project management practices“, mstsnl.net/agile-and-waterfall-project-management-practices/
- Comparison of Agile, Scrum and Waterfall project management, eduwiki.me/comparison-of-agile-scrum-and-waterall-project-management/
- Agile, Scrum and Waterfall project management, ossalumni.org/agile-scrum-and-waterfall-project-management/
- “Waterfall and Incremental model in project management“, wikipedia-lab.org/waterfall-and-incremental-model-in-project-management/
- Waterfall or Agile? What methodology to choose for your project?, pm.mba/posts/waterfall-vs-agile/
- “Waterfall and Agile project management methodologies and when to use them“, agileprogramming.org/waterfall-and-agile-project-management-methodologies/
- “Waterfall vs Agile project management methodologies“, dobrojutro.net/waterfall-vs-agile-project-management-methodologies/
- “Agile vs Waterfall project management“, pgov.org/agile-vs-waterfall-project-management/
- “Scrum vs Kanban vs Waterfall: Differences and when to use each methodology”, managerspost.com/scrum-vs-kanban-vs-waterfall-differences/
- “Agile vs Waterfall Methodology – What are the differences“, islandjournal.net/agile-vs-waterfall-methodology-differences/
- https://www.businesspad.org/agile-vs-waterfall-difference-between-methodologies/: www.businesspad.org/agile-vs-waterfall-difference-between-methodologies/
- Agile vs Waterfall management methodology, http://www.kosovatimes.net/agile-vs-waterfall-management-methodology/
In this line of thinking, I would recommend that the Board of Directors be explained in detail what the difference between the two methods of work is, as well as what the advantages and disadvantages are.
If I were you, I would suggest that according to the projects assigned to us and the attitude of the Client, the right approach should be selected, as long as it is within the skills of the specific Project Manager.