Waterfall and Agile are excellent methodologies used every day to deliver successful projects. Many people believe you have to choose a single methodology and use it exclusively. However, in the real world many companies are using both. They select the best methodology for the type of project they are delivering.

Another common scenario is combining the best from each methodology. This is especially true on major programmes with substantial development and infrastructure builds. For example, replacing a legacy ERP system with Software as a Solution (SaaS). Some parts of these programmes are a natural fit for Agile and some require the discrete test phases of Waterfall. 

Some Agile frameworks are suitable for infrastructure programmes, but many organisations prefer to use Waterfall for the infrastructure build and Agile for the development. This is one of the strengths of the methodologies: that they can be used concurrently on a programme.

Another consideration is the transition to methodologies. Agile has been around for over two decades, but some organisations have not used it. Don’t underestimate the learning curve for an organisation that has never used Agile. Many of them are reluctant to change the practices and methodologies that they have used to deliver projects successfully over a long period of time.

It isn’t uncommon to see companies using their own type of Waterfall or Agile. This can work well, but it’s critical that everyone is using the methodology consistently. 

What really counts is delivering the highest quality product possible on time and to budget. Whether you are using Agile or Waterfall, it’s essential that you understand the requirements, write quality code that can be maintained, test thoroughly, plan and prove the cutover, train the users, work with the support team to provide the information they require and support the users during the warranty period.