MinuteRead
30 min
Loading…
Book summary
by Ken Schwaber
Premium summary · Opens in the app · 30 min read
Software development has a problem. For decades, organizations have approached complex projects with tools designed for simple, predictable work. They create detailed plans, define exhaustive requirements, and then attempt to execute those plans with military precision. The result is almost always the same: projects run late, budgets explode, and the final product disappoints the people who asked for it.
**Author:** Ken Schwaber
**Estimated Reading Time:** 45 minutes
**What You'll Learn:** How Scrum transforms chaotic, complex projects into manageable, iterative work that delivers real value. You will understand the roles, events, artifacts, and rules that make Scrum work, and you will learn how to apply empirical process control to projects where uncertainty is the only certainty.
**Who This Book Is For:** Project managers, software developers, team leads, executives, and anyone who has ever watched a project spiral out of control despite detailed plans and rigorous documentation. If you have felt the frustration of delivering late, over budget, or the wrong product entirely, this book is for you.
Software development has a problem. For decades, organizations have approached complex projects with tools designed for simple, predictable work. They create detailed plans, define exhaustive requirements, and then attempt to execute those plans with military precision. The result is almost always the same: projects run late, budgets explode, and the final product disappoints the people who asked for it. The problem is not laziness or incompetence. The problem is that complex work does not behave like simple work. When you build a bridge, you can calculate the load, specify the materials, and predict the construction timeline with reasonable accuracy. When you build software, you are navigating territory that has never been explored before. Requirements shift as users discover what they actually need. Technologies evolve mid-project. Competitors change the landscape. The very act of building the product reveals new possibilities and new constraints. Traditional project management treats these changes as failures to be prevented. Scrum treats them as reality to be embraced. Ken Schwaber, co-creator of Scrum, wrote this book to address a fundamental mismatch. Organizations were trying to manage complex, unpredictable work with tools designed for simple, predictable work. They were using Gantt charts to map unknown territory. They were writing requirement documents that pretended certainty where none existed. They were measuring progress by counting documents produced rather than value delivered. Schwaber's insight was radical in its simplicity: stop pretending you can predict the unpredictable. Instead, build a framework that allows you to inspect reality frequently and adapt quickly. Create short cycles of work, deliver something usable at the end of each cycle, and use what you learn to guide the next cycle. This book introduces Scrum, a framework for managing complex projects through empirical process control. Scrum is not a methodology in the traditional sense. It does not prescribe every step, every document, every role. Instead, it provides a simple structure within which teams can manage themselves, inspect their progress, and adapt their approach continuously. The book draws on Schwaber's extensive experience implementing Scrum in organizations of all sizes. He has seen…
Continue reading in the MinuteRead app
Get the complete 30-minute summary of Agile Project Management with Scrum
Get the complete summary in the appScrum is based on empirical process control: transparency, inspection, and adaptation.
The three roles are Product Owner, ScrumMaster, and Development Team.
The Sprint is a time-boxed period of two to four weeks that ends with a potentially shippable product increment.
The Product Backlog is a living, prioritized list of everything that might be included in the product.
The Daily Scrum is a fifteen-minute daily planning meeting where each team member answers three questions.
The Sprint Review focuses on the product. The Sprint Retrospective focuses on the process.
"Agile Project Management with Scrum" is a strong fit if you want practical ideas around business, management, technology, especially themes like scrum is based on empirical process control: transparency, inspection, and adaptation; the three roles are product owner, scrummaster, and development team. The MinuteRead summary distills these concepts into a focused read, whether you're deciding whether to buy the book or applying its lessons at work.
Motivated to help readers with 1) Scrum: An Agile Framework for Complex Project Management 2) The Scrum Team: Roles and Responsibilities 3), Ken Schwaber wrote “Agile Project Management with Scrum” to package those ideas for a fast, focused read. In “Agile Project Management with Scrum”, Ken Schwaber focuses on 1) Scrum: An Agile Framework for Complex Project Management 2) The Scrum Team: Roles and Responsibilities 3). Through “Agile Project Management with Scrum”, Ken Schwaber distills the core…
Continue Reading
Access the complete 30-minute summary and thousands more nonfiction books in the MinuteRead app.
Continue reading the complete summary in the MinuteRead app.
