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

What characteristic should requirement possess? All significant requirements included. No items have been left for future definition. Incompete if: - Non functional requirements missing; - Hidden assumptions; - Too general statements Conflicting terminology, contradictory required ac...
Story Points in estimating work One of effective way to estimate the work in software development is to use Story points. The story points are based on size and complexity, not duration.  They are also become unitless, they not measured by time or another units. One other good ...
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
Definition of DONE in Software Developent Let’s imagine, that at the end of every iteration in SCRUM or any other Agile Software Development method, the developer is coming to you and saying: "I'm done with this functionality!" But you of course ask: "What do you mean done? Are you done or...