Agile vs Waterfall

Here is my one page summary of some key differences between Agile and Waterfall.

(I created this when I was asked to explain this to an exec earlier this month about this and I didn’t have anything good in my toolkit nor could I find something on google.)

A comparison of key elements of Agile and Waterfall delivery approaches.

Key Differences between Agile and Waterfall

  • In waterfall, the focus is on creating documents that capture what is needed. In Agile, the focus is on working software.
  • In waterfall, people tend to work in sequence – like a relay race. In Agile, people collaborate – like a soccer team.
  • In Agile, the focus is on working together as a team and learning how to improve. There is a different mindset or culture.
  • In Waterfall, there is usually a messy whirlpool at then end where people abandon documentation to start figuring out how to make things work and/or what users really want.
  • In Agile, software is delivered incrementally so it is much easier to predict delivery dates.

If you have your own one page summary, please add a link in comments section so we can all learn from each other.

Print Friendly
Tagged with:
, , , , ,

Find Content

Adoption Agile Agile2009 Agile Failure Agile in the Large Agile Tour Toronto Change Artist Christine Day Coaching Communication Container Craftsmanship Creativity Empathy Facilitation Fear Games and Simulations Hierarchy Kanban Kotter Leadership Lean Management Observing Organizational Change Organizational Culture People Personal Growth Production Product Strategy Project Management Red Pill Safety Scrum Strategic Play Teamwork Technical Practices Training Training from the Back of the Room Transformation Transition Trust VAST Vulnerability XP

Leave a Reply

0 responses to “Agile vs Waterfall”

  1. […] Sahota describes it well with an infographic on his blog […]

Leave a Reply

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