Software Implementation Strategies

When implementing a new software, software vendors likely use one of two implementation methodologies: The Waterfall Method and the Agile Method. When discussing implementation with your vendor, it’s important to keep in mind the pros and cons to each. Let’s break those down.

Waterfall Method

The waterfall approach is a step-by-step process, once you complete one stage, you move on to the next.

Screen Shot 2015-11-12 at 12.04.15 PM

Waterfall pros:

  • The method itself is simple to understand and easy to use.
  • Each phase has specific deliverables and a review process, making it very easy to manage. Phases are prepared and completed one at a time, they do not overlap.
  • This method works really well for smaller projects where requirements are well-defined.

Waterfall cons:

  • Once an application has reached the testing stage, it is difficult to go back and change something that occurred in the concept stage.
  • Because vendors are not able to show the customer anything until very late in the project lifecycle, there are high amounts of risk and uncertainty.
  • If a project is complex and object-oriented, the waterfall method would not be the best approach.

To know if the Waterfall Model is right for you, make sure that you communicate openly with your implementation and business process team to make sure they understand the challenges that your project presents.

Agile Model

Another method that teams like to use is the Agile Model. Here, projects are broken down into smaller “sprints,” giving multiple phases for testing and feedback.

Screen Shot 2015-11-12 at 11.48.56 AM

 

Agile pros:

  • Customer satisfaction by quick, continuous delivery of useful software.
  • Working software is delivered frequently.
  • Close, daily collaboration between business people and developers.
  • Continuous attention to technical and design excellence.
  • Regular adaptation to changing circumstances.
  • We can accommodate late changes in requirements.

Agile cons:

  • In some software deliverables, especially the large ones, it is sometimes difficult to assess the effort required at the beginning of the software development life cycle.
  • Due to the speed of the sprints, there is less emphasis on designing and documentation.

Much like the Waterfall Method, your implementation and business process team will be the most equipped to help you decide which method is best for your project.

In any project, we aim to choose the methodology that best fits your team and your project and we’re happy to discuss which method we chose for your project and why.