An agile framework within which a Product Owner (PO), Development Team (DT) of 3-9 Developers and a Scrum Master (SM) work as the Scrum Team (ST) to build and sustain complex products of the highest, possible value. They do this work within a timebox called a Sprint; Sprints may be shorter, but may not last more than 30 days. Events, roles and artifacts are described definitively in the official Scrum guide: http://scrumguides.org/scrum-guide.html
Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
- Simple to understand
- Difficult to master
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 the body of this document.
Specific tactics for using the Scrum framework vary and are described elsewhere.
- Scrum: a Pocket Guide
- The Agile Pocket Guide: A Quick Start to Making Your Business Agile Using Scrum and Beyond by Peter Saddington (2012)
- Agile Software Development with Scrum by Ken Schwaber and Mike Beedle (2001)
- Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum by Craig Larman and Bas Vodde (2008)
- Scrum and XP from the Trenches by Henrik Kniberg (2007)