Agile Project Management with Scrum (Developer Best Practices) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
The rules and practices for Scrum―a simple process for managing complex projects―are few, straightforward, and easy to learn. But Scrum’s simplicity itself―its lack of prescription―can be disarming, and new practitioners often find themselves reverting to old project management habits and tools and yielding lesser results. In this illuminating series of case studies, Scrum co-creator and evangelist Ken Schwaber identifies the real-world lessons―the successes and failures―culled from his years of experience coaching companies in agile project management. Through them, you’ll understand how to use Scrum to solve complex problems and drive better results―delivering more valuable software faster.
Gain the foundation in Scrum theory―and practice―you need to:
- Rein in even the most complex, unwieldy projects
- Effectively manage unknown or changing product requirements
- Simplify the chain of command with self-managing development teams
- Receive clearer specifications―and feedback―from customers
- Greatly reduce project planning time and required tools
- Build―and release―products in 30-day cycles so clients get deliverables earlier
- Avoid missteps by regularly inspecting, reporting on, and fine-tuning projects
- Support multiple teams working on a large-scale project from many geographic locations
- Maximize return on investment!
From the Publisher
|A Practical Guide to the Most Popular Agile Process||Agile Advice for Your First Year and Beyond||The Fast, Focused, Practical Guide to Excellence with Scrum||Real World Lessons in Scrum||Proven, 100% Practical Guidance for Making Scrum and Agile Work in Any Organization|
|Title||Essential Srum||The Scrum Field Guide||The Great ScrumMaster||Agile Project Management with Scrum||Succeeding with Agile|
|Author||Kenneth Rubin||Mitch Lacey||Zuzana Sochova||Ken Schwaber||Mike Cohn|
|Description||Leading Scrum coach and trainer Kenny Rubin provides easy-to-digest descriptions enhanced by illustrations based on an entirely new visual icon language for describing Scrum’s roles, artifacts, and activities.||Drawing on years of hands-on experience helping companies succeed, Certified Scrum Trainer (CST) Mitch Lacey helps you overcome the major challenges of Scrum adoption and the deeper issues that emerge later.||Complete guide to becoming an exceptionally effective ScrumMaster and using Scrum to dramatically improve team and organizational performance. Easy to digest and highly visual, you can read it in a weekend…and use it for an entire career.||In this illuminating series of case studies, Scrum co-creator and evangelist Ken Schwaber identifies the real-world lessons—the successes and failures—culled from his years of experience coaching companies in agile project management.||This is the definitive, realistic, actionable guide to starting fast with Scrum and agile–and then succeeding over the long haul. Leading agile consultant and practitioner Mike Cohn presents detailed recommendations, powerful tips, and real-world case studies drawn from his unparalleled experience helping hundreds of software organizations make Scrum and agile work.|
|Endorsement||"This book serves as an indispensable guide, helping teams choose among the billions of possible ways of implementing Scrum and finding one that leads to success." — Mike Cohn, author of "Succeeding with Agile", Certified Scrum Trainer||"I am happy to say that I can definitely recommend Mitch’s book! I am confident that you will find my book and this book to be good compliments to one another, even (and especially) where the two differ on particular issues or approaches." -- Kenneth Rubin, author of "Essential Scrum"||"The Great ScrumMaster: #ScrumMasterWay fills an important gap in providing practical advice and tools for ScrumMasters who wish to improve their craft. The book is full of powerful tips sure to help any ScrumMaster." — Mike Cohn, author of "Succeeding with Agile", Certified Scrum Trainer||"This book is an excellent guide for anyone looking to improve how he or she delivers software, and I recommend it highly." — Mike Cohn, author of "Succeeding with Agile", Certified Scrum Trainer||"By reading this book, you will find that Mike brings up issues that you never thought of, offers advice on how you might handle situations, and helps you define new roles on your team." -- Tim Lister, Principal, The Atlantic Systems Guild, Inc|
About the Author
A 30-year veteran of the software development industry, Ken Schwaber is a leader of the agile process revolution and one of the developers of the Scrum process. A signatory of the Agile Manifesto in 2001, he subsequently founded the Agile Alliance and the Scrum Alliance. Ken authored Agile Project Management with Scrum and coauthored Agile Software Development with Scrum and has helped train more than 47,000 certified ScrumMasters.
- Publisher : Microsoft Press; 1st edition (February 11, 2004)
- Language : English
- Paperback : 192 pages
- ISBN-10 : 073561993X
- ISBN-13 : 978-0735619937
- Item Weight : 11.5 ounces
- Dimensions : 7.4 x 0.8 x 9 inches
- Best Sellers Rank: #380,275 in Books (See Top 100 in Books)
- Customer Reviews:
About the author
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
The book's laid out in a series of stories which illustrate responsibilities and typical problems to overcome for the Scrum roles of Product Owner, ScrumMaster, and Team. The stories are short, concise, and followed up by Lessons Learned which cover salient highlights for the various points made in the section. Throughout the book runs Schwaber's theme of how one can use Scrum to solve any number of problems and increase the productivity of their development work.
What's really nice about the book is that there are stories of failures as well as successes. Software development is rarely all roses, so it's nice to see a couple examples where things didn't work -- and a solid analysis of what went wrong in those cases.
On the flipside, I'd have liked a bit more detail on constructing the sprint and product backlogs. I realize that traipses somewhat over into the realm of software estimation, but more fleshing out would have been helpful. However, there's a great example of scaling Scrum and rolling up numerous product backlogs from lower levels in to a larger backlog for a major system, so that's quite beneficial.
The book's terrifically well-written, is an easy read, and is formatted such that you're able to quickly pick up the important bits of Scrum. It's a terrific read for anyone looking to bring some sensible, tailorable processes to their software development efforts.
I do think it has become somewhat hard for Schwaber to imagine what it is like NOT to be familar with Scrum, as it is so deeply embedded in his thinking and practice! For instance, he uses the term "sashimi" early on without bothering to define it in Scrum terms - that comes later (Hence the 4 stars instead of 5. Would really like to give 4 1/2.)
His other book "Agile Software Development with SCRUM" has more in-depth coverage of the subject. It includes a fuller account of the essential difference between defined and empirical processes which is at the heart of Scrum and other agile methods. In this one, he does include the same reference to the (hard to find!) industrial engineering textbook that explains this, but in a more offhand way - just quoting a key paragraph a couple of times.
Perhaps the best sequence of reading depends on your role. If, like me, you are a developer, the first book is, I think, more rewarding for in-depth study and relationship to Agile principles in general, while this one is a good follow-up on implementation realities. For a manager wondering whether Scrum deserves exploring, this book will give a strong (positive) answer to that question, and can be followed by more in-depth study with the other book.
This is a good second book. It attends less to the basics of running the team and working with the customers and corporate surroundings, although Schwaber does present all those basics. Instead, the focus is on case studies, especially ones that look like bad matches to Scrum management style. I like that emphasis: typical methodology books assume perfect compliance with fragile or rare prerequisite assumptions, then wash their hands of any circumstance that doesn't meet their delicate needs. This is a good bit more realistic - it's about the whole concept of cut-and-fit to get the most out of Scrum despite unfavorable situations and stakeholders.
Late in the book, Schwaber makes the point that people will do whatever they're rewarded for. However obvious this sounds, it's an ongoing source of corporate inanity. Suppose that percent of the code covered in testing is a major goal: programmers will dutifully eliminate handling of exceptional conditions or invalid preconditions for which tests are hard to generate (NOT an improvement). Suppose reduced development time is rewarded: watch testing time plummet and bug counts soar. I agree that progress must be measurable, and agree at the top of my lungs that the wrong measurements are worse than none at all.
Still, one theme comes through again and again: that, when the going gets weird, typical practitioners will rapidly find themselves in way over their heads. He, with more experience than any other Scrumster around, exerts the limits of his creativity to get past problems of fairly ordinary kinds (like intrasigent management). It's certainly a good recommendation for his consulting services. It's just not a message that a novice wants to hear. I have the strongest reservations about his fondness for bullpen office environments, as well.
There's good to be had here, I'm sure, but I'd have to see Scrum in action before I could really internalize the way it's meant to work.
PS: It's just an amusing typo, not a deliberate act that "the ... team was going to use Scum [sic]," p.64
Top reviews from other countries
What was interesting was Ken's own admissions of times something failed : those lessons remain relevent and are still valuable cautionary tales.