Scrum (software development)

Scrum (software development)
Stefan Morcov · CC BY-SA 4.0 · source
Name	Scrum
Developer	Jeff Sutherland; Ken Schwaber
Initial release	1995
Platform	Agile

Scrum (software development) Scrum is an agile framework for managing complex product development, originating in the mid-1990s and applied widely in software engineering, product management, and organizational transformation. It emphasizes iterative delivery, cross-functional teams, empirical process control, and continuous improvement through short, fixed-length iterations and regular inspection and adaptation.

Overview

Scrum combines ideas from iterative development, empirical process control, and team-based learning drawn from influences such as Toyota Production System, Lean Manufacturing, Systems Thinking, Complexity theory, W. Edwards Deming, Peter Drucker and practices popularized by figures like Jeff Sutherland and Ken Schwaber. The framework prescribes timeboxed iterations called sprints, regular events for coordination, and a small set of artifacts to maintain transparency. Scrum has been adopted across technology organizations including Microsoft, Google, Amazon (company), IBM, and Spotify (company) and is taught in certified programs by organizations like Scrum Alliance and Scrum.org with links to professional certifications such as Certified Scrum Master and Professional Scrum Product Owner. Its roots intersect with methodologies such as Extreme Programming, Feature-Driven Development, Rational Unified Process, and project management standards like PMBOK Guide.

Roles and Responsibilities

Scrum defines distinct roles that form a cross-functional team structure often compared and contrasted against roles in Waterfall model or PRINCE2. The Product Owner represents stakeholders and defines product backlog priorities; comparable product stewardship appears in organizations like Apple Inc. and Procter & Gamble where product managers interface with marketing and engineering. The Scrum Master serves as a facilitator and coach, analogous to agile coaches in firms like Accenture and Deloitte (company), and draws on servant leadership concepts associated with figures like Robert K. Greenleaf. The Development Team comprises professionals with skills in software engineering, quality assurance, user experience design, and operations similar to teams at Facebook, Netflix, Airbnb, and Salesforce. Larger organizations use scaling patterns such as Nexus, SAFe, and LeSS, with adoption examples at Spotify (company), ING Group, and Roche.

Practices and Ceremonies

Scrum prescribes recurrent ceremonies: sprint planning, daily scrum, sprint review, and sprint retrospective. Sprint planning aligns the team with the Product Owner’s goals, echoing planning practices used by Toyota Motor Corporation and project planning in Boeing. The daily scrum is a short synchronization meeting influenced by stand-up techniques used in manufacturing and military staff routines exemplified by practices in U.S. Navy operations. Sprint review invites stakeholders including customers, sales teams, and executives from organizations like Siemens and General Electric to inspect increment progress. Retrospectives focus on continuous improvement and draw from action-learning traditions connected to Kurt Lewin and Chris Argyris. Scrum teams frequently integrate engineering practices from Extreme Programming—including pair programming, test-driven development, and continuous integration—used by teams at Google and Facebook.

Artifacts

Core artifacts are the Product Backlog, Sprint Backlog, and Increment, designed to provide transparency and a single source of truth similar to canonical records in institutions like National Archives. Product Backlog items are often expressed as user stories in the format popularized by practitioners influenced by Extreme Programming and product managers at Amazon (company) and eBay. Teams use tools and platforms such as Jira (software), Azure DevOps, and GitHub to manage artifacts, while metrics like burndown charts and velocity are used to track progress, reminiscent of performance metrics used in operations research and management at firms like McKinsey & Company and Boston Consulting Group.

Implementation and Adoption

Adoption patterns vary from small startups to large enterprises. Case studies include transformations at ING Group, Spotify (company), and Microsoft which illustrate different scaling strategies and cultural shifts. Successful implementation commonly involves executive sponsorship akin to change programs led by leaders such as Satya Nadella, Reed Hastings, or Alan Mulally. Training, coaching, and community support are provided by organizations such as Scrum Alliance and Scrum.org; certification paths and professional development often reference thought leaders including Jeff Sutherland, Ken Schwaber, and Mike Cohn. Enterprises adopt hybrid approaches combining Scrum with DevOps practices promoted by practitioners like Gene Kim and Jez Humble, and integrate continuous delivery pipelines using tools from GitLab, Jenkins, and Docker (software).

Criticisms and Limitations

Critiques of Scrum include concerns about pseudo-agility, cargo-cult implementations, and mismatch with regulatory environments illustrated by constraints in industries like Pharmaceutical industry and Aerospace. Scholars and practitioners including Alistair Cockburn and critics in academic venues such as Harvard Business Review have documented challenges: scaling beyond a few teams, role ambiguity, and overstated promises of productivity. Empirical studies in venues like ACM and IEEE highlight mixed outcomes when Scrum is imposed without cultural change. Alternatives and complements include Kanban, SAFe, and Lean Startup practices propagated by figures like Eric Ries, which address flow, portfolio coordination, and product-market fit in contexts where Scrum's timeboxed cadence may be limiting.

Category:Agile software development