Scrum vs Waterfall

Discover Scrum, Waterfall, scope, requirements, activities, estimation, process, success, results

Both Scrum vs and waterfall methodologies have their strengths, so it all depends on the type of project and its environment. Both approaches have effective planning followed by execution, monitoring and controlling.
In a nutshell:

  1. It is better to use Scrum if there are lots of unknowns, where the projects are more complex, difficult to define detailed requirements upfront and therefore to define estimates at the beginning of the project.
  2. It is better to use the traditional approaches when there are few unknowns, project is less complex, easy to define exact requirements upfront and therefore easy to estimate and plan the project from the very beginning.

Scrum Scope, Requirements, Activities, Estimation, Process, Measure of success and Results definition:

  1. Scope is not clearly defined and Product will gradually appear during the project
  2. Requirements change frequently and customer learns more about what they want as the project goes on
  3. Activities cannot be well defined upfront
  4. Estimating and planning is difficult
  5. Process is iterative with numerous cycles and each cycle depends on the previous one
  6. Success is mostly measured by customer satisfaction
  7. Incremental results have value and can be used by users

Waterfall Scope, Requirements, Activities, Estimation, Process, Measure of success and Results definition:

  1. Scope is clearly defined upfront with clear product description available upfront and similar projects were done before
  2. Requirements are well defined up front with few change requirements expected during the project
  3. Activities can be well defined upfront
  4. Estimating is possible and reliable
  5. Process is more long term and Project might be split into phases
  6. Success is mostly measured by achieving the project goals ( time, cost, scope…)
  7. Users cannot start using the products until the project is complete

Get the book