- Series: Developer Best Practices
- Paperback: 176 pages
- Publisher: Microsoft Press; 1 edition (June 23, 2007)
- Language: English
- ISBN-10: 0735623376
- ISBN-13: 978-0735623378
- Product Dimensions: 7.2 x 0.6 x 8.9 inches
- Shipping Weight: 10.4 ounces (View shipping rates and policies)
- Average Customer Review: 12 customer reviews
- Amazon Best Sellers Rank: #736,396 in Books (See Top 100 in Books)
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.
The Enterprise and Scrum (Developer Best Practices) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
From the Publisher
Key Book Benefits:
-Delivers best practices from an author with more than 20 years of experience with agile development methods
-Provides guidance about both system and interpersonal processes
-Features numerous case studies about Scrum adoption at large enterprises--including MicrosoftÂ® Corporation
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.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
-one product: a large web site
-8 scrum teams: 6 service teams, 1 IT team, 1 CM team
-scrum of scrum: team composed of senior engineers from each scrum focused on global code integration, standard / API definitions, run by uber scrum master and uber product owner
-meta scrum: team composed of local scrum masters (problem raisers) and executives (problem solvers) focused on organizational issues, run by uber scrum master
-a product delivered within a deadline of 18 weeks (the last product of similar size and complexity was delivered in 18 months and was mostly unsuccessful)
-a very happy product owner (financial outcome better than expected, all key features delivered)
-best quality software ever written in the company (best as from a technical debt perspective, and great architecture paradigm)
-fantastic morale in the team
This book is written for people that understand scrum and are ready to think it to the next level. It clearly outlines a simple and powerful framework to roll out scrum across the enterprise and achieve great coordination in scalable manner in large projects. This is not an "enterprise scrum". It is the same scrum applied to the enterprise.
Some might miss details on tactical implementation which the book doesn't try to address. Why? I think because it is scrum and details have been written about over and over. So how do you attack your big impediments? Run Ken's framework and let it to the self-organization of the teams! It is scrum after all.
Too many agile books suffer from being targeted at a single team working on a deserted island--that is, a seven-person team with no issues outside their one team. This book does not suffer from that problem. Want to know how to organize work on a project that is partitioned by architectural layer? How to structure a product backlog for the entire organization? Or how to organize teams across a large project? Or what are the proper reporting relationships on a large Scrum project? This book provides sage advice on these enterprise adoption issues and more.
The book is chock-full of real-life anecdotes (in which only the name of the company and key players have been changed). Each anecdote illustrates how one real company dealt with a real problem. Their problem, their context, and their solution won't exactly be yours, but seeing how others have addressed challenges can be illuminating in thinking how to address yours.
This is probably not your best choice as a first book on Scrum. For that start with the author's other two books. This book picks up where they left off, providing a wealth of information for enterprises and even workgroups adopting Scrum. If you're already familiar with the basics of Scrum, and especially if you are starting to hit the hard points of adopting it and spreading it through your organization then this book is for you.
Before I further comment about that let me first take a guess about why people want to read a technical book. I think most people want to read a technical book because they hope the book can teach them something new. And if the reading process makes readers entertained that will make the book even more valuable. And that was what I got from "Agile Project Management With Scrum". But technical reading mostly does not get that luxury so long as the book is informative (and enlightened) we will say the time and energy spent for it is well worth.
So back to this book, I think before reading it every one will know that running scrum in a traditional waterfall process company is hard. What we want to know is how hard that it is. What kind of (typical) situation we may run into; what kind of specific issue we need to address and what was the author's way or suggestion to tackle them. But the author just kept saying that it is hard but you got to stick with scrum then finally you will make it. The author kept repeating that without even giving a valuable suggestion for it (putting the obstacles into transition backlog can't really be counted as a valuable suggestion). And the examples he gave were also superficial, i.e. repeating that you will make it finally without giving any valuable suggestion about how.
The second part of the book is about the practice using in the enterprise. But except for suggesting the use of scrum of scrum, which again readers will anticipate before reading the book and checking your burn down chart to know your productivity I still do not see any thing new or enlightened, although the example the author gave here were a little bit more impressive than the examples gave in the first part.
The third part of the book was the worst. The third part is about the introduction of scrum, the kind of materials you can find all over the internet. I even found that the author copies pasted some of paragraphs in his previous book "Agile Project Management With Scrum".
I do not mean to be harsh and the author is really some person I look up to. So maybe he was talking about something totally beyond my level and I hope anyone can point that out for me.
Most recent customer reviews
-that there are no cookbooks...Read more
* Part I is titled "Adopting Scrum" and provides an excellent outline of a scalable process for transitioning to Scrum along...Read more