In this article, briefly, I enclose information about the terms Waterfall and Agile.
The creation and implementation of a project, in each industry, is always subordinated and occurs in certain phases:
- Business idea – project initiation;
- Feasibility Study and Analysis;
- Development and Design;
- Planning and Budgeting;
- Creating the project;
- Market Realization;
- The operational life of the project; Reference: “Agile vs Waterfall Methodology – What are the differences”, https://www.islandjournal.net/agile-vs-waterfall-methodology-differences/
As a sentence of the process of creating a project, I will use the words of Napoleon Hill: “First comes thought, then, the organization of that thought into ideas and plans, then transformation of those plans into reality. The beginning, as you will observe, is in your imagination. ”
As a result of this sentence comes the question: How? How can an idea be realized and turned into a real project? What is the path, the steps?
The answer to this question, strange as it may sound, lies in “philosophy”:
The “Understanding and Concept” of the company for creation, development, and realization of the project on the one hand, and the “Philosophy and Culture” of the client/user of this project – on the other hand, related to the specific market conditions and business specifics. Reference: “Agile vs Waterfall management methodology”, https://www.kosovatimes.net/agile-vs-waterfall-management-methodology/
In this regard, Waterfall and Agile are methods, methodology for project management, ie. Different “philosophies” for structuring, organization, processes, relationships, and relationships in the implementation of a project.
Both (and many other) methodologies are created and implemented as a result of specific market conditions, business needs, and consumption, at specific times and with clearly defined goals, roles, and tasks, both for the business and for the client. Both methodologies have their positive and negative characteristics, pros and cons. Over time and gaining experience, both methodologies have been modified, supplemented, expanded, etc., with the main goal being only one: “winning the war for His Majesty the Client” – price, quality, time, profitability, and profit. Reference: “What is Kanban methodology”, https://wikipedia-lab.org/what-is-kanban-methodology/
Waterfall project management
Waterfall – is a linear, consistent methodology of implementation of processes from the beginning to the end of the implementation of a project (such as a waterfall or production line). The life cycle of the project is divided into separate phases/stages of development, as the course of development of the project is consistent, ie. After the completion of one phase – the next begins. Reference: “Waterfall and Incremental model in project management”, https://wikipedia-lab.org/waterfall-and-incremental-model-in-project-management/ At the beginning of the project, all its characteristics, specifics final goal, and result (task) are defined, the implementation of the project is planned in detail and carried out in successive steps, based on schedules, specifications, plans, etc. In the course of the project implementation, what is set and developed at the beginning is implemented for the specified time, and the result is = planned. Neither better nor worse. Reference: “Agile, Scrum and Waterfall project management”, https://ossalumni.org/agile-scrum-and-waterfall-project-management/
Any change from what was originally planned is costly, especially as the project progresses, so it is avoided, necessarily. The investment process (investment cost) for the implementation of the project starts with its beginning, based on a pre-calculated budget, and continues until its end, ie.
The investment is in the amount of the full volume of the project, until the creation of the final, planned result (project/product). Finally, comes the assessment of the Client, respectively the finding: this project is successful/unsuccessful. Reference: “Comparison of Agile, Scrum and Waterfall project management”, https://eduwiki.me/comparison-of-agile-scrum-and-waterall-project-management/
In this sense, the investment income from the project – unpredictable.
Examples of project implementation using the Waterfall methodology:
- Manufacture of household appliances (white/black);
- Car production;
Etc. Each industry is associated with consistent processes in the construction of the project. Reference: “Waterfall or Agile? What methodology to choose for your project?”, https://pm.mba/posts/waterfall-vs-agile/
Agile – is a methodology for project implementation, inspired and created mainly by the imperfections and inapplicability of the Waterfall method for specific industries (IT, software, etc.), implemented at specific times, market conditions, and different “philosophy and culture” of the Client. Reference: “Waterfall and Agile project management”, https://phron.org/waterfall-and-agile-project-management/ The main “philosophy” of this method, expressed in three sentences, is:
- What matters is the goal, not the way it is achieved;
- The ultimate goal of the project consists of many smaller goals;
- Phased delivery, quick feedback from the customer, quick changes and adaptation of the project;
Agile divides the project into many stages (called sprints), each with a specific “mini-goal” and a short lead time (usually 2 weeks). The purpose of this approach is implementation and delivery at a very early stage of the project (literally at every step), with minimal investment costs, receiving timely evaluation from the client, fast and with minimal investment costs adaptation of the project based on feedback.
This methodology mainly relies on the high expertise of the contractors (human resources) and that they determine the way to reach the goal (at each stage of the project), based on their experience, choice of strategy, and expert potential. Reference: “Waterfall vs V-Model vs Scrum vs Kanban”, https://newia.info/waterfall-vs-v-model-vs-scrum-vs-kanban/
The processes that accompany each two-week “sprint” occur simultaneously, without a specific plan and rules, ie. Something is made, tested – worked – delivered. The processes are accompanied by the so-called Daily Standup (to know who works on what and what), which are managed by a special manager and …. that’s how the system works.
Respectively, the Client receives a part of the project/product earlier, starts working with it, starts modifying and/or changing it in the course of the implementation, thus being a direct participant in the process, in terms of feedback, which provides after each stage of implementation.
The investment cost is smaller in size (covers only the first and/or the first few steps of development) in the initial course of the project, but in reality – at the end of the process, often exceeds the initial budget due to various changes and additions to the product. project. Investment income is faster, usually increasing with the development of the project (if it develops in the right direction), but maybe short in time.
One of the disadvantages and risks of this method is the real possibility in the process of creating the project and after the many numbers of stages, changes, and additions… to lose the ultimate goal, ie. the project to be realized in a completely different form from the one originally conceived. Reference: “Agile vs Waterfall: The Difference Between Methodologies”, https://www.businesspad.org/agile-vs-waterfall-difference-between-methodologies/
In conclusion, both methodologies have achieved market penetration, both – have positive and negative characteristics, and both – are fully applicable in some business segments and not applicable in others.
Ultimately, a good result in the implementation of a project/product depends on the specifics, organization, and resources of a company on the one hand and the other – the right strategy, concept, and organization of implementation.