R&D Management 28 min read

The New New Product Development Game: Origins of Scrum and Its Six Key Characteristics

This article revisits the 1986 Harvard Business Review paper that introduced Scrum, explaining why the framework uses rugby terminology, outlining its six defining features, contrasting linear and overlapping product‑development approaches, and illustrating these concepts with case studies from multinational companies.

DevOps
DevOps
DevOps
The New New Product Development Game: Origins of Scrum and Its Six Key Characteristics

The article begins by referencing the 1986 Harvard Business Review paper "The New New Product Development Game," which is credited as the origin of Scrum and its rugby‑inspired terminology.

It explains that modern product development demands speed and flexibility, rendering traditional sequential methods ineffective. Companies in Japan and the United States have adopted an integrated, “rugby‑style” approach where the product moves as a whole through overlapping phases.

The six characteristics of this approach are: built‑in instability, self‑organizing project teams, overlapping development phases, multilearning, subtle control, and transfer of learning. These elements combine like puzzle pieces to create a fast, adaptable development process that can also act as a catalyst for organizational change.

Traditional linear development is described as a relay race with distinct, hand‑off stages, whereas the rugby method involves continuous interaction among multidisciplinary team members, allowing work on later phases to begin before earlier phases are fully completed.

Case studies of companies such as Fuji‑Xerox, Canon, Honda, NEC, Epson, Brother, 3M, and HP illustrate how the six characteristics manifest in real projects, including the FX‑3500 copier, PC‑10 copier, a Honda city car, NEC's PC‑8000, Canon's AE‑1 camera, and the Auto Boy camera.

Each characteristic is examined in detail: built‑in instability is driven by high‑level goals that give teams freedom; self‑organizing teams exhibit autonomy, self‑transcendence, and cross‑pollination; overlapping phases create a shared rhythm that accelerates development; multilearning occurs at individual, team, and organizational levels; subtle control balances oversight with creative freedom; and transfer of learning spreads successful practices across projects and departments.

The article also discusses limitations of the integrated approach, such as the intense effort required from team members, potential unsuitability for breakthrough innovations or very large projects, and the risk of institutionalizing practices that become outdated as environments change.

Management implications are presented, emphasizing the need for adaptive leadership, a learning‑focused culture, and the willingness to allocate challenging goals while tolerating ambiguity, thereby fostering continuous innovation in rapidly evolving markets.

R&D managementagileproduct developmentScrumOrganizational learning
DevOps
Written by

DevOps

Share premium content and events on trends, applications, and practices in development efficiency, AI and related technologies. The IDCF International DevOps Coach Federation trains end‑to‑end development‑efficiency talent, linking high‑performance organizations and individuals to achieve excellence.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.