15 differences between traditional Waterfall and Agile Scrum approach

Here's a quick comparison of the plan-driven Waterfall methodology and Agile Scrum approach:

 

Core Waterfall Features:

  • Encourages conformance to processes and tools
  • Needs comprehensive documentation
  • Restricts new ideas
  • Promotes a process-centric environment
  • Depends on contract negotiation
  • Conforms to a plan
  • Requires continuous effort to motivate the team members
  • Require a huge rework to accommodate late changes
  • Results in a high cost of change
  • Encourages a detailed project plan
  • Leaves a large possibility of a mismatch between requirements and the final product
  • Is likely to have unhappy customers
  • Supports late customer feedback
  • Requires upfront decisions
  • Does not encourage regular interaction with business sponsors

Core Scrum Features:

  • Encourages people interactions
  • Promotes working software over comprehensive documentation
  • Encourages experimentation and new ideas
  • Promotes a people-centric environment
  • Encourages customer collaboration
  • Embraces change
  • Creates high performing, self-organizing, and motivated teams
  • Adapts late changes with minimal rework
  • Has a low cost of change
  • Is based on just-in-time planning principles
  • Reduces mismatch between initial business requirements and the final product
  • Is likely to produce delighted customers
  • Encourages fast and frequent customer feedback
  • Decisions wait till the last responsible moment (LRM)
  • Promotes high collaboration with the Product Owner

Learn Agile Scrum with my complete handbook, The Basics of SCRUM.

Please follow and like us:
Posted in Agile Scrum and tagged , , , , , , , , , , .

Leave a Reply

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