Why the most popular agile framework is named after a rugby formation
In short: Scrum is an iterative management framework that replaces rigid, sequential planning with short, time-boxed sprints. By organizing teams into self-managing units that prioritize continuous feedback, it aims to navigate requirement volatility. Yet, critics argue that when misapplied, it can devolve into a rigid, soul-crushing industrial process.
The term scrum was borrowed from a 1986 Harvard Business Review paper by Hirotaka Takeuchi and Ikujiro Nonaka. They likened the ideal product development process to a rugby match, where a cross-functional team moves down the field as a single, cohesive unit. This metaphor emphasizes speed and flexibility over the traditional, phase-based approach. In the early 1990s, practitioners like Ken Schwaber and Jeff Sutherland refined these concepts into the formal framework used today, eventually codifying their findings in the 2001 Manifesto for Agile Software Development.
At its core, scrum relies on sprints—fixed periods, typically two weeks long, designed to produce a tangible, 'done' increment of work. The process is governed by specific roles: the product owner, who manages business value and stakeholder expectations; the developers, who self-organize to complete tasks; and the scrum master, who coaches the team and removes obstacles. Unlike traditional project managers, scrum masters do not hold people-management responsibilities, a distinction intended to maximize team autonomy.
Despite its popularity, scrum is not without controversy. Critics, including Agile Manifesto signatory Ron Jeffries, have warned against 'Dark Scrum'—a state where teams adopt the rituals without embracing the underlying values of self-organization. Others, like Martin Fowler, have criticized the 'Agile Industrial Complex' for imposing rigid methods that contradict the very principles of individual interaction and flexibility that agile was meant to foster. Furthermore, some studies suggest that scrum can be inefficient for highly specialized teams or those working in distributed environments, where the mandatory daily meetings and rigid structures may hinder rather than help productivity.
To address these limitations, practitioners often adapt the framework. Techniques like 'Scrum of Scrums' allow multiple teams to coordinate on large-scale projects, while 'Scrumban' integrates kanban-style visualization to better manage workflow. Ultimately, scrum is intended to be a living practice, evolving through empirical observation rather than static adherence to rules. As the Scrum Guide—updated six times since 2009—suggests, the framework is meant to be tailored to the specific needs of the organization.
Opens the Intellect+ feed with this card first. Swipe up for the next one.
Sources
- Summary by Intellect · source: Scrum (project management)
To cite this card, link to https://intellectplus.co.uk/app/technology-scrum-project-management.
How we source, check and correct cards: Editorial standards.
General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.
Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?
Related
More in Computing and information technology · More in Technology · Latest · A–Z · All topics