Industrial-Sized Deals Shop all Back to School Shop Women's Handbags Learn more nav_sap_SWP_6M_fly_beacon $5 Albums $5 Off Fire TV Stick Off to College Essentials Shop Popular Services pivdl pivdl pivdl  Amazon Echo Starting at $99 Kindle Voyage Gear Up for Football STEM Toys & Games
Agile Project Management with Scrum and over one million other books are available for Amazon Kindle. Learn more

Agile Project Management with Scrum (Developer Best Practices) 1st Edition

114 customer reviews
ISBN-13: 978-0735619937
ISBN-10: 073561993X
Why is ISBN important?
ISBN
This bar-code number lets you verify that you're getting exactly the right version or edition of a book. The 13-digit and 10-digit formats both work.
Scan an ISBN with your phone
Use the Amazon App to scan ISBNs and compare prices.
Have one to sell? Sell on Amazon
Buy used
$0.31
Buy new
$27.28
More Buying Choices
61 New from $20.27 63 Used from $0.31
Free%20Two-Day%20Shipping%20for%20College%20Students%20with%20Amazon%20Student


InterDesign Brand Store Awareness Rent Textbooks
$27.28 FREE Shipping on orders over $35. In Stock. Ships from and sold by Amazon.com. Gift-wrap available.

Frequently Bought Together

Agile Project Management with Scrum (Developer Best Practices) + Agile Software Development with Scrum (Series in Agile Software Development) + Essential Scrum: A Practical Guide to the Most Popular Agile Process (Addison-Wesley Signature Series (Cohn))
Price for all three: $90.00

Buy the selected items together

Editorial Reviews

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.

NO_CONTENT_IN_FEATURE


Best Books of the Month
Best Books of the Month
Want to know our Editors' picks for the best books of the month? Browse Best Books of the Month, featuring our favorite new books in more than a dozen categories.

Product Details

  • 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.9 inches
  • Shipping Weight: 0.3 ounces (View shipping rates and policies)
  • Average Customer Review: 4.2 out of 5 stars  See all reviews (114 customer reviews)
  • Amazon Best Sellers Rank: #54,970 in Books (See Top 100 in Books)

More About the Author

Ken Schwaber is president of Advanced Development Methods (ADM), a company dedicated to improving the software development practice. He is an experienced software developer, product manager, and industry consultant. Schwaber initiated the process management product revolution of the early 1990's and also worked with Jeff Sutherland to formulate the initial versions of the Scrum development process.

Customer Reviews

Most Helpful Customer Reviews

95 of 101 people found the following review helpful By Jim on August 21, 2009
Format: Paperback
I purchased the book hoping it would provide real content about the rules and practices of Scrum. Instead, the author appears intent upon using the book to drive business to his Scrum certification business. He touts platitudes about "the rules of Scrum", but provides little substance. Outside of the basics -- that can be learned by simply searching for "Scrum" in a search engine -- the book offers little insight into how Scrum Masters conduct themselves differently than Project Managers. If you're looking for valuable insight into Scrum, skip this book. It was a waste of my money. One last gripe: The author wastes no opportunity to slam traditional Project Managers and projects run under the procedures of non-agile methodologies. Clearly, he has never worked for a good technical Project Manager on a well-run project. Contrary to his opinion, both do exist.
6 Comments Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
39 of 43 people found the following review helpful By dugfromthearth on February 8, 2008
Format: Paperback
This book is a sales pitch for agile project management, not a book on how to use it. There is chapter after chapter with the same format. 1) describe long list of problems company has, 2) implement agile 3) magic happens. There is a small amount of information on agile and how to use it.
3 Comments Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
68 of 79 people found the following review helpful By Amazon Customer on January 24, 2005
Format: Paperback Verified Purchase
The book was an easy read and provided a fair but light treatment of Scrum. The numerous examples provide a good illustration of some of the key concepts of the method and help in better understanding implementation issues and lessons learned. This being said, a complete understanding of Scrum requires additional reading above and beyond this book, and most importantly a good solid (if not many) attempt at applying it in the real world. For individuals interested in Scrum, I would also recommend a very active discussion group to which the book's author and many other Scrum aficionados contribute regularly: [...]
1 Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
62 of 74 people found the following review helpful By VSZ on March 4, 2004
Format: Paperback Verified Purchase
Our organization recently implemented Scrum, and although the
Beedle/Schwaber book was great to get us off the ground on Scrum
theory, we immediately had many questions once we actually tried to implement it in real life projects. I agree with the notion that Scrum is conceptually easy to understand, but actually quite complex to implement correctly. The scrum forum has been helpful, but we really needed a cohesive reference of situational problems. The APMWS book really hit the nail on the head and delivered what we needed the most: a practical guide to Scrum with anecdotes and "what happens if..." situations from real world Scrum implementations. This came just in time for us, and we are feeling more confident for our upcoming certification class.
The appendices in the back are also very helpful. The "Rules"
appendix is perfect as a quick introduction to Scrum for new Team
members and Product Owners. It's actually quite detailed for being such a short appendix.
Also, for newbies the three main Roles are very nicely explained. We had some misconceptions that were immediately addressed by this book.
Anyway, from a Scrum newbie that is faced with implementation issues, thanks to Ken for putting together a real world implementation guide.
2 Comments Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
60 of 72 people found the following review helpful By Michael Cohn on February 26, 2004
Format: Paperback Verified Purchase
Agile Project Management with Scrum is a wonderful book. The author, Ken Schwaber (one of the originators of the Scrum process), informs us through case studies and anecdotes. If you like learning by example, this book is for you. Scrum is quite likely the best starting point for most companies interested in pursuing an agile development process. The readability and excellent anecdotes in this book make it a fantastic starting point for any journey into agile development.
I loved seeing how Schwaber applied Scrum in many varying situations. Rather than introducing each case study one at a time, the book is organized around key areas. Multiple anecdotes are given for each key area. Throughout each chapter, Schwaber brings the anecdotes together in Lessons Learned sections and the chapters conclude by helping point out the conclusions we learn to draw from the anecdotes.
I appreciated that Schwaber was not shy about mentioning projects that didn't go perfectly-including one he got fired from for being too zealous in his role of sheepdog guarding his flock of developers.
Although this book is ostensibly about software development, Scrum has its roots in general new product development and can (and has been) applied to a wide variety of development projects. A problem with a process like Scrum is that it is best learned by "feeling it" rather than being told about it. There are many subtle differences between Scrum and a more command-and-control management process. Learning Scrum by reading a book filled with examples like this is the best way to get the feel for how to use it on your own projects.
1 Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
20 of 24 people found the following review helpful By Michael J. Edelman TOP 100 REVIEWERVINE VOICE on June 10, 2005
Format: Paperback Verified Purchase
Reading this book won't turn you into a ScrumMaster- only experience with a few projects will do that- but this book really has all the information you need to start to implement the Scrum agile methodology in your company or department.

I've been trained in two seperate PMI-certified methodologies, and both have been complete failures in my organizations. The response, of course, has been to bring in a third methodology. The real reason for the failures has been that traditional project managment as it is usually practiced is designed to fail. It encourages the creation of fictions that live a seperate existence form the actual project, with due dates dictated from above, and project schedules fudged to meet due dates rather than actual resources. In my own organization, we had a typical example of what happens in traditional "waterfall" development: A massive project to replace our main administrative system was ticking towards a June delivery (according to the detailed MS Project charts) and then, 30 days prior to delivery, it was announced that the delivery date had been pushed back an entire year!

This can't happen with Scrum. Scrum reflects what's really happening in a project, and it encourages incremental development- prioritizing requirements, and delivering them in their order of need, instead of trying to deliver a complete project with every single componant at a certain date. It's also one of the least onerous of methodologies. As a Scrum Master friend notes, "It's the simplest methodology you can implement that will actually deliver results".

It does requrie some changes in how things are done in the traditional organizations.
Read more ›
2 Comments Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Most Recent Customer Reviews

Set up an Amazon Giveaway

Amazon Giveaway allows you to run promotional giveaways in order to create buzz, reward your audience, and attract new followers and customers. Learn more
Agile Project Management with Scrum (Developer Best Practices)
This item: Agile Project Management with Scrum (Developer Best Practices)
Price: $27.28
Ships from and sold by Amazon.com

Want to discover more products? Check out these pages to see more: scrum guide, ticket scalping, ken schwaber, epub books, product testing, planning meetings for projects