Programming Books C Java PHP Python Learn more Browse Programming Books
Qty:1
  • List Price: $39.99
  • Save: $12.49 (31%)
FREE Shipping on orders over $35.
In Stock.
Ships from and sold by Amazon.com.
Gift-wrap available.
FREE Shipping on orders over $35.
Used: Very Good | Details
Condition: Used: Very Good
Comment: Pages are clean with no markings. Ships direct from Amazon!
Access codes and supplements are not guaranteed with used items.
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

The Enterprise and Scrum (Developer Best Practices) Paperback – June 23, 2007

ISBN-13: 978-0735623378 ISBN-10: 0735623376 Edition: 1st

Buy New
Price: $27.50
27 New from $18.00 27 Used from $0.03
Amazon Price New from Used from
Kindle
"Please retry"
Paperback
"Please retry"
$27.50
$18.00 $0.03
Unknown Binding
"Please retry"
Best%20Books%20of%202014

Frequently Bought Together

The Enterprise and Scrum (Developer Best Practices) + Agile Project Management with Scrum (Developer Best Practices) + Agile Software Development with Scrum (Series in Agile Software Development)
Price for all three: $91.22

Buy the selected items together
NO_CONTENT_IN_FEATURE

Shop the new tech.book(store)
New! Introducing the tech.book(store), a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry. > Shop now

Product Details

  • 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.3 x 0.7 x 8.9 inches
  • Shipping Weight: 10.4 ounces (View shipping rates and policies)
  • Average Customer Review: 3.5 out of 5 stars  See all reviews (11 customer reviews)
  • Amazon Best Sellers Rank: #1,093,736 in Books (See Top 100 in Books)

Editorial Reviews

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.


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

The rest of the book poses problems and tells you what you need to do, but rarely tells you how to do it.
a reader
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.
Chris Louvion
Although the book is about the "enterprise and Scrum" most of the contents will be applicable to any group of teams transitioning to Scrum.
Michael Cohn

Most Helpful Customer Reviews

75 of 83 people found the following review helpful By a reader on July 14, 2007
Format: Paperback Verified Purchase
I read this book based on Mike Cohn's recommendation. However, I was extremely disappointed in it.

The book starts out telling you what to do to manage Scrum throughout an enterprise. The only problem is the approach given assumes the entire enterprise has embraced using Scrum. I have never seen this. The real problem is typically getting the enterprise to embrace Scrum. The book gives little insight in how to do this. Integrating processes across teams and how to get organizations that work in competition with each other now to cooperate is pretty much ignored.

The rest of the book poses problems and tells you what you need to do, but rarely tells you how to do it. Most often, we are simply told to let the team figure it out. Sort of like a financial analyst telling you - "what you have to do is figure out how to buy stocks when they are low, and then sell them when the stocks go higher." Uh, OK, but _how_ do I do that? The book doesn't quite ever tell us.

The book also tells us about how the core of a system can become dead and tells us we have to stop this. But how? No advice is given on how to write tests or quality code or how to do integration across an Enterprise. In fact, almost nothing about writing code exists in the book. It's as if by following process entirely we can solve all of our problems with code quality, tests, integration, etc ...

My experience with Scrum teams and management is that you must give them reasons to expand Scrum beyond the team or you must explain to them how Scrum can scale when technical problems exist. How do you manage designs across multiple teams? How do you ensure re-use of common modules? How do you manage the dependencies between teams? These are all good questions which go both unasked and unanswered.
Read more ›
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
16 of 16 people found the following review helpful By Qiulang on July 27, 2008
Format: Paperback
I built up a lot of expectation before reading this book because I learned a lot from the author's earlier book "Agile Project Management With Scrum" and not to mention that the author was the cofounder of scrum. But after I read it I was rather disappointed. I feel like the book is more like an informal set of lecture notes written for a presentation in stead of a well written and well thought book.

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.
Read more ›
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
4 of 4 people found the following review helpful By Chris Louvion on December 25, 2007
Format: Paperback
I recently run a large project (~100 people) under a structure very similar to the organization described by Ken in this book:
-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

The results?
-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.
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

Most Recent Customer Reviews