Chris Castiglione Chris Castiglione is an educator. He is the co-founder of One Month, and an adjunct professor at Columbia University Business School. His mission is to use storytelling as a tool to inspire positive change in the world.

Agile vs. Waterfall

37 sec read

Key Takeaways

When we look at the web development process, there are two ways to approach it: Waterfall and Agile.

Waterfall: Each team member finishes their piece of the project, then passes it on to the next person in the assembly line.

Agile: Everyone on the team works together to solve the problem simultaneously.

Let’s imagine building a website:

In a Waterfall situation, you’ll see that John makes the wireframe, WHILE Sarah makes the design, THEN Mike writes all the code.

On an Agile team, John would make a very rough wireframe, WHILE Sarah makes the design — WHILE Mike begins writing the first lines of code.

Neither method is necessarily GOOD or BAD. You might find that certain clients or projects demand Agile, while others are better suited to Waterfall. At the end of the day, they are just two different methods for launching a product.

Additional Resources to Keep You Learning

Read Lean UX (2013) by Jeff Gothelf and Josh Seiden.

Chris Castiglione Chris Castiglione is an educator. He is the co-founder of One Month, and an adjunct professor at Columbia University Business School. His mission is to use storytelling as a tool to inspire positive change in the world.

Leave a Reply

Your email address will not be published. Required fields are marked *