Digital List Price: $47.99
Kindle Price: $37.67

Save $22.32 (37%)

These promotions will be applied to this item:

Some promotions may be combined; others are not eligible to be combined with other offers. For details, please see the Terms & Conditions associated with these promotions.

Deliver to your Kindle or other device

Deliver to your Kindle or other device

Flip to back Flip to front
Audible Narration Playing... Paused   You are listening to a sample of the Audible narration for this Kindle book.
Learn more

Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum Kindle Edition

4.1 out of 5 stars 13 customer reviews

New from Used from
"Please retry"

Length: 624 pages Enhanced Typesetting: Enabled
  • Due to its large file size, this book may take longer to download

Kindle Delivers
Kindle Delivers
Subscribe to the Kindle Delivers monthly e-mail to find out about each month's Kindle book deals, new releases, editors' picks and more. Learn more (U.S. customers only)

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.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your email address or mobile phone number.

Editorial Reviews

From the Back Cover

Lean and Agile Development for Large-Scale Products: Key Practices for Sustainable Competitive Success Increasingly, large product-development organizations are turning to lean thinking, agile principles and practices, and large-scale Scrum to sustainably and quickly deliver value and innovation. Drawing on their long experience leading and guiding lean and agile adoptions for large, multisite, and offshore product development, internationally recognized consultant and best-selling author Craig Larman and former leader of the agile transformation at Nokia Networks Bas Vodde share the key action tools needed for success. Coverage includes Frameworks for large-scale Scrum for multihundred-person product groupsTesting and building quality inProduct management and the end of the "contract game" between business and R&DEnvisioning a large release, and planning for multiteam developmentLow-quality legacy code: why it's created, and how to stop itContinuous integration in a large multisite contextAgile architectingMultisite or offshore developmentContracts and outsourced development In a competitive environment that demands ever-faster cycle times and greater innovation, the practices inspired by lean thinking and agile principles are ever-more relevant. "Practices for Scaling Lean & Agile Development "will help people realize a lean enterprise-and deliver on the significant benefits of agility. In addition to the action tools in this text, see the companion book "Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum"for complementary foundation tools.

About the Author

Craig Larman is a management and product development consultant in enterprise-level adoption and use of lean development, agile principles and practices, and large scale Scrum in large, multisite, and offshore development. He served as chief scientist at Valtech, an international consulting and agile offshore outsourcing company. His books include the best-sellers Agile and Iterative Development: A Manager’s Guide (Addison-Wesley, 2004) and Applying UML and Patterns, Third Edition (Prentice Hall, 2005).


Bas Vodde works as an independent product development consultant and large scale Scrum coach. For several years he led the agile and Scrum enterprise-wide adoption initiative at Nokia Networks. He is passionate about improving product development, and an avid student of organizational, team management, and product development research, and remains an active developer. Bas is the coauthor (with Craig) of the companion book Scaling Lean & Agile Development (Addison-Wesley, 2009).

Product Details

  • File Size: 11834 KB
  • Print Length: 624 pages
  • Simultaneous Device Usage: Up to 5 simultaneous devices, per publisher limits
  • Publisher: Addison-Wesley Professional; 1 edition (January 26, 2010)
  • Publication Date: January 26, 2010
  • Sold by: Amazon Digital Services LLC
  • Language: English
  • ASIN: B0046EDOYU
  • Text-to-Speech: Enabled
  • X-Ray:
  • Word Wise: Not Enabled
  • Lending: Not Enabled
  • Enhanced Typesetting: Enabled
  • Amazon Best Sellers Rank: #643,549 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
  •  Would you like to give feedback on images or tell us about a lower price?

More About the Authors

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Top Customer Reviews

Format: Paperback Verified Purchase
The content is rich and covers almost everything about scrum.
This is a very good book on agile development, unfortunately, inappropriately named.

1) Readers who bought this book, probably are interested in the additional stuff on multisite and offshore, and not the everything about Agile Development. Thus, this book can be, should be a lot thinner.

2) The book contains lots of good examples. Unfortunately, I have to jump around the book to read them. Thus, the organization of the content can be improved.
Comment 11 of 12 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Paperback Verified Purchase
This book is in my opinion, invaluable for anyone looking at scaling Agile/Scrum to beyond just one team.

It has clear, practical advice. In particular, the clarification of the dangers of component teams is particularly valuable as well as communication patterns between teams.

As an Agile coach, I have personally applied some of the patterns with success and sadly have witnessed many of the anti-patterns play out.
Comment 7 of 7 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Paperback
I was blown away by "Scaling Lean & Agile Development". Some time has passed since then but I still feel that it's one of the most important development books I've read. That book alluded to the companion volume, "Practices for Scaling Lean & Agile Development", and as you can imagine I awaited its publication eagerly. It came out in February - I've worked my way through it now. It's most definitely a worthy successor.

The first book presents theoretical and philosophical underpinnings for agile and lean development. The second book presents a survey of practices relevant to all aspects of the process of developing software at scale, presented by two guys who bring a wealth of knowledge and experience to the table.

The above was taken from a longer review on the Rally Agile blog - you can see the rest of it there ([...] and then follow the links for the agile blog).
Comment 5 of 6 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Paperback
The Introduction section of the book takes on the issue upfront - the companies grappling with a large scale software development work. The section makes it very clear that adopting Agile practices doesn't help either, in fact, it complicates the issues. The section candidly confesses that the authors are not attempting to create a bible, rather they are sharing their experience. Truthful, uncoated, shareable experience.

The book starts with the tools and actions that are required with higher emphasis for a large, multisite software development that follows Agile practices instead of traditional models like waterfall. There are twelve such chapters that focuses on actions and tools. It starts with testing, then moves to product management, planning and coordination. Subsequent five chapters focus on requirements management (PBI), design, architecture, legacy code integration, and continuous integration. All these chapters are organized by a set of takeaway points. Each such point are well illustrated, yet not too big. More importantly, those are relevant takeaway points.

The final three chapters focus on multisite development, offshore development, and outsourcing. These three chapters make this book an exceptional one. All the books on Agile practices I had read before this one summarily dismissed the idea of offshoring. While the market forces compelled many companies to try shipping software development work overseas, the mutual agreements followed dated contracting procedures. Relationship between onshore and offshore too, remained significantly patchy. The authors took on these issues directly.
Read more ›
Comment 2 of 2 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Paperback
This book is a companion book of 'Scaling Lean and Agile Development - Thinking and Organisational Tools for Large Scale Scrum'. In this book the authors talk about the various scrum practices which can be adopted while an organisation transform to agile and maintain its agility. It takes an understanding of systems thinking, queuing theory, feature teams, requirement areas, the impact of organisation policies explained in detail in the companion book, for these practices to bloom into a flower. With a little investment in learning and organisation re-design, these action tools can be very effective.

The cover page of the book is quite different with fractal art in it. The explanation given is also unique. It denotes that, there is no 'fractal' or 'best' practice but only adequate practice depending on specific context and situation of the enterprise. Practice should always be improved upon, even when relevant to a new context, though the underlying principles do not change. Even these fractal principles, practiced at team level may not work at enterprise level.

I liked the legacy code chapter the most as I was able to relate to it better, working in a legacy product with several millions of LOC. The authors argue that the only two reasons for legacy code are poor development skills and unrealistic deadlines with fixed content. Solution for the first issue is continual learning. The second one is quite tricky. It is suggested that organisations could be transparent and collaborate with the customers by involving them in the product development - reporting the development status to the key customers iteration by iteration with a release burn down chart and updated PBL, asking them feedback on priorities and modified goals , and giving probabilistic estimates.
Read more ›
Comment 3 of 4 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse

Most Recent Customer Reviews


There are no discussions about this product yet.
Be the first to discuss this product with the community.
Start a new discussion
First post:
Prompts for sign-in