Scrum

Scrum Plot Summary

Introduction

Imagine your team has been working for months on an important project. Deadlines keep slipping, costs are mounting, and motivation is waning. This frustrating scenario plays out in organizations worldwide daily. The traditional ways we organize work—detailed upfront planning, rigid hierarchies, and micromanagement—are failing us in an increasingly complex and fast-paced world. What if there was a radically different approach that could help teams accomplish twice as much work in half the time? An approach that harnesses human creativity, removes wasteful processes, and consistently delivers remarkable results. This revolutionary framework, born in software development but applicable to virtually any field of human endeavor, has transformed how the world's most innovative companies operate. By focusing on iterative progress, team autonomy, and radical transparency, this approach has enabled ordinary teams to achieve extraordinary results—from rebuilding the FBI's case management system to designing high-mileage cars, from delivering life-saving healthcare innovations to transforming education. The principles you'll discover in these pages can help you not only revolutionize how you work, but fundamentally change how you live.

Chapter 1: Embrace the Rhythm: Sprints and Daily Stand-ups

At the heart of Scrum lies a powerful concept of time management that fundamentally changes how teams approach work. Rather than the traditional approach of long projects with distant deadlines, Scrum breaks work into short, focused bursts called "Sprints." These timeboxed iterations—typically one to four weeks long—create a natural rhythm that propels teams forward with energy and clarity. The Sprint concept originated at MIT's Media Lab in the early 1990s, where students had to demonstrate working projects every three weeks. If their demonstrations weren't both functioning and impressive, their projects were terminated. This approach forced students to build remarkable things quickly and get immediate feedback. Jeff Sutherland, Scrum's creator, borrowed this concept when forming the first Scrum team. Instead of presenting management with elaborate planning charts, he committed to showing working software every month—something customers could actually use, not just backend infrastructure or architecture diagrams. This rhythm becomes even more powerful when combined with the Daily Stand-up meeting (or Daily Scrum). Each day, at the same time, for fifteen minutes or less, team members gather to synchronize activities by answering three simple questions: What did I do yesterday to help the team complete the Sprint? What will I do today? What obstacles are getting in our way? When implemented at Borland Software Corporation's Quattro Pro project in the early 1990s, this practice contributed to record-breaking productivity—one million lines of code produced by just eight people in 31 months, setting industry records. The transformative power of this approach was demonstrated when the first Scrum team implemented daily meetings during their third Sprint. They had planned four weeks of work—the same workload as previous months—and finished it all in a single week. A 400-percent improvement. The team members looked at each other in astonishment and said, "Wow." That's when Sutherland knew he was onto something revolutionary. To implement this rhythm in your own work, start by establishing a fixed Sprint length—be consistent to help your team develop a reliable cadence. During each Sprint, ensure everyone understands that the work is locked in; nothing can be added from outside the team. This protection creates focus and prevents the productivity-killing impact of context switching. Then, institute daily stand-up meetings that are crisp, focused, and action-oriented. The key is creating a regular heartbeat for your team—a rhythm that drives momentum and makes progress visible to everyone involved. What makes this approach so powerful is how it transforms our relationship with time itself. After engaging with Sprints and Stand-ups, you stop seeing time as a linear arrow into the future and instead experience it as something fundamentally cyclical—each Sprint offering an opportunity to deliver value, learn, and improve. This rhythm becomes the foundation for remarkable achievement.

Chapter 2: Build Self-Organizing Teams

The true engine of productivity in Scrum is not processes or tools but teams—specifically, self-organizing teams with the right characteristics. Studies comparing individual and team performance reveal something extraordinary: while the gap between the fastest and slowest individuals might be 10:1, the difference between the best and worst teams can be a staggering 2000:1. This suggests that focusing on team performance, rather than individual stars, offers the greatest leverage for improvement. What makes great teams? Professor Takeuchi and Nonaka, whose paper "The New New Product Development Game" inspired Scrum, identified three critical characteristics: they are transcendent (driven by a purpose beyond the ordinary), autonomous (self-managing and empowered), and cross-functional (possessing all the skills needed to complete their mission). These qualities were vividly demonstrated in the transformation of the "Loose Deuce," West Point's L2 cadet company under Sutherland's guidance in 1963. For over a century, L2 had ranked at the bottom of West Point's twenty-four companies in parade formations. As training officer, Sutherland had no direct authority—he wasn't part of the command structure. Instead, he focused on transparency, creating colored charts showing what went wrong and posting them where everyone would see them daily. At first, the criticisms were simple: "Charlie had his sword stuck in the dirt" or "Jim didn't turn in sync." As cadets improved, the problems shifted to the company commander, whose orders weren't clear enough. When confronted, Sutherland simply said, "The ratings are the ratings. Do you want to fix it or do you want to suck forever?" Within weeks, L2 became the number one company at West Point and was later selected to march at General MacArthur's funeral—an extraordinary honor reflecting their transformation from worst to first. The power of self-organization was similarly demonstrated during the Egyptian revolution in 2011. NPR producer J.J. Sutherland used Scrum to coordinate the news team's coverage in Cairo under extremely difficult conditions. With limited communication to Washington headquarters, the team organized itself, meeting daily to address three simple questions: What did you do since the last time we talked? What will you do before we talk again? What's getting in your way? This approach transformed chaos into coordinated coverage that outperformed competitors and won multiple awards. To build self-organizing teams in your organization, start by keeping teams small—seven people plus or minus two is optimal. Research shows that beyond nine people, productivity actually decreases due to communication overhead. Next, ensure teams are truly cross-functional with all the skills needed to deliver value. Finally, foster team autonomy by setting clear goals but allowing teams to decide how to achieve them. Remember that when examining team performance issues, don't blame individuals—look for system problems. The environment and incentives shape behavior more than personal traits. Create the right conditions, and ordinary people will achieve extraordinary results.

Chapter 3: Eliminate Waste in Every Process

At its core, Scrum is a system designed to identify and eliminate waste—the non-value-adding activities that consume resources without producing benefits. This focus on efficiency stems from Toyota's production system and the philosophy of Taiichi Ohno, who famously declared that "waste is a crime against society more than a business loss." By systematically rooting out different forms of waste, teams can dramatically increase their productivity and focus their energy on what truly matters. One of the most pervasive forms of waste in modern work is multitasking. While many people boast about their ability to juggle multiple projects simultaneously, research consistently shows this practice severely damages productivity. A study by Gerald Weinberg revealed that when switching between just two projects, 20% of productive time is lost to context switching. With five simultaneous projects, a staggering 75% of time is wasted! This happens because our brains physically cannot process multiple complex tasks at once. University of Utah researchers found that people who believe they're good at multitasking are actually worse than average, as they're simply more distractible. Half-done work represents another critical form of waste. Like a factory floor filled with partially assembled products, partially completed tasks tie up resources without delivering value. The Japanese manufacturing concept of "Work in Process" applies equally to knowledge work—whether it's software features, presentations, or reports. Doing half of something is essentially doing nothing. In Scrum, teams focus on getting items completely "Done" within a Sprint, where "Done" means fully usable, meeting all quality standards, and potentially deliverable. Perhaps most counterintuitively, working too hard creates more work. Scott Maxwell of OpenView Venture Partners discovered this when he started implementing Scrum. By measuring team productivity against hours worked, he found that peak output occurred at slightly less than forty hours per week. Working longer hours actually reduced productivity by inducing fatigue, increasing errors (which take 24 times longer to fix when not addressed immediately), and impairing decision-making. Israeli researchers demonstrated this by analyzing judicial rulings, finding that judges made more favorable decisions immediately after breaks and increasingly defaulted to the status quo as they became mentally depleted. To eliminate waste in your work, first stop multitasking—focus completely on one important task at a time. Second, drive items to completion rather than having many things partially done. Third, maintain sustainable pace—working longer hours doesn't get more done; it creates more problems. Fourth, make all work visible—use a simple board with "To Do," "Doing," and "Done" columns to track progress and identify bottlenecks. Finally, in your team retrospectives, consistently ask: "What waste did we create this week, and how can we eliminate it next week?" The discipline of eliminating waste creates the conditions for flow—that state where work becomes effortless and energy flows smoothly. In martial arts or meditative practice, when you reach a sense of oneness with motion, it's no longer an effort. The same principle applies to great teams. By removing everything extraneous and focusing only on what creates value, you create the foundation for exceptional performance.

Chapter 4: Prioritize Value Over Features

When faced with complex projects, our natural instinct is to plan everything in detail. We create elaborate charts with carefully precise steps, convinced that thorough planning will guarantee success. However, this approach often leads to wasted effort and missed opportunities. The Medco pharmaceutical company learned this lesson when their president announced an ambitious plan for specialized pharmacies nationwide with a firm deadline. Six months later, management realized they couldn't meet the timeline, projecting delivery at least one year late. That's when they called in Jeff Sutherland. The first step at Medco was breaking down the mountain of requirements documents—a two-foot stack of papers that no one had actually read completely. The team cut out the essential items, placed them on sticky notes, and prioritized them by value. This process revealed that many requirements were duplicative or unnecessary. Through careful prioritization and focusing on delivering incremental value, they transformed what seemed impossible into achievable goals. This approach reflects a fundamental rule in product development: 80 percent of value comes from 20 percent of features. The key is identifying which 20 percent to build first. In traditional development, teams don't know which features truly matter until they deliver everything—meaning 80 percent of their effort is wasted. With Scrum, teams focus on delivering the highest-value items first, then gather feedback to guide subsequent work. To implement this value-focused approach, start with relative sizing rather than absolute time estimates. Humans are terrible at estimating how long tasks will take in hours or days, but remarkably good at comparing sizes. Mike Cohn developed a technique called "Dog Points," where teams compare tasks to dog breeds—is this feature a dachshund (small) or a Great Dane (large)? This approach, often using the Fibonacci sequence (1, 3, 5, 8, 13...), helps teams build consensus about relative effort without getting bogged down in precise time estimates. Once you've sized your backlog items, use "Planning Poker" to eliminate bias in estimation. Each team member privately selects a card representing their estimate, then all cards are revealed simultaneously. If estimates are close, the team averages them and moves on. If they differ significantly, those with high and low estimates explain their reasoning, fostering valuable knowledge sharing before re-estimating. The final key practice is embracing change rather than fighting it. Traditional contracts penalize changes, creating "Change Control Boards" that slow innovation. Scrum offers "Change for Free"—allowing priorities to shift completely between Sprints as long as equivalent work is removed when new items are added. One Scrum developer even offered clients a contract clause allowing them to terminate early for 20% of the remaining value. When one client exercised this option after just three months, both parties won—the client got working software for a third of the original price, seventeen months early, while the developer earned a 60% profit margin instead of 15%. By focusing relentlessly on delivering value rather than simply checking off features, you can transform any project from a potential failure into a remarkable success.

Chapter 5: Measure Happiness to Predict Success

The connection between happiness and productivity might seem obvious, but its importance is often overlooked in business settings. Research conclusively demonstrates that happy teams are more productive, more innovative, and more profitable. What's particularly surprising is the direction of causality—people aren't happy because they're successful; they're successful because they're happy. Happiness actually precedes and predicts business outcomes. This insight led Sutherland to develop the "Happiness Metric," a simple but powerful tool for improving team performance. At the end of each Sprint, team members answer four questions: How do you feel about your role in the company (1-5)? How do you feel about the company as a whole (1-5)? Why do you feel that way? What one thing would make you happier in the next Sprint? The team then takes the top improvement idea and makes it the highest priority for the next Sprint, with clear acceptance criteria to measure success. When Sutherland implemented this approach at his Scrum consultancy, the results were remarkable. By systematically addressing what would make people happier—from improving user stories to streamlining processes—the team's velocity accelerated from 40 points per Sprint to 120 points in just a few weeks, tripling productivity. What makes the Happiness Metric particularly valuable is its predictive power. Unlike financial metrics that look backward, happiness projects forward. A drop in happiness typically precedes a drop in productivity by several weeks, providing an early warning system for potential problems. Zappos exemplifies an organization that has built happiness into its core culture. The online retailer, which grew from $1.6 million in sales in 2000 to over $1 billion in 2008, focuses intensely on creating connections between employees. New hires go through a four-week "boot camp" that builds lasting relationships across departments. The company offers free classes taught by employees and encourages internal movement between roles, allowing people to explore their interests and develop new skills. According to Senior HR Manager Christa Foley, this positive culture doesn't promote complacency but rather makes people work harder: "I love coming to work. Rather than becoming complacent, our positive and uplifting culture makes you work harder." To implement the Happiness Metric in your organization, start by creating psychological safety for honest feedback. During retrospectives, encourage team members to share what would make them happier without fear of judgment. Track happiness scores alongside productivity metrics, watching for early warning signs when happiness dips. Make at least one happiness-improving change each Sprint, and measure its impact. Finally, focus on the three drivers of workplace happiness identified by research: autonomy (control over one's work), mastery (getting better at valuable skills), and purpose (serving something larger than oneself). Remember that true happiness isn't complacency—it's passionate engagement. The goal isn't a team that's merely satisfied, but one that's thriving—showing 16% better performance, 32% more commitment, and 46% more satisfaction than their peers. By making happiness a strategic priority rather than an afterthought, you create the foundation for sustainable excellence.

Chapter 6: Visualize Progress with Transparency

One of the most powerful principles in Scrum is radical transparency—making everything visible to everyone. This approach eliminates the information hoarding, political gamesmanship, and coordination problems that plague traditional organizations. By creating visibility into work status, impediments, and progress, teams can self-organize to solve problems faster and deliver more value. The most tangible manifestation of this transparency is the Scrum board—a simple visual tool that shows all work items organized into three columns: To Do, Doing, and Done. This humble arrangement of sticky notes on a whiteboard transforms how teams coordinate. Anyone can walk into the room, glance at the board, and immediately understand the Sprint's status, which items are progressing well, and where people might be stuck. This visibility enables team members to self-organize around challenges—if someone sees a colleague struggling with a task that's been in "Doing" too long, they can offer help without waiting for management intervention. When Jeff Sutherland implemented this transparency at PatientKeeper, a healthcare software company, the developers were initially skeptical. They worried that increased visibility would only lead to more criticism and punishment. "Trust me," Sutherland told them, "This won't be used to hurt you or punish you. It will only be used to make things better." By making all work visible, teams could coordinate assignments across groups and support each other when roadblocks appeared. Someone on one team might have already solved a problem another developer was facing. This transparency helped PatientKeeper achieve remarkable results—releasing enterprise software 45 times a year, a pace unheard of in the healthcare industry. The benefits extend beyond project work to organizational culture. At the Grameen Foundation, which works to alleviate poverty worldwide, transparency transformed office operations. Their Kinshasa office replaced lengthy, unproductive status meetings with Scrum boards. Instead of hours-long sessions where problems were stated but nothing resolved, the director could simply walk around and instantly see where issues were occurring. This allowed the organization to focus its limited resources on the highest-impact activities. Implementing transparency requires courage. At Scrum, Inc., Sutherland makes everything visible—salaries, financials, expenditures—accessible to everyone. "I've never understood why anyone would want to keep this stuff secret except to further their own individual agenda or keep people infantilized," he explains. "I want the administrative assistant to be able to read the profit-and-loss statement and understand precisely how what he does contributes to that." To implement transparency in your organization, start with a physical Scrum board in a prominent location where team members gather. Make it impossible to ignore work status. Hold Daily Stand-ups in front of this board so everyone maintains awareness of progress and impediments. Gradually expand transparency beyond project work to include decision-making processes, company performance, and strategic priorities. Address resistance by demonstrating how transparency benefits everyone—it's not about surveillance but about enabling better decisions and more effective collaboration. Remember that transparency creates a virtuous cycle—as information becomes more accessible, coordination improves, trust increases, and people become more invested in collective success rather than individual accomplishment or avoiding blame. This transformation can be uncomfortable initially, but the results speak for themselves in faster delivery, higher quality, and more engaged teams.

Chapter 7: Implement Change Through Incremental Delivery

The traditional approach to change—whether launching products, implementing policies, or transforming organizations—involves extensive planning followed by a dramatic "big bang" rollout. This approach carries enormous risk and frequently fails because it assumes we can predict exactly what will work without testing our assumptions. Scrum offers a fundamentally different model: implement change through small, valuable increments, gathering feedback at each step to guide subsequent decisions. This incremental approach is illustrated by Team WIKISPEED, which builds cars that get over 100 miles per gallon, are street legal, achieve five-star crash ratings, and cost less than a Toyota Camry. Unlike traditional manufacturers who spend years developing vehicles before production, Team WIKISPEED works in one-week Sprints. Every Thursday they evaluate their backlog of tasks—from prototyping dashboard designs to testing turn signals—and decide what they can complete in the coming week. By "complete," they mean truly done—these features work, the car drives, each week. This rapid iteration allows them to discover problems early, incorporate user feedback continuously, and deliver remarkable results with limited resources. The key to successful incremental delivery is the concept of the "Minimum Viable Product" (MVP)—the smallest thing you can build that delivers genuine value and generates meaningful feedback. This might be a camera that takes pictures but can't focus, a dining room set with just two chairs, or a vaccine distributed to five villages instead of a hundred. By releasing something that works, even if limited, you learn what people actually value rather than what they say they value. For example, users might claim they want both landscape mode and Facebook sharing in a photo app, but when using the product, they never use landscape mode while consistently sharing photos. This feedback allows you to prioritize future development around features people actually use rather than those they merely request. Washington state's government demonstrates how incremental delivery can transform even bureaucratic organizations. Michael DeAngelo, Deputy Chief Information Officer, applied Scrum to policy development: "We set the goal that every week we're going to change one thing. We're taking an incremental approach. We have a potentially shippable product every single week that can be felt by the agencies." Rather than creating comprehensive documents addressing every possibility, they make small, continuous improvements that deliver immediate value. To implement incremental delivery in your organization, start by identifying the smallest valuable unit of your product, service, or change initiative that could be delivered to users. Break larger initiatives into these small, independently valuable pieces. Establish short cycles (one to four weeks) with a clear definition of "Done" for each cycle—something tangible that can be demonstrated and used. After each increment, gather feedback from actual users, not just stakeholders, and use this information to adjust priorities for the next cycle. The most powerful aspect of incremental delivery is how it transforms risk management. By delivering small pieces frequently, you discover problems when they're inexpensive to fix, validate assumptions through real-world testing, and build momentum through visible progress. Most importantly, you create the opportunity to change direction when you discover better approaches—something impossible with traditional big-bang implementations. As Scrum consultant Rick Anderson notes when advising government agencies: "Once you have outcome-based goals, you can start writing legislation that is outcome-based." Rather than specifying exactly how to build a bridge, legislation might say: "We want X number of people to travel over this waterway in Y amount of time with Z cost. How you do that is up to you." This approach encourages innovation and adaptation, producing better results with fewer resources.

Summary

The essence of Scrum isn't just a methodology but a fundamental shift in how we approach work and achievement. By embracing rhythmic cycles, self-organizing teams, relentless waste elimination, value-based prioritization, happiness metrics, radical transparency, and incremental delivery, organizations can transform performance while creating more fulfilling work environments. As Jeff Sutherland writes, "Free your mind, and your ass will follow" — once people experience the liberation that comes from working in this framework, they rarely want to return to traditional approaches. The most powerful takeaway is that you don't have to accept the status quo. Whether you're trying to build better software, educate students, alleviate poverty, or simply complete your weekend to-do list more effectively, these principles can help you achieve twice as much in half the time. Start today by choosing just one practice—perhaps daily stand-ups or a simple Scrum board—and implement it with your team. Watch how quickly small changes in process can yield dramatic improvements in results. Remember that Scrum isn't about wishing for a better world, but providing a practical, actionable framework to create one. Don't listen to cynics who tell you what can't be done. Amaze them with what can.

About Author

Loading...

Jeff Sutherland

Sutherland is a Graduate of the United States Military Academy, a Top Gun of his USAF RF-4C Aircraft Commander class[citation needed]. He flew more than one hundred missions over North Vietnam[citation needed]. After 11 years in the military, he became a doctor at the University of Colorado School of Medicine[citation needed]. Here he got involved in data collection and IT systems development.Dr. Jeff Sutherland is one of the inventors of the Scrum software development process. Together with Ken Schwaber, he created Scrum as a formal process at OOPSLA'95. Sutherland helped to write the Agile Manifesto in 2001. He is the writer of The Scrum Guide.by https://en.wikipedia.org/wiki/Jeff_Su...It's professional profile on LinkedIn is :linkedin.com/in/jeffsutherland

Read more