from Jeff Sutherland
Scrum by Jeff Sutherland is the book that brought to the general public the work framework that revolutionized not only software development but the way any complex project is managed. Sutherland, co-creator of Scrum and a Vietnam combat pilot, blends neuroscience, military experience, and decades of consulting to demonstrate that small, self-organizing teams focused on short cycles can achieve results that traditional project management methods never reach. It is not a technical book: it is a manifesto about how human work should function.
“Scrum embraces the fact that the development process is unpredictable. The product is the best possible artifact at any given point in time.” — Jeff Sutherland
BOOK SUMMARY
Sutherland structures the book around Scrum’s principles and mechanics, explaining them with real stories ranging from the FBI to robot teams:
Sprints: Short work cycles (1 to 4 weeks) where a team commits to delivering a functional increment of the product. At the end of each sprint, there is something finished and demonstrable. This eliminates the illusion of progress in Gantt-chart timelines and forces tangible results constantly.
Small, cross-functional teams: Sutherland demonstrates that teams of 3 to 9 people consistently outperform large teams. The key is that the team has all necessary skills to deliver without depending on other departments, eliminating bureaucratic bottlenecks.
Product Backlog and prioritization: An ordered list of everything the product needs, prioritized by customer value. The Product Owner decides what gets done first based on impact, not whims. This ensures the team always works on the most important thing.
Retrospectives: At the end of each sprint, the team asks: what did we do well? What can we improve? This continuous improvement ritual is, for Sutherland, the heart of Scrum. Teams that don’t do honest retrospectives stop improving.
Velocity and story points: Instead of estimating in hours (which are always lies), Scrum uses relative complexity points. Over time, the team discovers its real velocity and can accurately predict how much work it can deliver per sprint.
Sutherland dedicates entire chapters to explaining why traditional project management methods (waterfall, detailed 18-month timelines, hierarchical controls) are not only inefficient but dangerous. The FBI case, which spent hundreds of millions of dollars on a system that never worked using traditional methods and then rebuilt it in months with Scrum, is devastating.
WHY I RECOMMEND READING THIS BOOK? By Francisco Santolo
Scrum is not just for software teams. It is for any team that needs to deliver results in environments of uncertainty, which is basically any team in the real world. When we started applying short cycles and retrospectives to projects that had nothing to do with technology, the results were immediate: more focus, less waste, and a transparency that changed team dynamics.
What impacted me most was the radical simplicity of the framework. Scrum has only three roles, five events, and three artifacts. It all fits on one page. But that simplicity is deceptive: implementing it well requires discipline, honesty, and a willingness to change deep habits about how we manage work.
That said, I am very critical of how large consulting firms have implemented Agile. Many now call it Agile Washing: Scrum has been overused as a synonym for Agile, while forgetting to apply the business methodologies associated with agility —such as Customer Development, Lean Startup, Design Thinking, and continuous market validation. Reducing “being agile” to running sprints and daily meetings empties a movement that was born to transform how products and companies are created. Scrum itself is a superb productivity tool, but it must be used within the framework of agile values and principles, which are what matters most.
I was also struck by the FBI case. It is the perfect demonstration that throwing more money, more people, and more time at a poorly managed project doesn’t fix it, it makes it worse. And that a small team with the right method can accomplish in months what a bureaucratic army couldn’t achieve in years. That resonates deeply with the reality of any venture.
Sutherland has a unique background —combat pilot, academic, entrepreneur— and it shows in how he writes: direct, no detours, with hard data and concrete examples. It’s not a motivational book, it’s a book about engineering applied to human teams.
Read it if you feel your team works a lot but achieves little. You probably don’t have an effort problem but a method problem. But remember: Scrum without the agile principles behind it is just an empty shell.
RELATED BOOKS
• The Lean Startup — Eric Ries combines Scrum with Customer Development to create a complete startup-building framework. If Scrum is the how to work, Lean Startup is the what to build.
• Learning Agile — Andrew Stellman and Jennifer Greene offer a comparative guide to all agile frameworks (Scrum, XP, Lean, Kanban), ideal for understanding where each one fits.
• Rework — Jason Fried and David Heinemeier Hansson share Scrum’s underlying philosophy —less is more, focus over volume— applied to building companies without bureaucracy.