SCRUM - alexanderteplov/computer-science GitHub Wiki
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
In a nutshell, Scrum requires a Scrum Master to foster an environment where:
- A Product Owner orders the work for a complex problem into a Product Backlog.
- The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
- The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
- Repeat
The emergent process and work must be visible to those performing the work as well as those receiving the work.
The Scrum artifacts and the progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems. To help with inspection, Scrum provides cadence in the form of its five events.
If any aspects of a process deviate outside acceptable limits or if the resulting product is unacceptable, the process being applied or the materials being produced must be adjusted. The adjustment must be made as soon as possible to minimize further deviation.
Commitment, Focus, Openness, Respect, and Courage
The fundamental unit of Scrum is a small team of typically 10 or fewer people. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.
The Developers are always accountable for:
- Creating a plan for the Sprint, the Sprint Backlog;
- Instilling quality by adhering to a Definition of Done;
- Adapting their plan each day toward the Sprint Goal; and,
- Holding each other accountable as professionals.
The Product Owner is accountable for:
- Maximizing the value of the product;
- Developing and explicitly communicating the Product Goal;
- Creating and clearly communicating Product Backlog items;
- Ordering Product Backlog items;
- Ensuring that the Product Backlog is transparent, visible and understood.
The Scrum Master serves the Scrum Team.
- Sprint
- Sptint Planning
- Daily Scrum
- Sprint Review (collecting and analysing sprint results, preplanning)
- Sprint Retrospective