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
Over 2 million developers have joined DZone.
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

  • The Middleware Gap in AI Agent Frameworks
  • GenAI Isn't Solving the Problem Most Development Teams Actually Have
  • More Tests, More Confidence? Test Suites Are Investment Portfolios
  • The Lethal Trifecta Is Hiding in Your MCP Server
  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 user avatar
Michael Sahota
·
Apr. 09, 16 · Opinion
Likes (6)
Comment
Save
Tweet
Share
10.8K Views

Join the DZone community and get the full member experience.

Join For Free

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

The likes didn't load as expected. Please refresh the page and try again.

  • 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