Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Agile vs. Waterfall

DZone's Guide to

Agile vs. Waterfall

A list of exactly what Agile does differently than Waterfall.

· Agile Zone
Free Resource

The Agile Zone is brought to you in partnership with Techtown Training. Understand how your role fits into your organization's DevOps transformation with our DevOps eBook.

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.

Image title

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

Key Differences

  • 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.

Enjoy!

Adopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap, brought to you in partnership with Techtown Training

Topics:
agile ,project management ,waterfall

Published at DZone with permission of Michael Sahota, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}