What is Waterfall Project Management?
Waterfall – American model, comes literally from the word “waterfall” and the word accurately describes the processes of performing tasks in the project. The next step is implemented only when the previous one is completely completed.
It is at stake and invested heavily in the preliminary design/architecture process of the project. Only when we have a fully finished design, we proceed to the implementation. Only when we complete the implementation of the entire project, we proceed to its testing, both functionally and integratively. Reference: Comparison of Agile, Scrum and Waterfall project management, EduWiki.me
When all the tests are successfully completed, we present the already completed project to the business/consumer and it can be used. It seems so, in the end, we have exactly this perfect result that we wanted in the beginning.
If we are working on small project size, this is a very good approach to implementation. Once the task is clear, the implementation time is short, we can quickly and easily complete a project, the result of which to deliver to the user. And to use it successfully. Reference: Agile, Scrum and Waterfall project management, ossalumni.org
The costs are likely to be small, a quick return on investment.
But! With this approach come to a lot of risks during the development of the project, if it is large and contains many smaller projects:
The fact that we deliver the result of the project only when it is fully completed and tested is associated with a long period of time. This is a time when the business/consumer has no idea what his desired product will look like. The market and circumstances will have changed. The risk is that we can deliver a product that is no longer needed on the market at all, there are many similar ones, competitive and even working. Reference: Waterfall and Incremental model in project management, wikipedia-lab.org
We have made something that has seriously gone beyond the needs of the business, but due to the fact that we have kept it isolated in the process of work, we have missed the opportunity to receive a timely adjustment. We have an unnecessary product that we will most likely never use. Or we will have to rework, but because the change will often be fundamental, it can cost the same investment as time and money as the original.
We have spent a lot of money, missing the moments for analysis and updating during production. We were able to use these analyzes to estimate and adjust costs. For example, instead of building from 0 to the given module that we need, we could use or buy ready-made, which at the moment someone else has already produced. This is often cheaper. Reference: Project Charter – real detailed example for Project Planning phases, worldforgemagazine.com
What is Agile Methodology
Agile – this is the methodology from Japan, comes from the word “flexible”. The project is implemented in short iterations, in small steps. At the end of each step, we aim to deliver a small part of the product, coordinated with the development and product teams. It has been tested and completed within the scope of the task. Reference: Agile vs Waterfall management methodology, kosovatimes.net
The purpose of frequent delivery by the development team of these small-scale tasks is – this is quickly delivered to the business/consumer. So we have the opportunity to immediately receive feedback on whether:
What is made is exactly what was required by the business/consumer
We can see mistakes from the first planning in time and change the direction of realization
We have an up-to-date product throughout the realization
We can profit from the product while production is still in progress
Thus, Agile helps a lot in reducing unnecessary labor, reduces development time and money. Reference: Waterfall or Agile? What methodology to choose for your project, PM.MBA The guaranteed project result is a product that is needed on the market, modern, and easy to expand, modify.
Agile is a particularly good approach when working on a large project, often made up of multiple subprojects. Requires good coordination, builds strong teams of professionals.
But I think it is a risky methodology if it is applied in the implementation of small projects. It will waste unnecessary time, it will probably increase the budget expenditure. Quality is another topic that needs special attention to both Agile and Waterfall methodologies. No matter what approach you choose the quality for the end-use is a top priority. Reference: Quality control and quality assurance in Project Management and Agile practices, scrumtime.org
Waterfall or Agile project management for your project. A conclusion.
These are the main specifics of Waterfall and Agile. You also have my opinion regarding their advantages and disadvantages.
I suggest that at the next meeting we talk about what our new project is and together we decide which approach, the methodology will be the most suitable for implementation, in order to finally have a successful, interesting, and needed product on the market.