DOCSLIB.ORG

The Secret History of Agile Innovation by Darrell K

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Secret History of Agile Innovation by Darrell K INNOVATION The Secret History of Agile Innovation by Darrell K. Rigby, Jeff Sutherland, and Hirotaka Takeuchi APRIL 20, 2016 You hear a lot about “agile innovation” these days. Teams using agile methods get things done faster than teams using traditional processes. They keep customers happier. They enjoy their work more. Agile has indisputably transformed software development, and many experts believe it is now poised to expand far beyond IT. Ironically, that’s where it began — outside of IT. Some trace agile methodologies all the way back to Francis Bacon’s articulation of the scientific method in 1620. A more reasonable starting point might be the 1930s, when the physicist and statistician Walter Shewhart of Bell Labs began applying Plan-Do-Study-Act (PDSA) cycles to the improvement of products and processes. Shewhart taught this iterative and incremental- development methodology to his mentee, W. Edwards Deming, who used it extensively in Japan in the years following World War II. Toyota hired Deming to train hundreds of the company’s managers, eventually capitalizing on his expertise to develop the famous Toyota Production System — the primary source of today’s “lean” thinking. Iterative and incremental development methods were also a major contributor to the successful creation of the X-15 hypersonic jet in the 1950s. In 1986, one of us (Takeuchi) and coauthor Ikujiro Nonaka published an article in Harvard Business Review called “The New New Product Development Game.” Studying manufacturers that were releasing successful innovations far faster than competitors, the authors identified a team-oriented approach that changed the design and development process for products such as copiers at Fuji- Xerox, automobile engines at Honda, and cameras at Canon. Rather than following conventional “relay race” methods of product development — in which one group of functional specialists hands off its completed phase to the next functional stage — these companies were using what Takeuchi and Nonaka called a “rugby” approach, “where a team tries to go the whole distance as a unit, passing the ball back and forth.” In 1993, another of us (Sutherland) faced what seemed like an impossible task: Easel Corporation, a software company, needed to develop a new product to replace its legacy offerings in less than six months. Sutherland already had a strong background in methodologies such as rapid application development, object-oriented design, PDSA cycles, and skunkworks. He hoped to create a skunkworks-like culture in the middle of corporate headquarters, blending the benefits of both organizational separation and integration. So he began by learning everything he could about maximizing organizational productivity. Reading hundreds of papers and interviewing leading product-management experts, he found himself intrigued by several provocative ideas. One came from a Bell Labs article on the Borland Quattro Pro team, suggesting that short daily team meetings increased group productivity dramatically. But the capstone concept for Sutherland was the discovery of Takeuchi’s and Nonaka’s rugby approach, even though it focused on manufacturing rather than software. Borrowing many of the HBR article’s key ideas and filling in specific operational practices, Sutherland created a new way of developing software; honoring the rugby imagery, he dubbed his approach “scrum.” Scrum methods enabled him to finish his seemingly impossible project on time, under budget, and with fewer bugs than any previous release. He then collaborated with longtime colleague Ken Schwaber to codify the approach, and in 1995 the pair presented scrum to the public for the first time. Of course, Sutherland and Schwaber weren’t alone in their search for innovative methods. The Information Age was exploding. Disruptive technologies were terrorizing slow-footed competitors. Start-ups and incumbents alike sought better ways to adapt to the unfamiliar and turbulent environment. Software was becoming an integral part of nearly every business function, and many creative software developers were working hard on better methods of programming to increase adaptability. In 2001, 17 developers who called themselves “organizational anarchists” met in Snowbird, Utah, to share their ideas. Sutherland and other proponents of scrum were among them. But the group included advocates of several competitive approaches, including extreme programming (XP); crystal; adaptive software development (ASD); feature-driven development (FDD); and the dynamic-systems-development method (DSDM). All these approaches were often known as “lightweight” frameworks because they used fewer, simpler rules to allow faster adaptation to rapidly changing environments. Not many of the attendees found the “lightweight” terminology flattering. Although they disagreed on much, the group eventually settled on a new name for the movement: agile. The word was suggested by one attendee who had been reading the book Agile Competitors and Virtual Organizations: Strategies for Enriching the Customer. The book gave 100 examples of companies — including ABB, Federal Express, Boeing, Bose, and Harley-Davidson — that were creating new ways of adapting to more turbulent markets. Name in hand, attendees then forged consensus on a call to arms dubbed the “Manifesto for Agile Software Development,” which spelled out four key values that everyone agreed on. Later in the meeting, and continuing over the next few months, they developed 12 operating principles, called “Principles Behind the Agile Manifesto.” From 2001 on, all development frameworks that aligned with these values and principles would be known as agile techniques. Once the Snowbird meeting had canonized a creed for agile innovation, the agile movement spread rapidly. The signatories posted their document online and invited others to add their names as supporters. Most members of the original group, joined by a number of new adherents, reconvened later in the year to discuss ways to disseminate agile principles. All agreed to write and speak on the topic. Several attendees wanted to form a more permanent working group; so they established a nonprofit organization called the Agile Alliance to support the movement. Today, the Agile Alliance has nearly 30,000 members and subscribers. Meanwhile, agile methodologies continued to evolve. In the late 1980s and early 1990s, researchers from MIT had begun to study Japanese manufacturing systems, especially the Toyota production system. They coined the term “lean” to describe the system’s methods of improving productivity by eliminating waste (“muda”) through reductions in uneven work flows (“mura”) and destructive overburdening (“muri”). Although lean methodologies were not presented as agile frameworks in Snowbird, formal lean and kanban software-development systems emerged during the 2000s. At first, some agile purists refused to recognize these approaches as agile methodologies. But lean advocates intensified their focus on customer collaboration, and eventually more agile practitioners came to accept lean, kanban, and their hybrids (such as scrumban and lean scrum) as legitimate applications of agile values and principles. Success has many fathers, and agile innovation has a colorful heritage. While agile’s complex family tree sometimes provokes passionate debates among agile practitioners, two things are clear: first, agile’s roots extend far beyond information technology and, second, agile’s branches will continue to spread to improve innovation processes in nearly every function of every industry. 0:00 / 4:20 Darrell K. Rigby is a partner in the Boston office of Bain & Company. He heads the firm’s global innovation and retail practices. He is the author of Winning in Turbulence. Jeff Sutherland is a cocreator of the scrum form of agile innovation and the CEO of Scrum Inc., a consulting and training firm. Hirotaka Takeuchi is a professor in the strategy unit of Harvard Business School. This article is about INNOVATION FOLLOW THIS TOPIC Related Topics: PROJECT MANAGEMENT | OPERATIONS MANAGEMENT | PRODUCT DEVELOPMENT Comments Leave a Comment P O S T 7 COMMENTS John Mereness a month ago I recall the day my best friend (an IT Architect) was telling my dad all about Agile as new (2007) - dad said "call it what you will, though we were doing that in Skunkworks (Lockheed Martin) in 1961 and they were doing it many years before that". Later that day, dad congratulated me on being their Evangelist for such and pulled a copy off the shelf of Kelly: More Than My Share of It All – December 17, 1989 by Clarence L. "Kelly" Johnson (Author), Maggie Smith (Contributor) and said - read this and you will have a better understanding why you are the way you are. REPLY 0 0 JOIN THE CONVERSATION POSTING GUIDELINES We hope the conversations that take place on HBR.org will be energetic, constructive, and thought-provoking. To comment, readers must sign in or register. And to ensure the quality of the discussion, our moderating team will review all comments and may edit them for clarity, length, and relevance. Comments that are overly promotional, mean-spirited, or off-topic may be deleted per the moderators' judgment. All postings become the property of Harvard Business Publishing..
Load more

Recommended publications
  • Humanizing Management and Innovation
    Kindai Management Review Vol. 8, 2020 (ISSN: 2186-6961) Humanizing Management and Innovation Hirotaka Takeuchi Harvard Business School, USA Abstract This article is an excerpt from The Wise Company book that Ikujiro Nonaka and I published in October 2019 from Oxford University Press. It is a sequel to The Knowledge-Creating Company book we published 25 years ago. As our thinking evolved from information to knowledge to wisdom, we have increasingly pushed for a more humane form of management that uses unique human qualities to innovate for the good of society. They include imagination, empathy, intuition, ideals, morals, sensitivity, and more. The article starts out by addressing our rationale on why we are putting these human quali- ties at the center of management when the world is becoming more complex and digital. The article then discusses the future of innovation, which we divided into three stages: Zero to One; One to Nine; and Nine to Ten. In every stage, there will be a fusion of the analog and the digi- tal, where humans and machines will work together and co-evolve. We conclude, however, that humans will lead the co-evolution in the first and third stages, while machines will lead in the second stage. Keywords: knowledge creation, knowledge practice, practical wisdom or phronesis, ba, continuous innovation, fusion of analog and digital, management as a way of life In October 2019, Ikujiro Nonaka and I published emphasized the central role it plays in management The Wise Company,1) a sequel to The Knowledge- and organizational life. Creating Company.2) The publication of our first On the practical front, we wanted to make book gave birth to the field of knowledge manage- knowledge creation a way of life for everyone, thus ment and sparked a movement not just as an aca- humanizing it.
    [Show full text]
  • Scrum Master • the Team Role: Product Owner
    System Analysis and Design Lecture 7 Agenda 1. Previous lecture recap 2. Scrum Methodology 3. Kanban 4. Coursework overview and questions 5. Recommended reading Recap 1. Main ideas from Sprint methodology. 2. Main ideas from Rapid Application Development (RAD). Scrum Iterative & Incremental Models Major Software Development Models There a many Software Development Models with their strengths and weaknesses. But, they can be categorized into 3 major categories: 1. Waterfall – Structured, top/down approach. Examples: Waterfall, Structured System Analysis and Development Methodology (SSADM). 2. Iterative & Incremental – Iteratively go through important software development “steps” (analysis, design, build, etc.) and incrementally build the system. Examples: Spiral, RAD, Agile, etc. 3. Prototyping – Build prototypes, get feedback, refine. Once get the final version – build the software and deploy. Examples: RAD, Prototyping. Let’s start with a history… Scrum history… In their book, “New Product Development Game”, Hirotaka Takeuchi and Ikujiro Nonaka explained the ideas of what we now call Scrum as: "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal“. In 1995 Jeff Sutherland and Ken Schwaber presented the main ideas at Object-Oriented Programming, Systems, Languages & Applications. Roles There are 3 roles in Scrum: • Product owner • Scrum master • The team Role: Product owner The team member who knows the business and customer needs, as well as can make decisions on behalf of the client. S/he is responsible for communication between the developer team and the business. The main goal of Product Owner is successfully build the final product that meets business needs. The Product Owner must be “friends” with both: the business and the developer team.
    [Show full text]
  • The Roots of Scrum
    TheThe RootsRoots ofof Scrum:Scrum: HowHow thethe JapaneseJapanese experienceexperience changedchanged globalglobal softwaresoftware developmentdevelopment WithWith helphelp fromfrom Microsoft,Microsoft, YYahoo,ahoo, Adobe,Adobe, GE,GE, Oracle,Oracle, Siemens,Siemens, BellSouth,BellSouth, Unicom,Unicom, Palm,Palm, StSt.. JudeJude Medical,Medical, DigiChart,DigiChart, Healthwise,Healthwise, Sony/Ericson,Sony/Ericson, Accenture,Accenture, EOS,EOS, Systematic,Systematic, StarsoftStarsoft Labs,Labs, SirsiDynix,SirsiDynix, Softhouse,Softhouse, PhilipPhilips,s, BarclaysBarclays GlobalGlobal Investors,Investors, ConstantConstant Contact,Contact, Wellogic,Wellogic, MedcoMedco Jeff Sutherland, Ph.D. Co-Creator of Scrum http://jeffsutherland.com/scrum © Jeff Sutherland 1993-2007 Roots of Scrum Making the world a better place – Japanese manufacturing - Edward Deming – Team process – Silicon Valley entrepreneurs – Micro enterprise development – Accion and Grameen Bank Process and productivity research – Complex adaptive systems – IBM Surgical Team (Mythical Man Month) – iRobot – subsumption architecture © Jeff Sutherland 1993-2007 Scrum – value driven not plan driven Empower lean teams to deliver more software earlier with higher quality. Demonstrate working features to the customer early and often so the customer can inspect progress and prioritize change. Deliver exactly what the client wants by directly involving the customer in the development process. Provide maximum business value to the customer by responding to changing priorities in
    [Show full text]
  • The Roots of Scrum
    TheThe RootsRoots ofof Scrum:Scrum: HowHow JapaneseJapanese ManufacturingManufacturing ChangedChanged GlobalGlobal SoftwareSoftware DevelopmentDevelopment PracticesPractices JAOO,JAOO, Aarhus,Aarhus, Denmark,Denmark, 2828 SepSep 20052005 Jeff Sutherland, Ph.D. Certified ScrumMaster Training and Creator of Scrum Process Chief Technology Officer, PatientKeeper, Inc. Co-Chair, HL7 Orders and Observations Technical Committee Co-Investigator, Operating Room of the Future, UMMS Microsoft Business Framework Advisory Council © Jeff Sutherland 1993-2005 Jeff Sutherland http://jeffsutherland.com/scrum [email protected] +1 617 947 7400 Agile Systems Architect – CTO/VP Engineering for 9 software companies – Prototyped Scrum in 4 companies – Conceived and executed first Scrum at Easel Corp. in 1993 – Rolled out Scrum in 5 companies 1993-2005 – Helped Ken Schwaber roll out Scrum to industry Signatory of Agile Manifesto and founder of Agile Alliance Available 1/3 time for Scrum training, mentoring, peer review, and consulting © Jeff Sutherland 1993-2005 Roots of Scrum Team process – Silicon Valley entrepreneurs Takeuchi and Nonaka – Japanese manufacturing Making the world a better place – inner vision Object technology and Easel Smalltalk product – OOAD design tool experts, vendors, customers Evolutionary biology and complex adaptive systems Process and productivity research – Software Productivity Research – Surgical Team (Mythical Man Month, IBM) – Wicked Problems, Righteous Solutions – Borland Quatto Pro project iRobot – subsumption architecture © Jeff Sutherland 1993-2005 Toyota Motor Manufacturing North America Mission 1. As an American company, contribute to the economic growth of the community and the United States. 2. As an independent company, contribute to the stability and well-being of team members. 3. As a Toyota group company, contribute to the overall growth of Toyota by adding value to our customers.
    [Show full text]
  • Redalyc.Knowledge-Based View of Strategy
    Universia Business Review ISSN: 1698-5117 [email protected] Portal Universia S.A. España Takeuchi, Hirotaka Knowledge-Based View of Strategy Universia Business Review, núm. 40, 2013, pp. 68-79 Portal Universia S.A. Madrid, España Available in: http://www.redalyc.org/articulo.oa?id=43328679004 How to cite Complete issue Scientific Information System More information about this article Network of Scientific Journals from Latin America, the Caribbean, Spain and Portugal Journal's homepage in redalyc.org Non-profit academic project, developed under the open access initiative Knowledge-Based View of Strategy La Visión de la Estrategia basada en el Conocimiento 1. INTRODUCTION 68 Knowledge creation fuels innovation. This was the central message of The Knowledge-Creating Company book Ikujiro Nonaka and I published in 1995, when both of us were at Hitotsubashi University. This book presented a theory on how new knowledge is created through an interactive process known as SECI (Socialization, Externalization, Combination, Internalization: see Exhibit 1). We Hirotaka Takeuchi1 argued that this knowledge-creating process, which came to be Professor of Management Practice known as the SECI model, holds the key to understanding what Harvard Business School, brings about continuous innovation in firms. Harvard University, USA Jiro Nonaka and I are now writing a book that extends our thinking into [email protected] the field of strategy. We hope to publish this book by 2015, which will mark the twentieth anniversary of the publication of The Knowledge- Creating Company book. Jiro Nonaka is still at Hitotsubashi University, but I moved back to the Harvard Business School in 2010 and started teaching a course called Knowledge-Based Strategy within the Strategy Unit of the School.
    [Show full text]
  • Scrum & Agile Development
    Capasso Cheetham DAILY Kurtz PLANET SCRUM & AGILE DEVELOPMENT SCRUM “A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.” A SCRUM OVERVIEW ¡ History: Developed in the late 80s & early 90s ¡ Features: Lightweight Simple to Understand, Difficult to Master The Sprint Product Backlog Sprint Backlog Scrum Roles ¡ Makes clear the relative efficacy of your product management and development practices Scrum follows an empirical approach, accepting that a problem cannot be fully understood or defined and instead focusing on maximizing the team’s ability to deliver quickly and respond to changing requirements. HISTORY ¡ 1986: Hirotaka Takeuchi & Ikujiro Nonaka § Describe a new approach to commercial product development § “Holistic” or “Rugby” approach § One cross-functional team “tries to go the distance as a unit, passing the ball back and forth.” [1] ¡ Early 1990’s: Ken Schwaber & Jeff Sutherland § Advanced Development Methods & Easel Corporation § First to refer to method using single word ‘Scrum’ ¡ 1995: Schwaber & Sutherland publish Scrum Methodology ¡ 2001: Schwaber & Mike Beedle publish Agile Software Development with Scrum 2012: Yahoo!, a $50 billion company, has one the largest agile implementations in the world, encompassing over 150 teams containing over 1,500 employees. SIMPLIFIED PROCESS *Permission is granted to copy, distribute and/or modify image under the GNU Free Documentation License v1.2. SPRINT ¡ Basic unit of development ¡
    [Show full text]
  • The Scrum Papers: Nut, Bolts, and Origins of an Agile Framework
    THE SCRUM PAPERS: NUT, BOLTS, AND ORIGINS OF AN AGILE FRAMEWORK JEFF SUTHERLAND CO-CREATOR OF SCRUM 30 MAR 2021, LINCOLN MA Copyright Jeff Sutherland 1993-2021 1 Dedication ..................................................................................................................................................................................... 5 Introduction ................................................................................................................................................................................. 8 Forward: Ikujiro Nonaka and The Scrum Way .......................................................................................................... 11 Chapter 1: Introduction to Scrum ....................................................................................................................... 13 Scrum Primer Version 1.2 ................................................................................................................................................... 14 Rolling out Agile at a large Enterprise ........................................................................................................................... 33 Capturing Extreme Business Value: 1000% Annual Return on Investment in Scrum Trainers .......... 43 Chapter 2: The First Scrum ................................................................................................................................. 46 Agile Development: Lessons Learned from the First Scrum ...............................................................................
    [Show full text]
  • How to Implement Scrum in the Context of Marketing
    HOW TO IMPLEMENT SCRUM IN THE CONTEXT OF MARKETING Created by Femi Olajiga - Agile Marketing Coach and Team Effectiveness Trainer “INSPIRE THE WORLD, CREATE THE FUTURE.” TABLE OF CONTENTS SCRUM IN THE CONTEXT OF THE WORK BY PROFESSOR PART 1 HIROTAKA TAKEUCHI AND PROFESSOR IKUJIRO NONAKA PART 2 APPLYING SCRUM IN THE CONTEXT OF MARKETING CONCLUSION PART 3 PART 1 SCRUM IN THE CONTEXT OF THE WORK BY PROFESSOR HIROTAKA TAKEUCHI AND PROFESSOR IKUJIRO NONAKA In 1986, Professor Hirotaka Takeuchi of Harvard Business School and Professor Ikujiro Nonaka of Hitotsubashi University published the article titled “The New New Product Development Game”. The article explained leadership and team practices in manufacturing companies like Honda, 3M and Toyota. The core of their discussion revolved around the importance of speed and flexibility for the survival of the business, whilst identifying the following processes as key determinants of high-performing teams: Built-In-Instability: Team plans are based on the vision and strategic objectives defined by senior management. Leaders empower team members by offering some level of freedom and autonomy, which positively impacts team creativity. The article gave an example where senior management requested the team to deliver a project within a specified timeline, with a defined expectation and a target of reducing cost by 50%, whilst also giving the team the freedom required to execute the tasks required. The key point was that, with a good balance of pressure and freedom, team creativity will increase. Self-Organizing Teams: According to the article, a team must fulfill three important conditions before it can achieve high performance: Autonomy: Senior leaders reduce their micro-management of team members by giving teams more freedom to decide how they want to do things.
    [Show full text]
  • Scrum in This Paper
    THE SCRUM PAPERS: NUT, BOLTS, AND ORIGINS OF AN AGILE FRAMEWORK JEFF SUTHERLAND CO-CREATOR OF SCRUM 30 MAR 2021, LINCOLN MA Copyright Jeff Sutherland 1993-2021 1 Dedication .......................................................................................................................................................................................... 5 Introduction ...................................................................................................................................................................................... 8 Forward: Ikujiro Nonaka and The Scrum Way ............................................................................................................. 11 Chapter 1: Introduction to Scrum .......................................................................................................................... 13 Scrum Primer Version 1.2 ....................................................................................................................................................... 14 Rolling out Agile at a large Enterprise .............................................................................................................................. 33 Capturing Extreme Business Value: 1000% Annual Return on Investment in Scrum Trainers ........... 43 Chapter 2: The First Scrum ..................................................................................................................................... 46 Agile Development: Lessons Learned from the First Scrum .................................................................................
    [Show full text]
  • 1 May 29, 2019 Appointment of International Christian University
    May 29, 2019 Press Release Total 3 pages Appointment of International Christian University Board of Trustees Chair Dr. Hirotaka Takeuchi International Christian University (ICU: Mitaka, Tokyo) Trustee Dr. Hirotaka Takeuchi has been appointed Chair of the ICU Board of Trustees effective June 1, 2019, as the outgoing Chair Mr. Kakutaro Kitashiro completes his term. Dr. Takeuchi will be the first ICU alumnus to chair the ICU Board of Trustees. He will serve a two-year term until May 31, 2021. Profile: Dr. Takeuchi received his B.A. from International Christian University in Tokyo and M.B.A. and Ph.D. from the University of California, Berkeley. He was an Assistant Professor at the Harvard Business School from 1976 to 1983, where he taught courses in the MBA program. He joined Hitotsubashi University in Tokyo as an Associate Professor in 1983 and became Professor in 1987. In 1998, he became the Founding Dean of the first state-run business school in Japan (Hitotsubashi University Graduate School of International Corporate Strategy). After retiring from Hitotsubashi in 2010, he joined Harvard Business School as a Professor of Management Practice. Publications: Corporate Self-Innovation: Managing Chaos and Creation (H. Takeuchi et al., Chuo Koron- sha, 1986, in Japanese) The Best Practice Revolution (Diamond-sha, 1994, in Japanese) Managing Heterogeneity: The Path to Global Management (H. Takeuchi and Yoko Ishikura, Diamond-sha, 1994, in Japanese) The Knowledge-Creating Company (Ikujiro Nonaka and H. Takeuchi, Oxford University Press, 1995) Can Japan Compete? (M. Porter, H. Takeuchi, and M. Sakakibara, 2000, London: McMillan in English, and Diamond-sha in Japanese) Hitotsubashi on Knowledge Management (I.
    [Show full text]