Waterfall v.s. Agile – Which One Will Work Best For Your Project

Is there a way to shave years off of the trial and error implementing Agile?
Find Out Now.

It’s almost impossible to have a successful product without a successful process. In this video, we’ll explain two different processes: Agile and Waterfall.

At Todaymade, we understand our process is as important as our products. In fact, our process is not only what makes us different, it’s what makes us successful. So, what does our process look like? Well, it’s an agile approach. To learn more about the agile approach check out this quick video.

Video Script:

Meet Harry.
Harry owns a car dealership.
He needs a web application that will help him manage his current customers and their needs.
Looks like your due for an oil change.

Meet Sally.
Sally owns her own beauty salon.

She needs a web application that will help her manage her clients and the services they enjoy.
Would you like to use the same color in your hair as last time?

Harry: Chooses to use traditional development also know as the waterfall approach.
In the waterfall approach
Decisions are made at the beginning of the project.
During development the customer is not involved with the creative team.
Harry is only able to provide feedback at the end of the project when the creative process has been completed.

Sally: Chooses to use the agile approach.
Agile development focuses on one area of the project at a time.
During development Sally works with the creative team.
Sally is able to provide feedback throughout the entire creative process.

When Harry sees the final project. He realizes he needs a login feature.
Harry is disappointed when he is told changes can’t be made.

Harry used the waterfall approach.
Like water, that flows down a waterfall cannot come back, it is not possible for Harry to adjust the scope his project once its been developed.

As Sally reviews her project with the creative team; together they decide a profile feature would provide increased value.
Sally is excited when the team tells her they can add it.
Sally used the agile philosophy.
With agile, the client and creatives constantly work together to prioritize what is going to be the next feature that provides the MOST business value.

Every project has three main components:
1. Cost
2. Scope
3. Schedule

In order for Harry to get changes made. He is forced to spend more money and wait longer.
In order for Sally to get her changes made she works with the creative team to decide what features will provide the most value.

The bottom line:
Harry is left with a mediocre product and no money.
While Sally is left with a superior product and extra cash to celebrate her success with.

The next time Harry needs a web application.
“I’ll have what she’s having.”