DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • The Evolution of Software Development: From Waterfall to Agile to DevOps and Beyond
  • Why Developers Must Be Part of the Customer Validation Process
  • One of Waterfall's Most Resilient Artifacts
  • What It Takes to Make Mainframe Modernization Work

Trending

  • AI-Assisted Refinement Preparation
  • Spring Security JWT Validation Best Practices
  • How to Format Articles for DZone
  • Stop Writing Database Migration Scripts: Declarative Schema Sync for Java

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Agile vs. Waterfall

Agile vs. Waterfall

A list of exactly what Agile does differently than Waterfall.

By 
Michael Sahota
·
Apr. 09, 16 · Opinion
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
10.9K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

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!

agile waterfall

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

Opinions expressed by DZone contributors are their own.

Related

  • The Evolution of Software Development: From Waterfall to Agile to DevOps and Beyond
  • Why Developers Must Be Part of the Customer Validation Process
  • One of Waterfall's Most Resilient Artifacts
  • What It Takes to Make Mainframe Modernization Work

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook