Scrum

Scrum
Name	Scrum
Type	Agile framework
Origin	Rugby union
Creator	Jeff Sutherland; Ken Schwaber
First published	1995
Industry	Software development
Website	Scrum.org; ScrumAlliance.org

Scrum

Scrum is an iterative, incremental framework for product development widely used in Software development, Information technology, Telecommunications, Aerospace and Automotive industries. It traces conceptual inspiration to Rugby union and was formalized by Jeff Sutherland and Ken Schwaber following practices from organizations such as E-Trade, Yahoo!, Microsoft, IBM and Toyota. Scrum emphasizes time-boxed events, cross-functional teams, and empirical process control based on inspection and adaptation, influencing practices at Google, Amazon, Facebook, Spotify (company) and Salesforce.

Overview

Scrum defines a lightweight process for managing complex work, rooted in empirical process control originating from W. Edwards Deming and Shewhart cycle principles used in Toyota Production System, Lean manufacturing, and Total Quality Management. The framework prescribes roles, events, and artifacts intended to foster transparency and rapid feedback loops found in Extreme Programming, Kanban (development) and Crystal (software development). Scrum has been promulgated by organizations like Scrum Alliance, Scrum.org, Scaled Agile, Inc. and discussed at conferences including Agile Alliance and Scaled Agile Framework (SAFe) summits. Prominent adopters include Intel, Adobe Inc., Siemens, Philips and General Electric.

Roles

Scrum specifies a small set of roles distinct from traditional hierarchies: a Product Owner responsible for maximizing product value as practiced in Procter & Gamble and Unilever product teams; a Development Team that is cross-functional and self-organizing as seen at Cisco Systems and NVIDIA; and a Scrum Master who facilitates the process and removes impediments, a role evolved in consultancies like ThoughtWorks and Accenture. These roles interact with stakeholders from organizations such as Oracle Corporation, SAP SE, HP Inc. and Capgemini. Training and certification for these roles are offered by Scrum Alliance, Scrum.org, Project Management Institute and Scaled Agile, Inc..

Events

Scrum prescribes regular, time-boxed events to enable inspection and adaptation: Sprint planning, Daily Scrum, Sprint Review and Sprint Retrospective, practices mirrored in ceremonies at Amazon.com, eBay, Netflix and Airbnb. Sprints typically last from one to four weeks—an approach echoed in iterative models promoted by Rational Unified Process and Spiral model. The Daily Scrum often references techniques from Stand-up meeting traditions used in Toyota and Honda production floors. Reviews involve stakeholders such as Venture capital investors, Product Hunt communities, and corporate boards at firms like Intel Capital and Sequoia Capital.

Artifacts

Scrum defines artifacts intended to provide transparency: the Product Backlog, Sprint Backlog, and Increment. Backlog refinement is a collaborative activity influenced by backlog practices in GitHub, Atlassian product management, and Jira (software), and aligns with prioritization techniques like MoSCoW method and Kano model. Metrics such as velocity, burn-down charts and cumulative flow diagrams are used alongside tools from Tableau Software, Power BI and Grafana for visualization. Artifacts are commonly stored and managed in platforms like Confluence (software), Bitbucket, GitLab and Azure DevOps.

Implementation and Adoption

Organizations implement Scrum at team, program and portfolio levels through scaling approaches and transformations led by consultancies such as McKinsey & Company, Boston Consulting Group, Deloitte and PwC. Scaling frameworks include Scaled Agile Framework (SAFe), Large-Scale Scrum (LeSS), Nexus (Scrum), and Disciplined Agile Delivery; enterprises like Microsoft Azure, IBM Watson, Siemens Healthineers, Boeing and Lockheed Martin report scaled adoptions. Adoption is supported by communities and training events run by Agile Alliance, Scrum Gathering, Lean Startup Conference and corporate programs at Facebook F8, Google I/O and Microsoft Build.

Criticism and Limitations

Scrum faces critique from academia and industry for issues including role ambiguity, misuse in command-and-control cultures, and difficulties scaling in regulated sectors such as Food and Drug Administration-governed MedTech and Federal Aviation Administration-certified aerospace projects. Critics from Harvard Business Review, IEEE and MIT Sloan Management Review note risks of cargo-cult adoption seen in Enron-era management fads and caution against applying Scrum where waterfall governance imposed by Sarbanes–Oxley Act or International Organization for Standardization standards is mandatory. Empirical studies at Carnegie Mellon University, Massachusetts Institute of Technology and Stanford University highlight mixed productivity outcomes and emphasize the need for organizational change management practiced by firms like Change Management Institute and Prosci.

Variants and Related Frameworks

Several variants and complementary frameworks intersect with Scrum, including Kanban (development), Extreme Programming, Crystal (software development), Feature-Driven Development, Behavior-Driven Development, Test-Driven Development, Scaled Agile Framework (SAFe), Large-Scale Scrum (LeSS), Nexus (Scrum), Disciplined Agile Delivery and Spotify (company)-inspired squads and chapters. Hybrid approaches combine Scrum with DevOps, Continuous integration and Continuous delivery practices championed by Jenkins (software), Travis CI, CircleCI and GitHub Actions. Academic programs at University of Cambridge, University of California, Berkeley, Carnegie Mellon University and Imperial College London teach these mixes alongside industry adoption case studies from Intel Labs, Google X and NASA missions.

Category:Agile methodologies