- Series: Developer Best Practices
- Paperback: 192 pages
- Publisher: Microsoft Press; 1 edition (February 21, 2004)
- Language: English
- ISBN-10: 073561993X
- ISBN-13: 978-0735619937
- Product Dimensions: 7.3 x 0.6 x 8.8 inches
- Shipping Weight: 11.7 ounces (View shipping rates and policies)
- Average Customer Review: 4.2 out of 5 stars See all reviews (126 customer reviews)
Amazon Best Sellers Rank:
#203,470 in Books (See Top 100 in Books)
- #49 in Books > Business & Money > Management & Leadership > Quality Control & Management > Agile
- #51 in Books > Computers & Technology > Business Technology > Software > Project Management Software
- #77 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Testing
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Agile Project Management with Scrum (Developer Best Practices) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Frequently bought together
Customers who bought this item also bought
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.
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top Customer Reviews
The Kindle edition I purchased was well produced with no production problems. The author has long experience of both Agile and Scrum in Software development. It may be interesting to read with Adkins on Coaching Agile Teams.
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.
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.