Agile Method vs Waterfall Method

Agile Method vs Waterfall Model

Brenda Smith

CMGT/410

May 30, 2016

Curtis Proffitt

Agile Method vs Waterfall Model

In analyzing two different methods for managing a project I have taken a single project and created two models one using the agile method and the other using the waterfall model. The project is the development of a mobile application and is created using Microsoft project version 2013.

In the waterfall model also called traditional a sequential set of steps or tasks are setup and a timeline is created. This is done during the first stage also known as the requirement stage. All of the specifications, start dates and duration are determined during this step. This is the point where the customer or stakeholders have the most input. Once this stage is complete there is no allowance for changes in scope or any other requirements including budget. If there is any over runs such as time or budget cuts usually have to be made by lowering project quality and stakeholder satisfaction. Once the precedent relationships are added, the plan resembles a waterfall. The waterfall model does not allow for backward scalability. Therefore, incorporate changes in scope or phases, the project will have to be recreated using the new perimeters. This in turn will lower the customer and stakeholders confidence in the project..

The agile method incorporates parts of other methods that share common qualities. The agile method has the ability to adapt to changes in the scope of the project. There are five levels of planning within this method: vision, roadmap, release, sprint and feature. Tasks are grouped together in short periods of time are called sprints. The work performed within a sprint is called a feature. Sprints and features can be easily altered to accommodate stakeholders’ changing requirements. On the agile project plan, the sprints, features and backlog are clearly visible.

In the waterfall model there is no allowance for...