- Paperback: 624 pages
- Publisher: Addison-Wesley Professional; 1 edition (February 5, 2010)
- Language: English
- ISBN-10: 0321636406
- ISBN-13: 978-0321636409
- Product Dimensions: 7 x 1.4 x 9 inches
- Shipping Weight: 2.1 pounds (View shipping rates and policies)
- Average Customer Review: 14 customer reviews
- Amazon Best Sellers Rank: #859,903 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.
Practices for Scaling Lean & Agile Development: Large, Multisite, and Offshore Product Development with Large-Scale Scrum 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Garth Brooks: The Anthology Part 1 | Limited Edition
A great gift for country music fans, The Anthology Part 1 includes CDs containing the music of Garth's first five years, and behind-the-scenes photographs and stories never before made public. Learn more
Frequently bought together
Customers who bought this item also bought
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).
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
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.
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.
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. They have brought up the issues on onshore and offshore collaboration, use of video calls for communications, and importance of mutual visits by the team members to each others' locations. The authors showed clearly what it takes to make a large multisite team function like a distributed team instead of a dispersed team. The way pain points have been addressed, that can be brought up only through hard earned experiences, and the authors deserve credits for sharing these observations so candidly.
Many of the points don't resonate well with my type of thinking. As example, the authors emphasized on avoiding fixed fee fixed scope engagements, which I don't think buyers would be comfortable with. But then, the authors didn't write a book of standards, they were merely documenting their experience. For each readers with significant experience in software development, there would be points in this book to disagree with. That's the most unique characteristic of this book.
I would recommend this book to all Agile practitioners.