Глава 1
Transforming Business Through Agility: A Revolution in How We Work
In a world where technology doubles in power every two years while halving in cost, traditional business structures are crumbling under the weight of exponential change. Enter Scrum-a framework that's changing what's possible in organizations worldwide. From fighter jets to healthcare, from banking to restaurant management, Scrum has become the dominant methodology for teams seeking to deliver twice the work in half the time. The Scrum Fieldbook, authored by J.J. Sutherland (CEO of Scrum Inc. and son of Scrum co-creator Jeff Sutherland), has become required reading in boardrooms globally. Even Denmark now teaches Scrum at every university, recognizing it as essential for economic competitiveness. What began as a software development methodology has evolved into nothing short of a business revolution-one that promises to transform not just how we work, but what we believe is possible.
Глава 2
The Exponential Challenge of Modern Business
We live in an era of unprecedented change, where the pace of technological advancement follows Moore's law-computing power doubles every two years while costs halve. This exponential growth creates change at a pace our linear-thinking brains struggle to comprehend. Consider the lily pond riddle: if lily pads double daily and cover the pond in 30 days, on which day is the pond half covered? Day 29. This means when you notice a problem is half as bad as it could be, you have just one cycle left before complete disaster.
Traditional organizational structures simply cannot handle this complexity. They were designed for a world of predictable, incremental change-not the exponential reality we now face. Companies that fail to adapt quickly find themselves becoming the next Kodak or Blockbuster, wondering how they missed the signs of disruption.
Scrum enables organizations to respond nimbly to unpredictable change by breaking work into short cycles called Sprints, typically lasting 1-4 weeks. Each Sprint delivers a potentially shippable product increment, allowing teams to gather feedback and adjust course rapidly. This approach embraces change rather than fighting it, making adaptation fast, cheap, and productive.
Sweden's Saab demonstrates Scrum's transformative power. While known for cars, Saab primarily builds fighter jets. When developing their Gripen E fighter, they adopted Scrum throughout their organization-first in software, then spreading to design, engineering, and quality. This inspired a revolutionary approach: creating a modular, "Lego-like" aircraft that could be easily updated over its 50-year lifespan. Despite superior capabilities, it costs half as much as competitors to operate. When managers claim their work is "too complex for Scrum," I remind them: "Whatever you're building isn't more complicated than a fighter plane."
Глава 3
The Framework That Makes Change Cheap
Scrum fundamentally reduces the cost of changing your mind. Whether you're flipping houses in Minneapolis or integrating billion-dollar corporate acquisitions, the core problems remain the same: understanding what your product should be, what features it needs, and how to deliver it at reasonable cost and speed.
The framework follows a simple 3-5-3 structure: three roles, five events, and three artifacts. The roles are Product Owner (who prioritizes what will be built), Scrum Master (who helps teams go faster), and Team Member (who does the work). The events include Sprint Planning, the Sprint itself, Daily Scrum, Sprint Review, and Retrospective. The artifacts are the Product Backlog (prioritized list of everything that might be done), Sprint Backlog (what the team commits to completing in the current Sprint), and the Increment (the working product produced each Sprint).
Tom Auld flips houses using Scrum in Minneapolis. He assembles a team of contractors who choose to work with him because of his process. They create a backlog on Post-its organized as "To Do," "Doing," and "Done" columns. The work is divided into six one-week Sprints. Daily, the team decides how to tackle work together. Weekly, Tom conducts Sprint Reviews, pays for completed work, and adjusts plans based on discoveries (like raccoons in walls or wiring issues). This approach reduces expensive rework and embraces inevitable changes.
Mark Anderson's 3M team implemented Scrum for their six-month acquisition integration timeline, working in one-week Sprints with three fifteen-minute Scrums weekly. Despite not implementing Retrospectives as rigorously as they could have, the integration was remarkably successful-on day one, all managers were in place, employees knew where to report, finance systems were ready, and global kickoff proceeded smoothly.
The Standish Group reports that 67% of requirements change during development because people learn as they build. Traditional systems protect false visions of the future through documentation and bureaucracy, delivering a world where nothing gets done. Instead of fighting inevitable change, Scrum embraces it, making adaptation fast, cheap, and enjoyable.
Глава 4
The Decision Paralysis Epidemic
Decision paralysis plagues organizations when they discover unexpected problems during projects. Jim Johnson of the Standish Group discovered through extensive research that "decision latency"-the time between recognizing a decision needs to be made and actually making it-is the root cause of many project failures. The shocking finding: projects where decisions take under an hour have a 58% success rate, while those taking over five hours plummet to just 18% success.
Most decisions are trivial and easy, but hierarchical approval processes create devastating delays. In companies using systems like the Japanese ringi approval process, even pre-budgeted expenses can require dozens of signatures and months of waiting, creating enormous inefficiency.
Meetings are often costly decision-making venues with poor outcomes. A simple one-hour meeting with twenty attendees represents significant expense, and worse, the Standish Group found over 40% of meeting decisions are later reversed. This happens for two reasons: decisions are often driven by the loudest person in the room rather than the most knowledgeable, and people who weren't included feel slighted and work to overturn decisions.
Navy Commander Jon Haase successfully implemented Scrum in Explosive Ordnance Disposal, one of the most demanding Special Forces environments. His team's productivity increased from 4 to 50 points daily-a 1,250% improvement-by implementing timeboxed events with clear objectives and agendas. This demonstrates that Scrum can succeed in even the most high-stakes, unpredictable environments.
Christopher Langton's work on cellular automata revealed that systems operate best at the "edge of chaos"-where rules aren't too rigid or too loose. This phase transition zone describes complex adaptive systems like traffic, where individual actions seek solutions through self-organization. Scrum is designed to operate precisely at this edge, embracing complexity rather than attempting to control it through rigid planning.
The real solution to complex problems emerges only through system interactions, not perfect planning. As Eisenhower noted, "Plans are worthless, but planning is everything" because emergencies never unfold as expected. People's pursuit of perfect plans leads to analysis paralysis-endless studies and debates with no action. Scrum breaks this cycle by providing quick feedback on decisions, allowing teams to pivot and adapt.
Глава 5
The Myth of Multiple Priorities
The word "priority" originated in the fourteenth century to indicate precedence or rank. Linguistically, "priorities" is nonsensical-like saying there were multiple first-place finishers in a race. The term didn't appear in common usage until around 1940, coinciding with the rise of modern management techniques-a meaningless word masquerading as rigorous business language.
Scrum Inc. typically finds that 30% of work in companies actively opposes business goals, while 64% of the remaining work creates features customers rarely or never use. This means 75% of employees are working on the wrong things. The problem stems from an inability to truly prioritize, as evidenced by common phrases like "we have multiple conflicting priorities" or "everything is the number one priority."
Output measures how much a team produces (Velocity), while outcome focuses on creating actual value. When starting with Scrum, teams should first focus on getting work done and out the door quickly, even if imperfect. This provides fast feedback rather than wasting time and money building the wrong thing.
The architecture of a product determines what "done" can mean. At the Stealth Space Company, their first rocket had avionics systems with specialized circuit boards connected by rare materials. When one board failed, all boards needed removal with hundreds of hand-reconnections using expensive materials. The solution was creating a stable interface between avionics and the rest of the rocket using common connectors available off-the-shelf. This "modularized" approach made the Definition of Done clear: components must work and fit the stable interface.
The root cause of prioritization problems is an unwillingness to say no. Organizations easily say yes to every request until they implode. Corporate strategy typically focuses too much on what companies will do rather than what they won't do. At one global materials company struggling with product development, they had over 100 projects in progress but not enough people to staff even 70 of them. By making hard choices and reducing to just 12 focused projects, they doubled productivity in ten weeks and reduced their typical 2.5-year development cycle to just six weeks.
Глава 6
Fear: The Hidden Enemy of Innovation
Fear drives people to act in seemingly irrational ways that prevent them from achieving results. As a former NPR journalist who worked in war zones, I've become intimately familiar with fear-its "curves and special places, its harsh planes, its acrid taste, its shuddering caress, and its dark seduction." This same fear drives workplace dysfunction-the fear of becoming obsolete or losing our jobs makes us resist necessary change.
At a major automaker, I witnessed organizational insanity where status came from distance from actual work. Two hundred people spent five years and $75 million on a dealer incentives tracking project without producing anything valuable. Only twenty-five people were actually doing work; the rest were managers managing managers having meetings about meetings. When we implemented Scrum, we cut 175 people from the project, eliminated unnecessary meetings, and delivered a working product within months. Before our intervention, everyone knew it was insane but feared saying so would threaten their positions.
Large banks and traditional corporations with vast resources are increasingly calling us because "no one wants to work for us." Despite raising salaries and running slick ad campaigns targeting millennials, these companies create workplace cultures that crush creativity and drive young talent away. One hardware manufacturer finally broke through when a leader emotionally admitted "the way we work sucks" and committed to fixing even small symbolic problems like a perpetually broken toilet.
A major U.S. utility was plagued by inefficiency-typically sending five separate crews to resolve a single customer problem. This happened because different functional silos handled scheduling, dispatching, tools, power control, and repairs, with no coordination between them. However, during hurricane season ("storm time"), all barriers between departments dropped. Crews from across the country worked together, executives served meals to workers, and power was restored in days instead of weeks. Yet once the crisis passed, they immediately reverted to their inefficient practices.
MIT professor Otto Scharmer theorizes that fear drives organizational dysfunction through three voices in our inner dialogue: The Voice of Judgment filters new information through existing worldviews, seeking only confirmation of what we already believe. The Voice of Cynicism protects us emotionally from feeling hope only to have it shattered. The Voice of Fear makes us afraid to fail, keeping organizations trapped in cycles of denial. W. Edwards Deming advocated "Drive out fear" because fear produces wrong numbers and destroys motivation.
Глава 7
Structure Determines Culture
Riccardo Mariti transformed his restaurant by eliminating hierarchy, offering profit-sharing, and creating a flat organization without titles or bosses. He discovered that structure determines culture, and culture defines limits. As Darrell Rigby of Bain & Company noted, two companies can have similar org charts but vastly different cultures and operating models.
Two fundamental constraints shape organizational design. Conway's law (1968) states that organizations produce designs mirroring their communication structures-if your organization is rigid and hierarchical, your product will be too. Shalloway's corollary warns that when development groups reorganize, their current application architecture works against them.
When transitioning to Scrum, management must change too. At Riccardo's restaurant, eliminating managerial roles meant Riccardo had to stop solving everyone's problems and instead help staff make better decisions themselves. This shift reduced customer issue response time by 70%. In Agile companies, leadership becomes more critical as the buffer between decisions and consequences disappears-the distance between a bad decision and its impact approaches zero.
The five Scrum values form the lifeblood of the framework, interlocking and building upon each other to create organizations that are energetic and enjoyable places to work:
1. Commitment means more than trying-it requires team members to dedicate themselves to each other, to change, to completing Sprint work, and to producing value.
2. Focus requires maintaining laser concentration despite constant distractions. The road to accomplishing nothing is paved with "just this one thing" that wasn't in the Sprint Backlog.
3. Openness ensures transparency-meetings are open, backlogs visible, and everyone's voice must be heard. Traditional projects often hide problems until they suddenly appear as emergencies.
4. Respect creates an environment where people feel safe admitting errors without fear of punishment. Respect means accepting people with their strengths and weaknesses, focusing on problems rather than blame.
5. Courage is essential for being open, transparent, and embracing change. Many managers fear Agile transformation because their roles will change.
Traditional organizations are burdened with layers of structure that create waste and slow everything down. While some hierarchy prevents chaos, leaders should aim for "minimum viable bureaucracy." At Colombia's Drummond Company gas division, consultant Fabian Schwartz focused on improving communication and collaboration rather than drilling operations themselves. By forming a cross-functional Scrum Team of senior leaders who met daily for fifteen minutes, they reduced well drilling time from an average of nineteen days to just six days without changing any technology or people-only how they worked together.
Глава 8
Patterns for Hyperproductive Teams
Christopher Alexander, an influential architect, sought to articulate why certain spaces simply feel right-what he called the "quality without a name" that makes a place the ideal version of itself. Like Alexander's patterns for architecture, Scrum has its own patterns for creating hyperproductive teams-practices that have been proven to work across multiple companies and domains.
OpenView Venture Partners discovered that teams who finished their sprints early accelerated faster than those who packed their sprints full. Teams that consistently worked until the last minute maintained the same velocity but never achieved the fourfold productivity improvement that Scrum aims for. The pattern became clear: Scrum isn't about velocity-it's about acceleration. Teams that finish early have time to improve and get faster.
The first critical pattern for hyperproductive teams is stability. Teams that stay together develop shared mental models and transactive memory-they learn to anticipate each other's needs and store collective knowledge across team members. Bruce Tuckman's research shows teams progress through forming, storming, norming, and performing stages, a process that takes considerable time. Data from 75,000 teams shows that members dedicated to a single team are nearly twice as productive as those split across multiple teams.
"Yesterday's Weather" recognizes that past performance is the best predictor of future performance. Teams should only commit to the same amount of work they completed in previous Sprints, ideally using a three-Sprint average to quiet the noise in velocity measurements. Though teams often want to improve and may feel tempted to overcommit, finishing early and pulling in more work creates the possibility to accelerate, while not finishing work crushes morale.
"Swarming" addresses the productivity-killing habit of working on too many things simultaneously. The pattern directs teams to focus entirely on completing the most important backlog item before moving to the next. Like a Formula One pit crew working in perfect synchronization to get a car back on track in seconds, Scrum teams should concentrate all their effort on delivering value quickly.
The "Interrupt Buffer" addresses the common problem of teams being constantly interrupted by management, sales, or support requests. Teams should set aside a percentage of their capacity as an "Interrupt Buffer"-perhaps taking on only 15 items instead of their usual 20, reserving the remainder for emergencies. The Product Owner guards this buffer, deciding which interruptions truly warrant immediate attention.
"Good Housekeeping" emphasizes maintaining a clean product and environment daily, fixing problems immediately, and building in quality at every step rather than testing for it at the end. At Red River Army Depot, they revolutionized Humvee repair by completely disassembling damaged vehicles and rebuilding them with better components every sixteen minutes. This approach increased production from three Humvees per week to forty per day-a 6,600% improvement.
Глава 9
Scaling Scrum Across Organizations
Schlumberger, though not widely known to the general public, is ubiquitous in oil and gas drilling worldwide. When CIO Eric Abecassis faced a failing IT modernization project despite significant investment, he turned to Scrum as a radical solution. Through acquisitions, Schlumberger had accumulated 150 different legacy IT systems with no unified view. They attempted to implement an SAP Enterprise Resource Planning system to integrate everything from cash management to supply chain.
Scrum Inc. began working with Schlumberger, and despite initial challenges, by May productivity had jumped 25% while external contractors were reduced by 40%. Abecassis reported a 25% cost reduction for the entire project with expectations to reach 30-40% savings and productivity improvements. Their SAP implementation for North America successfully launched simply by changing their working methods.
The author quotes Peter Drucker on resistance to change, noting that opposition is inevitable even when facing destruction. Abecassis's strategy focused on converting those willing to change, who then saw the impact and became fully committed. As Scrum succeeded, it spread throughout the organization, eventually transforming Abecassis's leadership team into "one Team with one mission."
Scrum@Scale creates networks of teams that distribute decision-making to the edges, making organizations robust and self-healing. The key is establishing stable interfaces between components, similar to how Saab's Gripen E teams organized around modular aircraft components. Organizations should mirror their products with loosely coupled components, minimizing management overhead to create a "minimum viable bureaucracy."
The Scrum Master cycle centers on the Executive Action Team that drives organizational learning. The author describes how Bosch, a 130-year-old company with hundreds of thousands of employees, transformed to meet 21st century challenges by implementing Scrum throughout the organization. After initially trying to implement Scrum using waterfall tools, CEO Volkmar Denner and his board reconstituted themselves as a Scrum team with a Product Owner and Scrum Master. The results were dramatic: Bosch halved development time for Tesla components, produced ten agricultural innovations in four weeks instead of one in six months, and transformed their home and garden unit to include everyone from designers to marketers in fully Agile teams.
When organizations fully embrace what Scrum makes possible-self-organizing to increase speed, quality, and responsiveness-they fundamentally shift their trajectory. Schlumberger's IT team achieved "twice the work in half the time" and even exceeded that benchmark. CIO Eric Abecassis states his mission is "to generalize the concept of a 'Team of Teams' that is supported by the Scrum principles to become a tool to drive business," reflecting his ambitious vision for organizational transformation.
Глава 10
The Future of Work
Like John Snow's epidemiological breakthrough challenging miasma theory in 1840s London, Scrum has developed through observed patterns of success. Snow's meticulous mapping of cholera cases led to the discovery that contaminated water, not "bad air," spread disease. Similarly, Scrum's effectiveness has been proven through careful observation and data collection across thousands of projects. Yet resistance persists as people cling to traditional methods like Gantt charts, project plans, and detailed business requirements, even when substantial evidence shows better alternatives exist. This resistance mirrors the medical establishment's initial rejection of Snow's findings, despite clear evidence.
The author highlights Denmark as a compelling Scrum success story, where Carsten Jakobsen pioneered its implementation at Systematic in 2006 for critical healthcare and defense software development. The results were remarkable: teams doubled their velocity, reduced defects by 41%, and significantly improved both customer and employee satisfaction. The data was so convincing that Systematic's CEO not only continued supporting Scrum but took the unprecedented step of implementing it at the leadership level. This success sparked a national movement - now Scrum is taught at every Danish university, and traditional companies across industries are adopting it not just as an improvement tool but as a survival necessity in the digital age.
The author challenges conventional transactional thinking about resources, presenting a revolutionary perspective that certain resources - particularly social and emotional ones like kindness, creativity, and love - actually increase through use rather than becoming depleted. Drawing on economist Albert Hirschman's work, he explains that moral resources behave differently from physical ones: they atrophy when unused but grow stronger when regularly practiced. This concept is supported by extensive research on social connections and health outcomes. Studies show people with six or more close social connections are half as likely to get sick as those with three or fewer, and recovery rates from serious illnesses improve significantly with strong social support networks.
Scrum creates frameworks that provide essential psychological needs: purpose, meaning, security and self-worth through clearly defined roles and expectations. This structure proves particularly powerful because it works across cultural and linguistic boundaries, tapping into fundamental human needs and motivations. The methodology has been successfully implemented in organizations from Silicon Valley startups to Japanese manufacturers to European government agencies, demonstrating its universal applicability.
The world is changing at an unprecedented pace, which can either paralyze organizations or liberate them to achieve extraordinary results. What seems impossible today can be accomplished with the right framework and mindset. The author emphasizes that the tools and path are now available - we can transform not just how we work, but what we collectively believe is possible. This transformation extends beyond productivity improvements to fundamentally changing how organizations operate, innovate, and adapt to rapid change.
