Skip to content

What is the difference between Waterfall and Agile?

Agile Waterfall drawing diagram
Flickr/visualpunch; cropped

There’s a great analogy to describe the difference between the Agile and Waterfall methodologies. Waterfall is like an orange- you need all the segments before it is complete. Whereas an onion, Agile, has layers and can be complete after the first layer if necessary, or you can keep building until it’s finished.

There are loads of sayings and assumptions about both Agile and Waterfall, but Agile is the new buzzword. Agile, according to clients, is considered ‘faster and cheaper’, and I wonder if this is why it is becoming more and more popular? I think the real question is, though:

Do Clients Really Know What Agile Is?

Surely it must be difficult for a client to determine what they need for their projects, so most clients will need guidance from their chosen agencies, to ensure the right method is being used to achieve their digital visions. Here are some basic tips to help explain the more complicated elements to clients and ensure they are fully on board.

1. Use visual aids to explain

When trying to explain how the Agile methodology will work, it can be difficult for clients to understand the different sprints, meetings and reporting involved. During the pitching stage, use visual aids and exercises to help them understand how you will move forward. A great example is the use of Lego – building a Lego village with Agile rules to represent the different stages of the project.

2. Ensure the method fits the client

If the company used more of a Waterfall method in previous projects internally, then maybe an Agile method for their digital needs won’t work effectively or efficiently for them. It is your responsibility as the agency to make sure you inform the client appropriately. Why change the project process if it has worked well before?

3. Using Agile should make things easier, not harder

If it’s easier to use Waterfall, then use it! Don’t make it harder for yourself and the client just to be the ‘cool kids in town’. It’s important to be honest with your client and make it simpler for your agency- don’t be blinded by buzzwords.

4. Ensure your process is perfect

When you go to pitch Agile to a client, make sure you know your process inside and out. If you don’t use Agile in a pure sense, then you need to make sure you can communicate your process to your client perfectly. Know what you’re talking about!

5. Trust from your client is key

Implementing Agile, particularly with a new client, means you need them to trust you more than ever. You need to make sure that your client can hand their projects over to you without any concerns, and know that they will be involved every step of the way. Honesty is the best policy with Agile, and honesty will allow the client to trust you.

6. Consider a hybrid Agile/Waterfall solution

Whether you want to offer oranges or onions to your clients, make sure that you know what you are actually offering, and remember you can offer them a hybrid version as well. This has worked with various agencies and projects, and it could be the best solution for your client.

 

Is Agile really ‘faster and cheaper’? That will be for the client and agency to decide, dependent on the projects, but I think it’s fair to say that Waterfall can be ‘faster and cheaper’ as well.

Topics

Register for Free

Get daily updates and enjoy an ad-reduced experience.

Already have an account? Log in