Scrum is a lightweight yet powerful framework for developing, delivering, and sustaining complex products. It is not a process, technique, or definitive method; rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.
The Pillars and Values of Scrum
Scrum is founded on empiricism and lean thinking. It is built upon three pillars and five values.
| Pillars (TIA) | Description |
|---|---|
| Transparency | The emergent process and work must be visible to those performing the work as well as those receiving the work. |
| Inspection | The Scrum artifacts and the progress toward agreed goals must be inspected frequently to detect undesirable variances. |
| Adaptation | If an inspector determines that one or more aspects of a process deviate outside acceptable limits, the process must be adjusted. |
| Values (FORCC) | Description |
|---|---|
| Focus | The team focuses on the work of the Sprint and the goals of the Scrum Team. |
| Openness | The Scrum Team and its stakeholders agree to be open about all the work and the challenges. |
| Respect | Scrum Team members respect each other to be capable, independent people. |
| Courage | The Scrum Team members have the courage to do the right thing and work on tough problems. |
| Commitment | People personally commit to achieving the goals of the Scrum Team. |
The Scrum Framework (3-5-3)
Scrum is defined by its three roles, five events, and three artifacts.
| Category | Components |
|---|---|
| 3 Roles | Product Owner, Scrum Master, Development Team |
| 5 Events | The Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective |
| 3 Artifacts | Product Backlog, Sprint Backlog, Increment |
Example Scenario
A Typical Sprint
A team starts a two-week Sprint with a Sprint Planning meeting, where they select work from the Product Backlog and create a Sprint Backlog. Every day, they hold a Daily Scrum to coordinate their work. The Scrum Master removes any impediments. At the end of the Sprint, they demonstrate the working software (Increment) to stakeholders in the Sprint Review and then discuss how to improve their process in the Sprint Retrospective.
Why Scrum Matters
- Provides a Simple Structure for Agility – It is the most popular agile framework because it is simple to understand but difficult to master, providing a clear structure for applying agile principles.
- Delivers Value Incrementally – It focuses on delivering a valuable, working product increment every Sprint, which allows for rapid feedback and a faster return on investment.
- Manages Risk and Uncertainty – The iterative nature of Scrum allows teams to inspect and adapt, reducing the risk of building the wrong product.
- Empowers Teams – It is built on the principles of self-organization and cross-functionality, which leads to higher team morale, ownership, and productivity.
See also: Agile, Product Owner, Scrum Master, Development Team, Product Backlog, Sprint Backlog.