- Scrum Tutorial
- Scrum - Home
- Scrum - Overview
- Scrum - Framework
- Scrum - Roles
- Scrum - ScrumMaster
- Scrum - Events
- Scrum - Artifacts
- Scrum - User Stories
- Scrum - Burn-Down Charts
- Scrum - Estimation
- Scrum - Tools
- Scrum - Benefits
- Scrum - Certifications
- Scrum - FAQs
Scrum - Framework
Scrum is a framework for developing and sustaining complex products. Ken Schwaber and Jeff Sutherland developed Scrum. Together, they stand behind the Scrum Rules.
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 process framework that has been used to manage complex product development since the early 1990s. Scrum is not a process or a technique for building products; 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 development practices so that you can improve.
The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage.
The rules of Scrum bind together the events, roles, and artifacts, governing the relationships and interaction between them. The rules of Scrum are described throughout this tutorial.
Note - Across the industry, there are misconceptions that Scrum means no documentation, scrum team consists of only developers, and so on. It is not entirely so; we will give clarifications on these in later sections.
Scrum Process Framework
In Scrum, the prescribed events are used to create regularity. All events are time-boxed events, such that every event has a maximum duration. The events are described more elaborately in the subsequent chapters.
The heart of Scrum is a Sprint, a time-box of two weeks or one month during which a potentially releasable product increment is created. A new Sprint starts immediately after the conclusion of the previous Sprint. Sprints consist of the Sprint planning, daily scrums, the development work, the Sprint review, and the Sprint retrospective.
In Sprint planning, the work to be performed in the Sprint is planned collaboratively by the Scrum Team.
The Daily Scrum Meeting is a 15-minute time-boxed event for the Scrum Team to synchronize the activities and create a plan for that day.
A Sprint Review is held at the end of the Sprint to inspect the Increment and make changes to the Product Backlog, if needed.
The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. In this meeting, the Scrum Team is to inspect itself and create a plan for improvements to be enacted during the subsequent Sprint.
Scrum is a process framework that defines certain rules, events, and roles to bring in regularity. However, it can be adapted to any organization, based on needs, provided the basic scrum rules are not violated.