Agile Software Development with SCRUM Paperback – Illustrated, 25 Feb. 2002

The classic book on Agile and Scrum. It’s a pleasingly thin book which picks in the content. Easy to read and easy to follow. It can be a little dry in places but overall it’s a great book.

Excellent book for those wanting to learn the concepts of Scrum, had a profound effect on improving business processes for my software development team. Easy to read with great stories

This was one of the first books published on Agile software techniques, and is in some ways showing its age. The quality of the diagrams is poor (although they are still perfectly understandable), and Scrum in its original form has been superseded by a variety of other techniques.But these other techniques might never have existed had it not been for Scrum, and the software development principles embodied in this book are still core to the whole ethos of Agile processes. For those reasons, this is still a key book that should be read and understood by anyone working in software development today, particularly anyone with people or project management responsibilities.Schwaber and Beedle's book is quite short and easy to read: both of which are to its benefit. That Scrum is simple enough to be described so succinctly is one of the main reasons why it works as a process, and achieved rapid widespread adoption. This is the book that introduced Scrum to the world, and more than ten years later is probably still the best introduction to the topic.Note that Scrum focuses on the project management aspects of software development. If you're looking for information on the more technical development activities, other books will serve you better; for example Kent Beck's "Extreme Programming Explained" (which again is a few years old, but still excellent).

Great book, fantastic for scrum masters....but extreme programming it does not tackle!completely mislabeled.5 stars because the content more than makes up for it!

We decided to look at Scrum after deciding agile was the way forward but failed to implement a decent framework around it. Scrum is a very straightforward and lightweight project management framework and this book gets the principles across succinctly. I was able to pass this book over to our COO (a non-technie) and he read it and has embraced it too - between us we've been practising Scrum since, so far with good success. Following this I highly recommend you read Agile Estimating and Planning by Mike Cohn

Content great. Paper quality not so much. The pages of the book are so thin as if printed on recycled toilet paper.

This book explains some very useful methods for delivering customer-focused solutions. Aside from a new set of terminology to get used to, the book cites the usefulness of: fast daily status meetings ("Scrums"), 'locked' 30-day iterations ("Sprints") that deliver working code at the end, small teams of 6-8 multi-skilled people, a prioritised book of work that is re-appraised every 30 days ("Backlog"), regular assessment of the work effort in the backlog rather than using a project plan, collective responsibility for delivery. I have seen people use these methods in successful projects within my company but they didn't know they were using Scrum, they were just doing things that they felt were right, have worked for them in the past and enabled them to focus on driving out a solution that would meet the real needs of the users.

Covers what you need to know about Scrum.