Scrum
A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. It is not a methodology, but a framework for developing, delivering, and sustaining complex products.
Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Lean thinking reduces waste and focuses on the essentials.
- Type: Agile Framework
- Core Idea: Iterative and Incremental Development
- Key Elements: Sprints, Roles, Events, Artifacts
Key Concepts
The building blocks of the Scrum framework.
Sprints
Sprints are the heartbeat of Scrum, where ideas are turned into value. They are fixed length events of one month or less to create consistency. A new Sprint starts immediately after the conclusion of the previous Sprint.
Scrum Team
The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies.
Scrum Events
The Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts. These events are Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective.
Scrum Artifacts
Scrum’s artifacts represent work or value. They are designed to maximize transparency of key information. The Product Backlog, Sprint Backlog, and Increment are the three Scrum artifacts.
Product Owner
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.
Scrum Master
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
Implementation & Strategy
Costs, timelines, and strategic considerations for adopting Scrum.
Estimated Project Costs
Scrum is a framework for managing projects, so it doesn't have a direct cost. However, there are costs associated with training and certification, as well as the cost of the tools that you use to manage your Scrum projects. These costs can range from a few hundred dollars to several thousand dollars per person.
Implementation Strategy
A typical Scrum implementation starts with a single team. As the team becomes more comfortable with the framework, it can be rolled out to other teams in the organization. It's important to have a dedicated Scrum Master to help guide the team and to ensure that the framework is being used correctly.
Comparisons
How Scrum stacks up against other Agile frameworks.