Waterfall vs Agile

Waterfall vs Agile

Learning Mudra, Category - PMP

The two methods : Waterfall and Agile

In the beginning of every project, the members, especially the leaders of the project have to make a crucial decision. They have to choose the framework that they would work on during the duration of their project. The two most prominent frameworks are - waterfall method and agile method. Some of the readers must have been confused at the type of name, some must be giggling. Cluelessness is widespread. Don’t worry, we will try to explain these 2 methodologies. Software projects these days, use waterfall or agile method. So let’s explore these 2 in detail and see when to use which one.

Waterfall meaning

Let’s start with this one first - The Waterfall method. A silly name, but in its defence; it is the traditional method in project management. The origin of this is that, umm, picture a waterfall. How does the water fall? Water falls down from the opening of the mouth or source of water straight downwards where it accumulates. That is what waterfall method is. It originates/starts at the top and moves down in a process. It follows a proper chain of things or processes coming downwards. So in essence, waterfall follows a rigid process of operation.

Agile meaning

Now, agile is complete opposite. Agile seems like a very sophisticated name and it is. Even the process is very sophisticated and unique. One agile project is different from other agile project as steps may differ. Even if the starting points of both projects were the same. That is the uniqueness of agile. Picture a waterfall for agile and remove gravity. The water goes all over the place randomly before reaching the water at the base where it accumulates. So, there is a randomness in agile. A flexibility.

Waterfall explained and steps

Now let us explore waterfall in a more complex and practical manner now that we know the basic difference. Waterfall is a linear process of doing a project. And there is a process followed, traditionally.

• Requirements gathering-

In this step we see what our requirements are and what we require. We will need to conduct proper research, the primary one.

• Design-

We specify the framework during this step like what resources we need to choose. For software it can be what coding language we use.

• Implementation-

At this stage the work takes place. We work according to requirement and design and implement.

• Verification or testing-

We test whether what we have done works fine or not. We see its functionality and see if any changes are needed.

• Maintenance-

Product or service are finished by now. We just see it continuously functions properly.

Benefits & disadvantages of Waterfall and Agile

Waterfall method is straight forward and has customer interaction at just the beginning of the journey where we do the survey and ask them what their preference is. Then at the end to track their satisfaction and make any changes if required. Moreover it is easily measurable. The cost incurred is lower as customer interaction is lower in waterfall method. This is less time consuming. The disadvantages can be that customer could be not satisfied with the end result or the product and all effort could go to waste. The need of customer existed when we did survey in the beginning and not anymore.

For more information on Agile and Waterfall; get in touch with us at +91-987-123-7360 or email us at info@learningmudra.com

Agile explained

Agile on the other hand is iterative and a proper team work based approach. Instead of processes, the work is in the form of sprints. Customer is frequently in touch during this method. Under this method processes are done by dividing them into small goals. Work is prioritized too in this method and higher priority is done first obviously. It requires all of the processes mentioned in waterfall method to be done simultaneously in different stages. So in that sense it is more flexible. The work is constantly monitored and tracking is done. Tracking of where is a scope for improvement is also done. The process works on feedback from customer and from team and it is intuitive to an extent. They could start doing something but reach at a different goal altogether.

Agile benefits

The benefits of this method are many. For starters, customer is highly involved at every step so instant feedback is provided which leads to improved product. Changes are made at every step as and when required. Customer too will feel like he is a stakeholder, given how much he is involved in the entire operation. It is a user oriented method. And a highly flexible one. It is suitable when an advance level project needs to be undertaken. For example in an app: basic features will be released. Then slowly more will be added as each will be made to perfection. This is the recipe for agile, a recipe for superior products as well as more successful projects.

Which one to choose

So, to conclude, it depends on the type of project you undertake, this can determine which of the two above explained methods you should go for and this will determine how much resources you will need to perform these tasks. For any assistance related to these two, as well as any query egarding PMP, ACP, or any other training of your interest, write to us at training@learningmudra.com