Waterfall vs. Scrum

What is “Waterfall”?

Waterfall is a plan-driven project management in software development. So normally you work with Gantt charts & Microsoft Project, you have Start & end dates and Project phases. In Waterfall, development phases have force defined order: first you write Requirements, than you Design and Develop your application and at the end coming Testing and Deployment phase.

Waterfall vs. Scrum

Waterfall

Requirements documents
Resistant to change
-Change is a bug
Poor “customer” involvement
Start-to-finish Project Plan
Large team size
Multiple phases
-eventual delivery
Contract driven
-Fixed feature set

Scrum

Just-in-time requirements
Continuos change
-Change is a feature
Permanent “customer” involvement
Plan for the Sprint. Product Backlog
Small teams (3 to 9 people)
Increment every Sprint
Contract is closer to T&E
-Likely not a fixed feature set

Related Post

3 Levels of requirements in Agile development In Software Development Requirements have 3 levels: - expanded description of customers business - business point of view requirements - functionalities which should be made in our application Example: “We need a tool for selecting big data...
Scrum with Multiple Teams Scrum says a team should be 3 to 9 people. But sometimes you want or need to go faster, so you add more teams. This process calls Multi-team Scrum or Scaled Scrum. Challenges of Multi-team Scrum Now you need to coordinate not only a single tea...
Integration Team in Multi-team Scrum If one team in Scrum not enough, it's advisable use Multi Team. But here you get one more problem - how to manage more than one team. And the answer: use the Integration team. With Multi Team your Scrum will look a little bit different. Multi-team...
User Story Scenarios Each User Story needs to be testable, need to demonstrate, that requirement has been met. Here is effective formula, which demonstrate, that specific user story has been met: Given , When Then