Page History

...

The old framework for developing software.  This is characterized by front loading all of the planning to the n-th degree.  Waterfall works for physical products, but is risky for software because of the constantly changing requirements.  As a result, the nature of software prevents knowing the entire plan up front.

• • Dr. Winston Royce - In 1970, wrote a paper that evolved into the Waterfall Model of Software Development.
    • Waterfall Phases
      1. Requirements Analysis
      2. Design
      3. Code
      4. Integration
      5. Test
      6. Deploy
    • Risky and invites failure
      • Rarely have perfect knowledge of what is needed at the beginning
      • Know less about our project when we start out than we will know in the future.
      • The first day is the dumbest day of the rest of our project.
      • Waterfall projects eventually descend into anarchy
        • Low quality
        • Too much overtime

...

The new framework that leverages Agile for developing software.  Scrum takes advantage of Agile principles by creating a set of ceremonies (i.e. meetings) whereby time boxed Sprints continuously iterate through Planning, Prioritization, Feedback, Process Retrospection and Process Adjustment.

Roles in the Scrum Process

...