DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • How Does a Scrum Master Improve the Productivity of the Development Team?
  • Bounded Rationality: Why Time-Boxed Decisions Keep Agile Teams Moving
  • How to Use AI to Enhance Scrum Ceremonies
  • Agile Teams Thrive on Collective Strengths, Not Sameness

Trending

  • A Hands-On ABAP RESTful Programming Model Guide
  • Building a Production-Ready AI Agent in 2026: Beyond the Hello World Demo
  • Top JavaScript/TypeScript Gen AI Frameworks for 2026
  • A System Cannot Protect What It Does Not Understand
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Scrum, What's in a Name?

Scrum, What's in a Name?

Would a software development method by any other name sound as sweet? Read on to learn why this Scrum Master says, 'No.'

By 
Gunther Verheyen user avatar
Gunther Verheyen
·
Jun. 10, 17 · Opinion
Likes (3)
Comment
Save
Tweet
Share
31.8K Views

Join the DZone community and get the full member experience.

Join For Free

Scrum is the most used framework for Agile product delivery. Often, people wonder about the name, its origins, and what it means. Let's have a look at the origins of the term 'Scrum.' And, as a result, understand that it is not an acronym.

The term 'Scrum' was first used by Hirotaka Takeuchi and Ikujiro Nonaka in their ground-breaking 1986 paper, "The New New Product Development Game." They borrowed the name from the game of rugby to stress the importance of working as a team in complex product development. This was about complex product development in general, not only software products. Their research showed that outstanding performance is achieved when teams are small and self-organizing units of people and when such teams are fed with (challenging) objectives, not with executable tasks. Teams can only achieve greatness when given room to devise their own tactics to best head towards shared objectives.

Image title


The well-known Agile development method inherited its name 'Scrum' from this paper as it thrives on the same principles for developing and sustaining complex software products. Those principles are time-boxing of work, creating releasable ("Done") products, and self-organization of teams that - collectively - have all the skills required to create products in a releasable state, where releasable means "ready to ship to the market."

The Japanese authors of the paper consider the concept that they named 'Scrum' as the necessary core of any system that pretends to be Lean. But, they never use the term 'Lean' as such, because it has become synonymous to an outside interpretation and copy of the perceived management practices of the Toyota Production System.

These management practices are not the core of Takeuchi and Nonaka's development system. That core was named 'Scrum' by the authors. Lean management practices should simply be complementary to it. There can't be 'Lean' if the heart of it, Scrum (as named by the authors), is overlooked, which, in general, is the case. The authors, therefore, prefer to stress the need for the heart and soul of the system to be Scrum and take away the sole focus on the surrounding management practices. They never talk of Lean, but always speak about Scrum.

As Scrum is no acronym, there is no reason to write "SCRUM."


If you enjoyed this article and want to learn more about Scrum, check out our compendium of tutorials and articles.

scrum

Published at DZone with permission of Gunther Verheyen. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • How Does a Scrum Master Improve the Productivity of the Development Team?
  • Bounded Rationality: Why Time-Boxed Decisions Keep Agile Teams Moving
  • How to Use AI to Enhance Scrum Ceremonies
  • Agile Teams Thrive on Collective Strengths, Not Sameness

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook