There are always many ways to solving problems. Rather, we should say there are different mediums to software development. Let’s just say there are more ways than one to bring your ideas to reality. At this point, you are in a dilemma of which of the ways you should exploit. In this context, agile and the old waterfall model are often put forward for constant debates on which is better. Aside from these two, there are others; V model, Incremental Model, RAD Model, Spiral Model, and Iterative Model can still be utilized. You will ask yourself; why is then the fuss and competition between the Agile Model and Waterfall Model when other models exist. The answer is not far-fetched, just read ahead.
You will definitely want to know more about these two; while agile was a response to the shortcomings of the waterfall model which is more traditional. The cons of the waterfall model have indeed increased the popularity of the Agile Model. Let’s just say one man’s loss is another’s gain. Since we already pointed out Waterfall is filled with issues that could affect the end result of your product, let’s adopt a holistic view of these problems and how the Agile Model could solve these problems.
Waterfall model cannot be adopted for large projects, it is best for small software development projects where progress will be assessed at the end of each phase. That’s even a minor issue with the Waterfall model, the lack of software testing until the final stage has always posed a problem to many start-ups. In the event of any discrepancy in the design, it will not come to the surface until the development stage is finished. What then happens when there is a need for change to the design? You will agree that this will defeat the aim of any project. There is no perfect software anywhere, what will help your start-up is the early identification of gaps and provision of support from onset to patch the shortcomings.
This is not to say the waterfall model is a dead end without good fruits, or the Agile Model which has come as a response to the problems of Waterfall model is fool and error proof. While utilizing the agile model, there is little or no regards for documentation. Not to talk of how the Agile model can disrupt age long philosophy and traditions of large companies who are strict with processes. For a newbie in software development, understanding Kanban, XP and other Agile methodologies can prove difficult.
The concern of this exposition is for start-up companies who will benefit from the quick, transparent and customer friendly approach of the Agile Model. As a new start-up, by involving the end users it will open doors for changes and further development. This is only possible through the Agile method as the Waterfall Model does not accommodate any break in the process of development.