According to the official definition, “Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.”.
Scrum is a simple, empricial framework which helps us deal with unpredictable, complex problems.
Scrum implements an empirical process where progress is based on observations of reality, not fictitious plans.
The Scrum Framework
Small team of people, consists of:
- Scrum Master (opens new window): TBC
- Product Owner (opens new window): TBC
- Developers (opens new window): TBC
Scrum Pillars (opens new window)
- Transparency: This means presenting the facts as is
- Inspection (by the Scrum Team): Check the product, processes, people, and practices and you work.
- Adaptation: Continuous improvement base on the result of Inspection
The main goal of these events is to create regularity and minimize the need for meetings.
- Sprint (opens new window): It is the heart-beat of scrum, which encompasses all the work necessary to achive the Product Goal. It's a fixed-length event of one month or less.
- Sprint Planning (opens new window): Initiates the sprint by laying out the work to be done.
- Why is this sprint valuable?
- What can be done this sprint?
- How will the chosen work get done?
- Outcome: Sprint Backlog
- See: Definition of Done
- Daily Scrum (opens new window):
- Inspect progress toward Sprint Goal
- Synchronize activities
- Plan for the next 24 hours
- Team members often meet immediately after the Daily Scrum for detailed discussions or replan.
- It's 15 minutes (timebox) to keep everyone focused
- It happens at the same time & location to reduce complexity
- It happens everyday
- It's by developers and for developers
- It's not a status meeting (update on the tasks they've been working on)
- Sprint Review (opens new window):
- Inspect the outcome of the Sprint & determine future adaptation
- Progress toward Product Goal is discussed with stakeholders
- Maximum of 4-hour timeboxed event for a 4-week Sprint
- See: Backlog Refinement
- Sprint Retrospective (opens new window):
- Inspect individuals, interactions, processes, tools, and their Definition of Done.
- Identify the most helpful changes to improve effectiveness.
- It's timeboxed to a maximum of 3 hours for a 4-week Sprint.
Scrum Artifacts enable inspection & adaptation by providing transparency on the work and the value.
- Product Backlog (opens new window):
- Definition: An emergent, ordered-list of what's needed to improve the product.
- Commitment: Product Goal, which is a future state of the product that helps Scrum Team to plan their future Sprints. It's either fulfilled or abandoned.
- Sprint Backlog (opens new window):
- Sprint Goal (Why)
- Set of Product Backlog Items (What)
- Actionable plan for delivering the Increment (How)
- Commitment: Sprint Goal, which is a single commitment for the sprint. It has flexibility in terms of the exact work needed to achive it.
- Increment (opens new window):
- Concrete stepping stone toward the Product Goal.
- Each increment is added to the previous
- All increments should work with each other
- Commitment: Definition of Done, which is a formal description of the minimum quality required for an increment to be accepted.
Scrum works not because it has three roles, five events, and three artifacts, but because it adheres to the underlying Agile principles of iterative, value-based incremental delivery by frequently gathering customer feedback and embracing change.
External, introductory resources
- What is Scrum? (opens new window): A short overview of what Scrum is
- Scrum Glossary (opens new window): A short Scrum glossary with the most essential terms
- Scrum Values (opens new window): Pracical examples of applying Scrum Values
More external resources
- Sprint planning (opens new window)
- Daily scrum (opens new window)
- Demo/Review meeting (opens new window)
- Sprint retrospective (opens new window)
Scrum in IxDF