What is Scrum?
According to the Scrum Alliance, Scrum is an Agile framework for completing complex projects. Scrum originally was formalized for software development projects, but it works well for any complex, innovative scope of work.
According to the 9th State of Agile Survey, more companies — and bigger companies— are scaling and embracing Agile as part of the larger vision to deliver software faster, easier, and smarter.
- Ninety-four percent (94%) of all organizations surveyed now practice Agile.
- In 2013, the majority of respondents had fewer than 1,000 people in their software organization.
- In 2014, approximately 35% of respondents had more than 5,000 people in their organization, and 20% worked in very large organizations with more than 20,000 people.
- In addition, 45% of this year’s respondents worked in development organizations where the majority of their teams are agile. Contrast this with the 2009 report, which found that (31%) of the respondents worked in organizations with only zero to two teams practicing agile.
Of all the Agile frameworks, Scrum is arguably most widely adopted. Professionals from around the world and in a variety of industries are using Scrum to position their teams for greater success.
11 Things To Know About Scrum
- Scrum is a framework for developing and sustaining complex products. This definition, according to Scrum.org, consists of Scrum’s roles, events, artifacts, and the rules that bind them together.
- Founded by Scrum co-creator Ken Schwaber, Scrum.org provides Professional Scrum Assessments and Training through our global community to help individuals, teams and organizations improve their ability to deliver software with higher levels of value and agility. Ken Schwaber collaborated with Jeff Sutherland to develop Scrum - the Scrum Guide is written and provided by them. Together, they stand behind the Scrum Guide and Scrum.org.
- 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 lightweight, simple to understand and difficult to master, according to ScrumGuides.org.
- Scrum, according to ScrumGuides.org, 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.
- Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.
- Scrum prescribes four formal events for inspection and adaptation, as described in the Scrum Events section of this document: Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective.
- The Scrum Process Framework, as detailed by the Scrum Guides, consists of a Scrum Team - a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
- Scrum also features a Development Team, made up of professionals who do the work of delivering a potentially releasable Increment of 'done' product at the end of each Sprint. Only members of the Development Team create the increment. Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness, according to Scrum Guides.
- The heart of Scrum is a Sprint, which, as defined by Scrum Guides, is a time-box of one month or less during which a useable, and potentially releasable product Increment is created. Sprints best have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. Sprints contain and consist of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. Sprints are limited to one calendar month.
- The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. The Daily Scrum is held at the same time and place each day to reduce complexity, according to Scrum Guides.