
Transform your organization beyond tech with "The Scrum Fieldbook." From Toyota to Google, J.J. Sutherland's methodology has revolutionized diverse industries. Even U.S. General Barry McCaffrey calls it "mandatory reading for any leader." What could your team accomplish in half the time?
J.J. Sutherland, CEO of Scrum Inc. and bestselling author of The Scrum Fieldbook, is a leading authority in Agile methodologies and organizational transformation. A former award-winning NPR correspondent who covered conflicts across the Middle East, Sutherland brings firsthand experience managing high-stakes challenges to his practical guides on adaptive leadership. His work bridges agile principles with real-world execution, drawing from his collaborations with Fortune 100 companies, the U.S. Navy, and global enterprises.
Sutherland co-authored the foundational Scrum: The Art of Doing Twice the Work in Half the Time, a global phenomenon that has sold over one million copies and redefined productivity frameworks. The Scrum Fieldbook expands these concepts, offering actionable strategies for teams navigating rapid change. As head of Scrum Inc., he oversees enterprise transformations while advocating for scalable, human-centric workflows. His insights have been featured in The Wall Street Journal, TED Talks, and industry-leading podcasts, cementing his role as a trusted voice in modern management.
The Scrum Fieldbook is a practical guide to implementing Scrum methodologies in real-world projects, offering actionable strategies for agile teams. J.J. Sutherland, son of Scrum co-creator Jeff Sutherland, explains how to customize Scrum processes, manage backlogs and sprints, and build high-performing teams. The book includes case studies from companies like Google and Amazon, illustrating Scrum’s adaptability across industries.
This book is ideal for Scrum Masters, Product Owners, and team leaders seeking to optimize agile workflows. It’s also valuable for organizations transitioning to Scrum, offering solutions for overcoming resistance to change, refining stakeholder communication, and scaling Scrum for complex projects.
Yes, for its blend of theoretical frameworks and real-world applications. Sutherland provides step-by-step guidance on sprint planning, backlog prioritization, and fostering a culture of continuous improvement. The inclusion of case studies and troubleshooting tips makes it a resource for both beginners and experienced practitioners.
While Jeff Sutherland’s Scrum introduces foundational principles, The Scrum Fieldbook focuses on practical implementation. J.J. Sutherland emphasizes customization for diverse teams, addressing challenges like distributed workflows and stakeholder alignment. It also expands on advanced concepts like Scaling Scrum and Nexus frameworks.
Sutherland outlines three core roles:
The book stresses collaboration and adaptability to ensure these roles function cohesively.
It advocates for dynamic prioritization, breaking large projects into smaller tasks, and maintaining stakeholder transparency. Sutherland emphasizes refining backlogs iteratively to reflect changing priorities, ensuring teams focus on high-value deliverables.
Key strategies include setting clear sprint goals, conducting daily stand-ups for progress tracking, and using retrospectives for continuous improvement. Sutherland highlights the importance of adaptability when facing unexpected challenges during sprints.
It introduces frameworks like Scrum of Scrums and Nexus to coordinate multiple teams. Sutherland advises aligning cross-team priorities, maintaining consistent communication, and using shared metrics to manage dependencies in complex projects.
Sutherland challenges the myth that Scrum is a “one-size-fits-all” solution. He clarifies that Scrum requires customization, balances speed with sustainability, and thrives in cultures valuing transparency and incremental change—not just rigid adherence to rituals.
It recommends involving stakeholders in sprint reviews, using artifacts like product backlogs for transparency, and aligning expectations through frequent feedback loops. Sutherland stresses the Product Owner’s role as a liaison between teams and stakeholders.
The book features examples from tech giants like Google and Amazon, demonstrating Scrum’s application in software development, product launches, and organizational restructuring. These case studies highlight iterative success, failure analysis, and process refinement.
Sutherland advocates for education, incremental adoption, and showcasing early wins to build buy-in. He emphasizes leadership support and creating psychological safety to ease teams into agile practices.
Senti il libro attraverso la voce dell'autore
Trasforma la conoscenza in spunti coinvolgenti e ricchi di esempi
Cattura le idee chiave in un lampo per un apprendimento veloce
Goditi il libro in modo divertente e coinvolgente
Scrum fundamentally reduces the cost of changing your mind.
Plans are worthless, but planning is everything.
Scrum embraces change rather than fighting it.
Scrum enables organizations to respond nimbly to unpredictable change.
Scomponi le idee chiave di The Scrum Fieldbook in punti facili da capire per comprendere come i team innovativi creano, collaborano e crescono.
Vivi The Scrum Fieldbook attraverso narrazioni vivide che trasformano le lezioni di innovazione in momenti che ricorderai e applicherai.
Chiedi qualsiasi cosa, scegli il tuo stile di apprendimento e co-crea intuizioni che risuonano davvero con te.

Creato da alumni della Columbia University a San Francisco
"Instead of endless scrolling, I just hit play on BeFreed. It saves me so much time."
"I never knew where to start with nonfiction—BeFreed’s book lists turned into podcasts gave me a clear path."
"Perfect balance between learning and entertainment. Finished ‘Thinking, Fast and Slow’ on my commute this week."
"Crazy how much I learned while walking the dog. BeFreed = small habits → big gains."
"Reading used to feel like a chore. Now it’s just part of my lifestyle."
"Feels effortless compared to reading. I’ve finished 6 books this month already."
"BeFreed turned my guilty doomscrolling into something that feels productive and inspiring."
"BeFreed turned my commute into learning time. 20-min podcasts are perfect for finishing books I never had time for."
"BeFreed replaced my podcast queue. Imagine Spotify for books — that’s it. 🙌"
"It is great for me to learn something from the book without reading it."
"The themed book list podcasts help me connect ideas across authors—like a guided audio journey."
"Makes me feel smarter every time before going to work"
Creato da alumni della Columbia University a San Francisco

Ottieni il riassunto di The Scrum Fieldbook in formato PDF o EPUB gratuito. Stampalo o leggilo offline quando vuoi.
Imagine a world where fighter jets are built like Lego sets, restaurant staff share profits without managers, and companies deliver twice the work in half the time. This isn't fantasy - it's the reality for organizations embracing Scrum. In an era where technology doubles in power every two years while halving in cost, traditional business structures are crumbling under exponential change. The framework that began in software development has sparked nothing short of a business revolution, transforming everything from healthcare to banking to military operations. When managers claim their work is "too complex for Scrum," they're quickly reminded: "Whatever you're building isn't more complicated than a fighter plane." Sweden's Saab proved this by using Scrum to develop their Gripen E fighter - a modular aircraft with superior capabilities at half the operating cost of competitors. The true power of Scrum lies in its ability to reduce the cost of changing your mind. Whether you're flipping houses in Minneapolis or integrating billion-dollar corporate acquisitions, the framework follows a simple 3-5-3 structure: three roles (Product Owner, Scrum Master, Team Member), five events (Sprint Planning, Sprint, Daily Scrum, Review, Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment). This structure creates a rhythm where work is broken into short cycles called Sprints, typically lasting 1-4 weeks, with each Sprint delivering something potentially usable. The Standish Group reports that 67% of requirements change during development because people learn as they build. Rather than fighting this inevitable change through bureaucracy and documentation, Scrum embraces it.
Decision latency-the gap between recognizing a decision need and making it-silently kills projects. Research shows projects with decisions made in under an hour succeed 58% of the time, while those taking over five hours succeed only 18%. Most organizations create delays through hierarchical approvals. Navy Commander Jon Haase demonstrated the alternative when implementing Scrum in Explosive Ordnance Disposal, boosting productivity by 1,250% through timeboxed events with clear objectives. Complex problems are best solved at what Christopher Langton called the "edge of chaos"-where rules are neither too rigid nor too loose. As Eisenhower noted, "Plans are worthless, but planning is everything" because emergencies never unfold as expected. The word "priority" originated meaning precedence-linguistically, "priorities" is contradictory, like claiming multiple first-place finishers. Yet this term became common around 1940. The consequences are severe: Scrum Inc. typically finds 30% of work actively opposes business goals, while 64% of remaining work creates rarely-used features. This means 75% of employees work on the wrong things. One global materials company had over 100 projects in progress without enough staff for even 70. By reducing to just 12 focused projects, they doubled productivity in ten weeks and cut their 2.5-year development cycle to six weeks. The root cause of prioritization problems is an unwillingness to say no, creating a culture where "everything is the number one priority"-revealing a profound misunderstanding of what priority means.
Have you ever wondered why smart people in organizations do things they know don't work? Fear drives seemingly irrational behaviors. At a major automaker, I witnessed organizational insanity where status derived from distance from actual work. Two hundred people spent five years and $75 million on a dealer incentives project with nothing to show. Only twenty-five people were doing actual work; the rest were managers managing managers. After implementing Scrum, we cut 175 people and delivered a working product within months. MIT professor Otto Scharmer identifies three inner voices driving dysfunction: The Voice of Judgment filters information through existing worldviews, the Voice of Cynicism protects us emotionally, and the Voice of Fear makes us afraid to fail. W. Edwards Deming advocated "Drive out fear" because it produces wrong data and destroys motivation. When restaurant owner Riccardo Mariti eliminated hierarchy and created a flat organization with profit-sharing, he discovered a fundamental truth: structure determines culture, and culture defines limits. Conway's law states that organizations produce designs mirroring their communication structures - if your organization is rigid and hierarchical, your product will be too. The five Scrum values - Commitment, Focus, Openness, Respect, and Courage - create energetic workplaces. At Colombia's Drummond Company, consultant Fabian Schwartz formed a cross-functional Scrum Team of senior leaders who met daily for fifteen minutes. This improved communication reduced well drilling time from nineteen days to just six days by changing only how they worked together.
What makes some teams four times more productive than others? OpenView Venture Partners found that teams finishing sprints early accelerated faster than those working until the last minute. The latter maintained consistent velocity but never achieved the fourfold productivity improvement Scrum aims for. The insight: Scrum isn't about velocity - it's about acceleration. Teams that finish early have time to improve and get faster. Four critical patterns emerge for hyperproductive teams: First, stability - teams that stay together develop shared mental models and transactive memory, anticipating each other's needs. Data shows members dedicated to a single team are nearly twice as productive as those split across multiple teams. Second, "Yesterday's Weather" - teams should only commit to the amount of work they completed in previous Sprints, using a three-Sprint average. Third, "Swarming" - focusing entirely on completing the most important backlog item before moving to the next, like a synchronized Formula One pit crew. Fourth, maintaining an "Interrupt Buffer" - reserving capacity for emergencies while protecting the team from disruption. At Red River Army Depot, these patterns helped revolutionize Humvee repair, increasing production from three vehicles per week to forty per day - a 6,600% improvement.
Tom Auld, a Minneapolis house flipper, manages contractors using Scrum boards with "To Do," "Doing," and "Done" columns. His weekly reviews allow for payment of completed work and adaptation to unexpected issues like raccoons in walls or wiring problems. When adopting Scrum, management styles must evolve too. At Riccardo's restaurant, the owner stopped solving problems directly and instead empowered staff to make decisions. This reduced customer issue response time by 70% while increasing profitability and workplace satisfaction. Denmark demonstrates Scrum's broader impact. After Carsten Jakobsen implemented it at Systematic in 2006, teams doubled their productivity, reduced defects by 41%, and improved both customer and employee satisfaction. These results were so compelling that Scrum is now taught at all Danish universities as critical for economic competitiveness.
Like John Snow's epidemiological breakthrough challenging miasma theory in 1840s London, Scrum has emerged from observed success patterns across thousands of projects. Yet resistance persists as people cling to traditional methods despite evidence favoring better alternatives. Scrum's power lies in creating structures that fulfill essential psychological needs: purpose, meaning, security, and self-worth through defined roles and expectations. This framework transcends cultural and linguistic boundaries by addressing fundamental human needs. In our rapidly changing world, organizations can either become paralyzed or liberated to achieve extraordinary results. The tools and path exist to transform not just our work methods but our collective sense of what's possible. With change accelerating exponentially, the real question isn't whether you can afford to adopt Scrum, but whether you can afford not to.