Who should read *Scrum* by Jeff Sutherland?

This book is ideal for business leaders, project managers, and teams seeking to boost efficiency. It’s particularly valuable for those navigating complex projects, as it provides actionable strategies for adaptive planning, team collaboration, and eliminating bureaucratic bottlenecks.

Is *Scrum* by Jeff Sutherland worth reading?

Yes—it’s a practical guide for transforming workflows. Sutherland combines battlefield-tested tactics with case studies (e.g., tech companies, government agencies) to demonstrate how Scrum reduces timelines while maintaining quality. Readers gain tools for sprint planning, prioritization, and fostering team accountability.

What are the key principles of Scrum according to Jeff Sutherland?

Core principles include breaking work into short cycles (sprints), holding daily stand-ups for progress updates, and prioritizing tasks via a dynamic backlog. Teams stay focused on delivering incremental value while adapting to feedback, ensuring alignment with stakeholder needs.

How does Scrum differ from traditional project management?

Unlike rigid, linear methods, Scrum uses iterative sprints (1-4 weeks) to tackle complex tasks. It emphasizes team autonomy, continuous improvement, and transparency over fixed plans, reducing waste from miscommunication or shifting priorities.

What is a Sprint in Scrum methodology?

A sprint is a time-boxed cycle (typically 1-4 weeks) where teams complete predefined tasks. Each sprint ends with a review to assess outcomes and a retrospective to refine processes, ensuring rapid adaptation to changes.

Can Scrum be applied outside software development?

Yes—Sutherland highlights uses in education, government (e.g., FBI), and corporate sectors. Scrum’s focus on collaboration and iterative progress makes it effective for any complex project requiring flexibility.

What role does leadership play in Scrum teams?

Leaders act as facilitators, not micromanagers. They empower cross-functional teams to self-organize, remove obstacles, and align work with overarching goals, fostering a culture of trust and shared accountability.

Scrum

Q: What is *Scrum: The Art of Doing Twice the Work in Half the Time* about?

*Scrum: The Art of Doing Twice the Work in Half the Time* outlines Jeff Sutherland’s revolutionary project management framework, emphasizing productivity through iterative workflows, team autonomy, and waste reduction. It blends real-world examples—like streamlining FBI projects—with principles from Agile and Lean methodologies to help organizations deliver value faster.

The Art of Doing Twice the Work in Half the Time

Jeff Sutherland

4.14(23313 Reviews)

Overview of Scrum

Revolutionize your workflow with "Scrum" - the methodology that helped the FBI modernize databases and engineers build 100-mpg cars. Jeff Sutherland's #1 ranked guide reveals how teams worldwide achieve twice the results in half the time. What could you accomplish tomorrow?

Choose how it's told

One book. Many ways to hear it.

Same ideas from Scrum. Pick the voice, depth, and pace that fits you. Switch anytime.

Chapter 1

The Broken System: Why Traditional Work Methods Fail

The story begins with a dark day for Jeff Johnson, an FBI project manager watching his ambitious system modernization project collapse after years of work and millions wasted. This disaster highlighted everything wrong with traditional "waterfall" project management: rigid planning, delayed feedback, and inevitable obsolescence. In the early 2000s, while terrorists communicated via cutting-edge technology, FBI agents were still shuffling paper files between offices. This failure wasn't unique. Studies show that 68% of software projects fail, and even "successful" ones typically exceed budgets by 200% and timelines by 70%. Why? Because our traditional approach to work is fundamentally flawed. We plan exhaustively upfront, assuming we can predict the future. We separate thinking from doing. We build elaborate hierarchies that slow decision-making and stifle innovation. The problem isn't just in software. From manufacturing to healthcare to government, we see the same patterns: massive waste, missed deadlines, ballooning costs, and demoralized teams. The traditional management paradigm, born in the industrial age, simply doesn't work in today's complex, rapidly changing world. What if we could achieve twice the results in half the time? What if teams could be both more productive and happier? What if we could embrace change rather than fear it? These questions led to the development of Scrum-not just a methodology but a fundamentally different way of working that turns traditional management upside down. Instead of detailed long-term plans, Scrum embraces adaptation. Instead of separating thinkers from doers, it empowers self-organizing teams. Instead of measuring hours worked, it focuses on value delivered. The results have been nothing short of revolutionary, with companies reporting productivity improvements of 300-800%. But the journey to this new way of working begins with acknowledging that the way the world works is broken.

Chapter 2

Scrum Fundamentals: A New Framework for Work

Scrum represents a radical departure from traditional management approaches. Rather than pursuing the illusion of control through elaborate planning, Scrum embraces uncertainty and adaptation. Think of it like navigating a sailing ship: you can't control the wind, but you can continuously adjust your sails to reach your destination. The name "Scrum" comes from rugby, where players huddle closely together, moving as a coordinated unit with shared purpose. Similarly, Scrum teams work as cohesive units, adapting continuously to changing conditions. At its core, Scrum replaces the traditional "plan-build-test" sequence with continuous cycles of "inspect and adapt." These cycles take the form of "Sprints"-short, focused periods (typically 1-4 weeks) during which teams commit to delivering specific, valuable outcomes. Each day begins with a brief "Daily Scrum" where team members synchronize their efforts and identify obstacles. At the end of each Sprint, the team demonstrates working results to stakeholders and conducts a retrospective to improve their process. This approach creates a virtuous cycle: plan a little, do a little, check results, adjust, and repeat. It's essentially the scientific method applied to work-form hypotheses, test them quickly, learn from results, and iterate. This contrasts sharply with traditional approaches where feedback comes too late to be useful. What makes Scrum powerful isn't just its practices but its underlying principles. Transparency ensures everyone sees the true state of work. Inspection means regularly examining progress and process. Adaptation means changing course based on what's learned. These principles create an environment where teams can respond intelligently to change rather than blindly following outdated plans. Scrum isn't limited to software development. It's been successfully applied in manufacturing, education, marketing, operations, healthcare, and even wedding planning. The fundamental patterns work anywhere complex problems need solving in uncertain environments. When implemented properly, Scrum typically doubles productivity while significantly improving quality and team satisfaction. But achieving these results requires more than adopting practices-it requires embracing a fundamentally different mindset about how work should be organized and managed.

See every word as you hear it

Read along effortlessly as each word of Scrum lights up in real time.

Chapter 3

The Origins: From Vietnam to Revolutionary Management

My journey to creating Scrum began in the skies over Vietnam, where I flew reconnaissance missions in an RF-4C Phantom. Each mission demanded rapid observation, orientation, decision, and action-what military strategist John Boyd later called the OODA loop. This experience taught me that survival depends on adapting faster than your environment changes. After returning from war, I applied this mindset to my academic and business career. While leading technology at a banking subsidiary in the 1980s, I faced a failing operation with plummeting morale and productivity. The traditional management approach wasn't working. Drawing on emerging ideas about complex adaptive systems, I proposed creating a "company within a company"-a small, autonomous team focused solely on ATM networks. With the CEO's blessing, we assembled a cross-functional team, eliminated individual incentives in favor of team performance, and gave them autonomy to solve problems. Within six months, productivity skyrocketed. We delivered a system that transformed banking across North America, making ATMs truly reliable for the first time. This experience showed me the power of autonomous, purpose-driven teams. Later, at the MIT AI Lab, I encountered another inspiration: a self-organizing robot that could navigate complex environments without central control. Instead, simple rules allowed its components to adapt independently toward a common goal. Could human teams work this way? The final piece came in 1993 when I discovered a Harvard Business Review article about how companies like Honda and Canon were developing products differently. Rather than sequential handoffs between specialized departments, they used "rugby" approaches-small, cross-functional teams working in overlapping phases with extraordinary results. This resonated with my experiences. The traditional "waterfall" approach-where work cascades sequentially from planning to execution to testing-was fundamentally flawed. It assumed we could predict everything upfront and that requirements wouldn't change. Reality proved otherwise. Synthesizing these insights with principles from lean manufacturing and the quality movement, I developed Scrum as a new framework for product development. The name came from that rugby analogy-teams that function as a unit, moving the ball downfield through continuous interaction rather than predetermined plays. The results were immediate and dramatic. Teams using Scrum completed projects in a fraction of the time while delivering higher quality and adapting seamlessly to changing requirements. The secret wasn't working harder but working differently-focusing on continuous improvement, rapid feedback, and self-organization.

Chapter 4

The Power of Teams: Transcending Individual Capabilities

While our culture often celebrates individual genius, the truth is that teams accomplish virtually everything meaningful in business. More importantly, the difference between great and mediocre teams far exceeds differences between individual performers. A high-performing team can be 5-10 times more productive than an average one, regardless of the individuals involved. I witnessed this principle dramatically at West Point, where the underestimated L2 regiment transformed from worst to first by focusing on transparency and collective improvement. They posted their mistakes publicly, creating accountability and identifying patterns they could address systematically. This transparency, combined with a shared transcendent purpose, enabled them to achieve what seemed impossible. Great teams need three essential elements-what I call the "three-legged stool" of high performance. First, they need a transcendent purpose that inspires commitment beyond self-interest. Second, they need autonomy to determine how they'll achieve their objectives. Third, they need all the skills necessary to deliver end-to-end results. This last element is particularly crucial. Traditional organizations separate functions into silos, creating handoffs and delays. Scrum teams are cross-functional, containing all the skills needed to deliver value. This approach was validated dramatically by U.S. Special Operations in Iraq, where small, cross-trained teams proved far more effective than traditional military units with rigid specialization. Team size matters tremendously. The ideal Scrum team has seven members (plus or minus two). This isn't arbitrary-it reflects fundamental cognitive limitations. Research shows that humans can only track about seven items in working memory, and the number of communication channels increases exponentially with team size. Beyond nine people, coordination costs skyrocket while productivity plummets. Every Scrum team needs a Scrum Master-not a traditional manager but a facilitator who helps the team improve its process and removes organizational obstacles. The role was inspired by the All Blacks rugby team's rituals and leadership approach, focusing on service rather than control. Perhaps most importantly, Scrum recognizes that when things go wrong, the problem usually lies in the system, not the individuals. This insight comes from attribution theory in psychology-we tend to blame people when the environment is actually the culprit. Like the famous Milgram experiments showed, ordinary people can do terrible things in the wrong system. Rather than blaming individuals, Scrum focuses on creating systems where good people can do great work together.

Get more out of Scrum

Get daily insights from 100K+ lessons
Words light up in sync with the audio
Your library saved on every device

Chapter 5

The Discipline of Time: Sprints and Daily Rhythm

Time is the one truly finite resource we have. We can always get more money, more materials, more people-but we can never get more time. This reality creates both urgency and focus when properly harnessed. The Sprint forms the heartbeat of Scrum. Inspired by practices at the MIT Media Lab, a Sprint is a short, focused period (typically 1-4 weeks) during which a team commits to delivering specific results. This timeboxing creates a healthy pressure that focuses attention and prevents perfectionism or endless tinkering. At the end of each Sprint, the team must demonstrate working results-not plans or promises but actual, functional deliverables that stakeholders can experience. This regular cadence of demonstrations creates transparency, builds trust, and provides opportunities for course correction before too much time or money is invested in the wrong direction. The power of Sprints comes from their regularity. Like heartbeats, they establish a predictable rhythm that teams can count on. Everyone knows when planning happens, when work happens, when demonstrations happen, and when reflection happens. This rhythm reduces uncertainty and creates a sense of progress that motivates continued effort. Within each Sprint, the Daily Scrum (sometimes called the daily standup) creates an even finer-grained rhythm. For 15 minutes each day, team members synchronize by answering three questions: What did I do yesterday? What will I do today? What obstacles are in my way? This isn't a status report to management but a coordination mechanism for the team itself. The Daily Scrum makes progress and problems visible immediately, not at the end of a project when it's too late to adjust. It reinforces accountability without micromanagement. And it ensures that obstacles are identified and addressed quickly rather than festering. This disciplined approach to time transforms how teams work. Instead of long, unfocused efforts with uncertain endpoints, work becomes a series of focused sprints with clear goals and regular feedback. Instead of discovering problems too late, teams surface and solve them daily. And instead of hoping for eventual success, teams deliver incremental value continuously. The result is not just better productivity but greater predictability and reduced risk. By breaking work into small increments and getting feedback at each step, teams avoid the massive failures that plague traditional projects. They can change direction when needed without throwing away months of work. And they build confidence through a track record of regular delivery rather than promises of future results.

Chapter 6

Eliminating Waste: The Path to Flow and Excellence

In traditional work environments, an astonishing amount of time and energy is wasted on activities that create no value. The Japanese manufacturing concept of "muda" (waste) helps us recognize these patterns so we can eliminate them. Three types of waste particularly plague knowledge work: First is multitasking-the illusion that we can do several things at once effectively. Research conclusively shows this is false. When we switch between tasks, we lose context, make more errors, and take significantly longer. Studies comparing sequential work to multitasking show productivity drops of 40% or more when attempting multiple tasks simultaneously. Our brains simply aren't wired for it. In Scrum, we focus on completing one valuable item before starting another. Second is partially done work-the accumulation of unfinished tasks that deliver no value until completed. Half-built features, untested code, or unimplemented designs are like inventory in manufacturing-they tie up resources without generating returns. Worse, partially done work often becomes obsolete before completion. Scrum addresses this by focusing on completing valuable increments within each Sprint rather than starting many things and finishing few. Third is defects-problems that must be fixed later at much higher cost. Research shows that fixing a software bug immediately costs a fraction of fixing it weeks or months later when context is lost and dependencies have increased. The principle of "doing it right the first time" isn't about perfectionism but about addressing quality issues when they're cheapest to fix. Beyond these specific wastes lies the broader concept of "flow"-the state where work proceeds smoothly without interruption or friction. Achieving flow requires eliminating not just obvious waste but anything that doesn't directly contribute to creating value. Even some Scrum practices themselves might be considered waste if they don't serve the team's needs in a specific context. The ultimate goal is work that feels like what psychologist Mihaly Csikszentmihalyi calls "flow state"-where challenges match skills perfectly, attention is fully absorbed, and time seems to disappear. This state represents not just peak productivity but peak human experience. By eliminating waste and focusing on value, Scrum creates conditions where flow becomes possible not just occasionally but systematically. Importantly, sustainable pace is essential to eliminating waste. Contrary to traditional thinking, working longer hours typically reduces productivity rather than increasing it. Scott Maxwell's venture capital firm discovered that limiting work to 40 hours per week and ensuring proper rest actually improved results dramatically. This aligns with research showing that judgment deteriorates with fatigue, leading to poor decisions and costly rework.

See every word as you hear it

Read along effortlessly as each word of Scrum lights up in real time.

Chapter 7

Planning Reality: How to Estimate and Deliver Reliably

Traditional project planning often resembles fantasy more than reality. Consider Medco Health's crisis when they promised Wall Street a complete system overhaul by a specific date-without any realistic understanding of what that would take. When I was called in, they had mountains of documents but no clear path to delivery. The fundamental problem is that humans are terrible at absolute estimation-guessing exactly how long something will take. However, we're remarkably good at relative sizing-comparing one task to another. Scrum leverages this natural ability through techniques like Planning Poker, where team members independently estimate task sizes using a modified Fibonacci sequence (1, 2, 3, 5, 8, 13, etc.) that reflects how uncertainty increases with size. When estimates diverge significantly, the team discusses assumptions until reaching consensus. This approach harnesses collective wisdom while avoiding anchoring biases where early opinions unduly influence others. The key insight is that the people doing the work should estimate it-not managers or specialists who won't actually perform the tasks. Another crucial shift is focusing on user stories rather than technical tasks. A user story captures who wants what and why: "As a [user role], I want [capability] so that [benefit]." This format ensures everyone understands the human context and value of each feature, not just its technical requirements. Effective stories follow the INVEST criteria: Independent (can be developed separately), Negotiable (details can be discussed), Valuable (delivers benefit to users), Estimable (team can size it), Small (fits within a Sprint), and Testable (success can be verified). Stories that don't meet these criteria should be refined before work begins. For planning Sprints, teams use their established velocity-the amount of work they've historically completed in a Sprint-to determine how much they can commit to. This creates realistic forecasts based on actual performance rather than wishful thinking. By tracking velocity over time and removing obstacles that limit it, teams naturally increase their productivity without artificial pressure. The Definition of Done provides clarity about when work is truly complete. Without this shared understanding, teams might consider something "done" when it's coded but not tested, or tested but not documented. A robust Definition of Done includes all steps needed to deliver truly releasable quality. This approach to planning embraces reality rather than fighting it. It acknowledges uncertainty while providing frameworks to manage it. It leverages empirical data rather than optimistic guesses. And it focuses on delivering incremental value rather than promising perfect solutions that never materialize.

Chapter 8

The Happiness Factor: Why Joy Drives Performance

We often assume success leads to happiness, but research shows the opposite is true: happiness precedes and predicts success. People who report higher happiness levels show 31% higher productivity, 37% higher sales, and significantly better health outcomes. This isn't just feel-good philosophy-it's practical business sense. The pursuit of happiness isn't about momentary pleasure but about finding meaning and progress in ongoing challenges. Like mountain climbers who find joy in the difficult ascent rather than just the summit, teams find fulfillment in overcoming obstacles together toward meaningful goals. In Scrum, we actively measure happiness alongside traditional metrics. Tools like the "Happiness Metric" ask team members simple questions about their satisfaction with their role and the company. These measurements often predict problems before they appear in performance data, serving as leading indicators of team health. Transparency plays a crucial role in creating happy, high-performing teams. When everyone can see the state of work, priorities, and progress, they make better decisions and feel more connected to the larger purpose. Companies like PatientKeeper and Zappos have embraced radical transparency, making virtually all information available to all employees. This creates an environment where people can exercise autonomy effectively and see how their work contributes to the whole. However, teams can sometimes fall into what I call the "happiness bubble"-a state of complacency after initial improvements where they stop pushing for further growth. Breaking this bubble requires conscious effort. Measuring velocity helps identify plateaus. Introducing "wise fools" who question comfortable assumptions can disrupt complacency. Sometimes bringing in new team members with fresh perspectives helps teams see opportunities they've become blind to. The relationship between happiness and performance creates a virtuous cycle. Happy teams perform better, which creates more success, which increases happiness further. But this requires intentional cultivation-creating environments where people have autonomy, mastery, and purpose, where they receive rapid feedback on their work, and where they can see their impact on customers and colleagues. This approach stands in stark contrast to traditional management, which often treats happiness as irrelevant or assumes it comes from extrinsic rewards like bonuses. Scrum recognizes that intrinsic motivation-the desire to do good work because the work itself is rewarding-is far more powerful and sustainable.

Get more out of Scrum

Get daily insights from 100K+ lessons
Words light up in sync with the audio
Your library saved on every device

Chapter 9

Strategic Prioritization: Maximizing Value Through Focus

Meeting Scott Maxwell at the Newton Center, we discussed how Scrum isn't just about speed but creating impact. What separates failed startups like Pets.com from successes like Zappos is their ability to focus on what truly matters. The Product Backlog-a prioritized list of everything that might be valuable-becomes the central strategic tool in Scrum. Creating an effective backlog starts with asking fundamental questions: What will deliver the most value with the least risk? What will teach us the most about what customers actually want? What can we deliver quickly to start generating feedback and revenue? The answers guide prioritization decisions that can make or break a product. The Product Owner role is crucial here. Inspired by Toyota's Chief Engineers, this person must deeply understand customer needs and translate them into clear priorities for the team. They don't dictate how work is done but are absolutely clear about what matters most and why. This role requires market insight, stakeholder management skills, and the ability to make tough trade-off decisions. The military concept of the OODA loop (Observe, Orient, Decide, Act) applies perfectly to Product Ownership. Just as fighter pilots gain advantage by cycling through this loop faster than opponents, Product Owners create market advantage by rapidly observing customer reactions, orienting to new information, deciding on adjustments, and acting through the team. This creates a learning cycle that outpaces competitors. A common mistake is treating everything as high priority. When everything is important, nothing is important. Effective prioritization means making hard choices about what to do first, what to do later, and what not to do at all. The backlog should be regularly refined to reflect new information and changing circumstances. The concept of Minimum Viable Product (MVP) embodies this prioritization principle. By delivering the smallest possible product that solves a real customer problem, teams can start generating value and learning immediately rather than waiting for perfect solutions. Each subsequent iteration adds the next most valuable features based on actual customer feedback rather than speculation. This approach extends to contracts and budgeting as well. Traditional fixed-scope contracts create perverse incentives where changes (even valuable ones) become expensive "change requests." Agile contracts instead fix time and cost while allowing scope to evolve based on learning. This "money for nothing and change for free" approach ensures resources are always directed toward maximum value rather than fulfilling outdated specifications.

Chapter 10

Transforming the World: Scrum Beyond Software

Scrum's principles extend far beyond software development, offering powerful approaches to some of society's most pressing challenges. In education, for example, traditional classroom models often fail to engage students or prepare them for modern collaborative work. Schools like Ashram College in the Netherlands have revolutionized education by implementing Scrum with students. In these classrooms, students organize themselves into small teams, plan their work on Scrum boards, and take ownership of their learning process. Rather than passively receiving information from teachers, they actively collaborate to master material, identifying each other's strengths and weaknesses to optimize collective learning. The results have been remarkable-grades improve, engagement increases, and students develop crucial collaboration skills alongside academic knowledge. This educational revolution is spreading globally. A foundation in the Netherlands now trains teachers in Scrum techniques, while similar initiatives are emerging worldwide. Universities like Harvard have adopted team-based learning approaches that reflect Scrum principles. This movement represents a fundamental shift in how we think about education-from standardized content delivery to collaborative knowledge creation. In humanitarian work, Scrum has proven equally transformative. The Grameen Foundation, inspired by Muhammad Yunus's microfinance innovations, uses Scrum to connect Ugandan farmers with vital agricultural knowledge via smartphones. Community Knowledge Workers use simple phones to access information that dramatically improves crop yields and incomes. By applying Scrum principles, the foundation maximizes impact with limited resources, helping lift communities from extreme poverty. Even government, traditionally resistant to innovation, has begun adopting Scrum approaches. In Olympia, Washington, government leaders implemented "Lean Government" practices based on Scrum principles. Despite initial resistance, these changes have improved service delivery while reducing bureaucratic waste. The transparency and accountability inherent in Scrum align perfectly with democratic ideals, offering a path to more responsive governance. Risk management represents another area where Scrum excels beyond software. Traditional approaches often involve elaborate planning to mitigate hypothetical risks, consuming resources that could be better used elsewhere. Scrum's incremental delivery model reduces financial, technical, and market risks by validating assumptions early through working prototypes. The "fail fast" approach means discovering problems when they're cheap to fix rather than after major investments. These diverse applications share common patterns: small, cross-functional teams working in short cycles with clear priorities and continuous feedback. The specifics vary by context, but the fundamental principles of transparency, inspection, and adaptation prove remarkably universal.

See every word as you hear it

Read along effortlessly as each word of Scrum lights up in real time.

Chapter 11

The Future of Work: Lessons from Revolutionary Organizations

The future of work is already emerging in organizations that have fully embraced Scrum principles. Valve Corporation, a highly successful gaming company, offers a fascinating glimpse of what's possible when traditional management hierarchies disappear entirely. At Valve, employees have complete autonomy to decide what projects they work on. There are no managers in the traditional sense-instead, people organize themselves around opportunities they find compelling. Projects begin when someone decides to start one and can convince colleagues to join. This radical self-organization has produced some of the gaming industry's most innovative products while creating extraordinary employee satisfaction. This approach represents the highest level of the Shu Ha Ri progression in Scrum adoption. "Shu" is the beginning stage where teams follow Scrum practices precisely to understand their purpose. "Ha" is the middle stage where teams begin adapting practices to their specific context. "Ri" is the mastery stage where the principles become so internalized that formal practices may evolve or even disappear while the essence remains. Organizations like Valve have reached this "Ri" state-they may not use formal Scrum terminology, but they embody its principles of self-organization, rapid adaptation, and value focus at the deepest level. Their success suggests that the future belongs not to command-and-control hierarchies but to networks of autonomous teams aligned by shared purpose. This evolution isn't limited to small tech companies. Even large organizations like the U.S. military have discovered the power of networked teams over rigid hierarchies. General Stanley McChrystal's transformation of Joint Special Operations Command in Iraq demonstrated how decentralized decision-making and information sharing could dramatically outperform traditional command structures in complex, rapidly changing environments. The common thread across these examples is a shift from extrinsic motivation (rewards and punishments) to intrinsic motivation (autonomy, mastery, and purpose). When people are connected to meaningful goals, equipped with necessary skills, and trusted to determine how best to achieve those goals, they consistently outperform traditional management approaches. This represents not just a different way of organizing work but a fundamentally different understanding of human motivation and potential. Rather than seeing people as resources to be directed and controlled, Scrum sees them as creative problem-solvers who thrive on challenge and contribution when given the right environment. As more organizations experience the dramatic performance improvements that come with this approach, traditional management practices will increasingly appear as outdated as typewriters in the age of computers. The future of work isn't about better controlling people-it's about creating conditions where they can achieve their full potential in service of meaningful goals.

Chapter 12

Implementing Scrum: A Practical Guide to Getting Started

Starting with Scrum doesn't require massive organizational transformation-it can begin with a single team and expand as results demonstrate its value. The essential first steps are straightforward but require commitment to a new way of working. Begin by selecting a Product Owner who understands customer needs and can articulate a clear vision of value. This person will prioritize work and make trade-off decisions, ensuring the team always works on what matters most. Next, form a cross-functional team of 5-9 people with all the skills needed to deliver end-to-end value. Designate a Scrum Master to guide the process and remove obstacles. Create an initial Product Backlog by listing all potential features or requirements, then prioritize them based on value and risk. Have the team estimate the relative size of backlog items using Planning Poker or similar techniques. These estimates, combined with the team's velocity (determined after a few Sprints), will enable forecasting when specific items might be delivered. Establish a Sprint length-typically two weeks-and conduct a Sprint Planning meeting where the team selects high-priority backlog items they can complete within that timeframe. Create a Sprint Backlog detailing the specific tasks needed to deliver those items. Make work visible using a Scrum Board with columns for "To Do," "In Progress," and "Done." Track progress daily using a Burndown Chart showing remaining work versus time. Hold brief Daily Scrums where team members synchronize their efforts and identify obstacles. At the end of each Sprint, conduct a Review where the team demonstrates working results to stakeholders and gathers feedback. Follow this with a Retrospective where the team reflects on their process and identifies improvements for the next Sprint. This cycle-plan, execute, review, improve-repeats with each Sprint, creating a rhythm of continuous delivery and improvement. As teams gain experience, they naturally adapt these practices to their specific context while maintaining the core principles of transparency, inspection, and adaptation. Common challenges include resistance from traditional managers who fear loss of control, difficulty defining "Done" completely enough to ensure quality, and the temptation to revert to old habits when pressure increases. Addressing these challenges requires persistent leadership support, clear communication about the benefits of Scrum, and patience as new habits form. Remember that Scrum is fundamentally about empiricism-learning through experience rather than theory. The practices provide a starting point, but the real power comes from the team's growing ability to inspect and adapt both their product and their process based on real-world feedback.

★★★★★

You made it to the end of Scrum

Loved by 1M+ learners

“23 days in and I have used it every single day. It is part of my daily habit now.”

jayallen

Key Themes in Scrum

agile methodology
iterative development
team self-organization
continuous improvement
waste reduction

Quotes from Scrum

We plan exhaustively upfront, assuming we can predict the future.
Scrum embraces uncertainty and adaptation.
Survival depends on adapting faster than your environment changes.
The traditional management paradigm simply doesn't work.
Scrum isn't just a methodology but a fundamentally different way of working.

Characters in Scrum

Jeff SutherlandAuthor and creator of the Scrum methodology
Jeff JohnsonFBI project manager of the Sentinel project
John BoydMilitary strategist who developed the OODA loop

About the Author

Jeff Sutherland is the co-creator of Scrum and bestselling author of Scrum: The Art of Doing Twice the Work in Half the Time, a seminal work on agile project management and organizational productivity. A graduate of the United States Military Academy at West Point, former U.S. Air Force pilot with 100+ combat missions, and Stanford-trained statistician, Sutherland blends military precision and data-driven insights to revolutionize team efficiency. His PhD in biometrics from the University of Colorado School of Medicine further informs his empirical approach to workflow optimization.

As CEO of Scrum Inc. and co-author of The Scrum Guide, Sutherland has shaped modern agile practices adopted by Fortune 500 companies and tech startups alike. His framework, developed through leadership roles at 11 software companies and refined via scaling models like Scrum@Scale, addresses core themes of iterative development, waste reduction, and cross-functional collaboration. The book has sold over 100,000 copies globally and been translated into 20+ languages, cementing its status as a foundational text in business innovation.

Download Summary of Scrum

Get the Scrum summary as a free PDF or EPUB. Print it or read offline anytime.

Users also liked

The Scrum Fieldbook

J.J. Sutherland

The elements of scrum

Chris Sims& Hillary Louise Johnson

Agile Project Management for Beginners

Bryan Mathis

Learning Agile

Andrew Stellman & Jennifer Greene

Scrum Insights for Practitioners

Hiren Doshi

Strategy Sprints

Simon Severino

Strategic Project Management Made Simple

Terry Schmidt

Lean UX

Jeff Gothelf

FAQs About This Book

Part of a Learning Plan

LEARNING PLAN

Discover more

LEARNING PLAN

The Science of Starting

This plan is essential for professionals and students who struggle with procrastination and the paralysis of starting new tasks. It provides a scientific approach to overcoming biological resistance and optimizing your digital environment for maximum output.

1 h 45 m•3 Sections

LEARNING PLAN

The Bullet Journal Strategy

In an era of digital distraction, this strategy offers a tactile, intentional approach to personal management. It is ideal for professionals and creatives who need to bridge the gap between daily chaos and long-term aspirations through structured reflection.

1 h 30 m•3 Sections

LEARNING PLAN

Digital Transformation: Systems Over Software

This plan is essential for leaders and entrepreneurs who feel stuck in reactive cycles and want to build scalable operations. It bridges the gap between simply using digital tools and architecting a business that improves itself through systems thinking.

2 h•4 Sections

LEARNING PLAN

Mastering Enterprise SRE Discovery

This plan is designed for technical sales professionals and solutions architects looking to penetrate complex enterprise environments. It bridges the gap between high-level discovery and the specific, high-stakes requirements of Site Reliability Engineering teams.

2 h•4 Sections

LEARNING PLAN

The Architecture of Modern Grit

This plan is designed for high-performers and professionals who feel plateaued by mental fatigue or inconsistent motivation. It provides a blueprint for building a resilient psychological framework, making it essential for anyone looking to master self-discipline and long-term endurance.

2 h•4 Sections

LEARNING PLAN

The Systems Thinking Advantage for Founders

In the volatile world of startups, founders often fall into the trap of reactive management. This learning plan is essential for entrepreneurs who want to move beyond chaos by mastering the structural dynamics of their business. It is ideal for early-stage leaders aiming to build scalable, stable organizations through first-principles design.

1 h 30 m•3 Sections

LEARNING PLAN

The Socratic Leader's Decision Toolkit

In an era of rapid change, leaders often rely on intuition over rigorous logic. This toolkit is designed for executives and managers who want to blend ancient wisdom with modern strategy to make more ethical, resilient choices.

1 h 30 m•3 Sections

LEARNING PLAN

The 30-Minute Discovery Playbook

In fast-paced retail environments, technical teams often struggle to articulate the business value of observability. This playbook is essential for sales engineers and technical leaders who need to master concise discovery and align technical pain points with executive priorities.

1 h 30 m•3 Sections

From Columbia University alumni built in San Francisco

LOVED BY

1,000,000+ curious minds.

4.7

avg rating

1M+ learners

"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."

@Moemenn

"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."

@Chloe, Solo founder, LA

117

"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."

@Raaaaaachelw

"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."

@Matt, YC alum

108

"Reading used to feel like a chore. Now it’s just part of my lifestyle."

@Erin, Investment Banking Associate , NYC

254

"Feels effortless compared to reading. I’ve finished 6 books this month already."

@djmikemoore

"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."

@Pitiful

4.5K

"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."

@SofiaP

"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"

@Jaded_Falcon

201

"It is great for me to learn something from the book without reading it."

@OojasSalunke

"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."

@Leo, Law Student, UPenn

483

"Makes me feel smarter every time before going to work"

@Cashflowbubu

See more on how BeFreed is discussed

From Columbia University alumni built in San Francisco

LOVED BY

1,000,000+ curious minds.

4.7

avg rating

1M+ learners

"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."

@Moemenn

"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."

@Chloe, Solo founder, LA

117

"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."

@Raaaaaachelw

"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."

@Matt, YC alum

108

"Reading used to feel like a chore. Now it’s just part of my lifestyle."

@Erin, Investment Banking Associate , NYC

254

"Feels effortless compared to reading. I’ve finished 6 books this month already."

@djmikemoore

"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."

@Pitiful

4.5K

"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."

@SofiaP

"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"

@Jaded_Falcon

201

"It is great for me to learn something from the book without reading it."

@OojasSalunke

"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."

@Leo, Law Student, UPenn

483

"Makes me feel smarter every time before going to work"

@Cashflowbubu

"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."

@Moemenn

"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."

@Chloe, Solo founder, LA

117

"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."

@Raaaaaachelw

"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."

@Matt, YC alum

108

"Reading used to feel like a chore. Now it’s just part of my lifestyle."

@Erin, Investment Banking Associate , NYC

254

"Feels effortless compared to reading. I’ve finished 6 books this month already."

@djmikemoore

"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."

@Pitiful

4.5K

"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."

@SofiaP

"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"

@Jaded_Falcon

201

"It is great for me to learn something from the book without reading it."

@OojasSalunke

"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."

@Leo, Law Student, UPenn

483

"Makes me feel smarter every time before going to work"

@Cashflowbubu

"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."

@Moemenn

"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."

@Chloe, Solo founder, LA

117

"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."

@Raaaaaachelw

"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."

@Matt, YC alum

108

"Reading used to feel like a chore. Now it’s just part of my lifestyle."

@Erin, Investment Banking Associate , NYC

254

"Feels effortless compared to reading. I’ve finished 6 books this month already."

@djmikemoore

"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."

@Pitiful

4.5K

"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."

@SofiaP

"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"

@Jaded_Falcon

201

"It is great for me to learn something from the book without reading it."

@OojasSalunke

"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."

@Leo, Law Student, UPenn

483

"Makes me feel smarter every time before going to work"

@Cashflowbubu

See more on how BeFreed is discussed

Start your learning journey, now

Chapter 11

Scrum

OverviewOverview of Scrum

One book. Many ways to hear it.

The Broken System: Why Traditional Work Methods Fail

Scrum Fundamentals: A New Framework for Work

See every word as you hear it

The Origins: From Vietnam to Revolutionary Management

The Power of Teams: Transcending Individual Capabilities

Get more out of Scrum

The Discipline of Time: Sprints and Daily Rhythm

Eliminating Waste: The Path to Flow and Excellence

See every word as you hear it

Planning Reality: How to Estimate and Deliver Reliably

The Happiness Factor: Why Joy Drives Performance

Get more out of Scrum

Strategic Prioritization: Maximizing Value Through Focus

Transforming the World: Scrum Beyond Software

See every word as you hear it

The Future of Work: Lessons from Revolutionary Organizations

Implementing Scrum: A Practical Guide to Getting Started

You made it to the end of Scrum

Key Themes in Scrum

Quotes from Scrum

Characters in Scrum

About the Author

Download Summary of Scrum

Users also liked

FAQs About This Book

What is Scrum: The Art of Doing Twice the Work in Half the Time about?

Who should read Scrum by Jeff Sutherland?

Is Scrum by Jeff Sutherland worth reading?

What are the key principles of Scrum according to Jeff Sutherland?

Part of a Learning Plan

Master Agile Scrum for Small Business

Learn Project Management for Beginners

Crescita carriera Project Manager e leader

Discover more

1,000,000+ curious minds.

1,000,000+ curious minds.

One book. Many ways to hear it.

The Broken System: Why Traditional Work Methods Fail

Scrum Fundamentals: A New Framework for Work

See every word as you hear it

The Origins: From Vietnam to Revolutionary Management

The Power of Teams: Transcending Individual Capabilities

Get more out of Scrum

The Discipline of Time: Sprints and Daily Rhythm

Eliminating Waste: The Path to Flow and Excellence

See every word as you hear it

Planning Reality: How to Estimate and Deliver Reliably

The Happiness Factor: Why Joy Drives Performance

Get more out of Scrum

Strategic Prioritization: Maximizing Value Through Focus

Transforming the World: Scrum Beyond Software

See every word as you hear it

The Future of Work: Lessons from Revolutionary Organizations

Implementing Scrum: A Practical Guide to Getting Started

You made it to the end of Scrum

Users also liked

Part of a Learning Plan

Master Agile Scrum for Small Business

Learn Project Management for Beginners

Crescita carriera Project Manager e leader

Discover more

Overview of Scrum