Buy new:
$32.67$32.67
$3.99
delivery:
Friday, Feb 2
Ships from: Becker Inc. Sold by: Becker Inc.
Buy used: $10.47
Other Sellers on Amazon
+ $3.99 shipping
88% positive over last 12 months
100% positive over last 12 months
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Follow the author
OK
Scaling Software Agility: Best Practices for Large Enterprises 1st Edition
Purchase options and add-ons
–Jim Highsmith, director, Agile Practice, Cutter Consortium, author of Agile Project Management “There’s tension between building software fast and delivering software that lasts, between being ultra-responsive to changes in the market and maintaining a degree of stability. In his latest work, Scaling Software Agility, Dean Leffingwell shows how to achieve a pragmatic balance among these forces. Leffingwell’s observations of the problem, his advice on the solution, and his description of the resulting best practices come from experience: he’s been there, done that, and has seen what’s worked.”
–Grady Booch, IBM Fellow
Agile development practices, while still controversial in some circles, offer undeniable benefits: faster time to market, better responsiveness to changing customer requirements, and higher quality. However, agile practices have been defined and recommended primarily to small teams. In Scaling Software Agility, Dean Leffingwell describes how agile methods can be applied to enterprise-class development.
- Part I provides an overview of the most common and effective agile methods.
- Part II describes seven best practices of agility that natively scale to the enterprise level.
- Part III describes an additional set of seven organizational capabilities that companies can master to achieve the full benefits of software agility on an enterprise scale.
This book is invaluable to software developers, testers and QA personnel, managers and team leads, as well as to executives of software organizations whose objective is to increase the quality and productivity of the software development process but who are faced with all the challenges of developing software on an enterprise scale.
Preface
Acknowledgments
About the Author
Part I: Overview of Software Agility
Chapter 1: Introduction to Agile Methods
Chapter 2: Why the Waterfall Model Doesn’t Work
Chapter 3: The Essence of XP
Chapter 4: The Essence of Scrum
Chapter 5: The Essence of RUP
Chapter 6: Lean Software, DSDM, and FDD
Chapter 7: The Essence of Agile
Chapter 8: The Challenge of Scaling Agile
Part II: Seven Agile Team Practices That Scale
Chapter 9: The Define/Build/Test Component Team
Chapter 10: Two Levels of Planning and Tracking
Chapter 11: Mastering the Iteration
Chapter 12: Smaller, More Frequent Releases
Chapter 13: Concurrent Testing
Chapter 14: Continuous Integration
Chapter 15: Regular Reflection and Adaptation
Part III: Creating the Agile Enterprise
Chapter 16: Intentional Architecture
Chapter 17: Lean Requirements at Scale: Vision, Roadmap, and Just-in-Time Elaboration
Chapter 18: Systems of Systems and the Agile Release Train
Chapter 19: Managing Highly Distributed Development
Chapter 20: Impact on Customers and Operations
Chapter 21: Changing the Organization
Chapter 22: Measuring Business Performance
Conclusion: Agility Works at Scale
Bibliography
Index
- ISBN-109780321458193
- ISBN-13978-0321458193
- Edition1st
- Publication dateFebruary 26, 2007
- LanguageEnglish
- Dimensions7.3 x 1 x 9.1 inches
- Print length384 pages
Frequently bought together

Customers who viewed this item also viewed
Editorial Reviews
From the Back Cover
–Jim Highsmith, director, Agile Practice, Cutter Consortium, author of Agile Project Management“There's tension between building software fast and delivering software that lasts, between being ultra-responsive to changes in the market and maintaining a degree of stability. In his latest work, Scaling Software Agility, Dean Leffingwell shows how to achieve a pragmatic balance among these forces. Leffingwell's observations of the problem, his advice on the solution, and his description of the resulting best practices come from experience: he's been there, done that, and has seen what's worked.”
–Grady Booch, IBM Fellow
Agile development practices, while still controversial in some circles, offer undeniable benefits: faster time to market, better responsiveness to changing customer requirements, and higher quality. However, agile practices have been defined and recommended primarily to small teams. In Scaling Software Agility, Dean Leffingwell describes how agile methods can be applied to enterprise-class development.
- Part I provides an overview of the most common and effective agile methods.
- Part II describes seven best practices of agility that natively scale to the enterprise level.
- Part III describes an additional set of seven organizational capabilities that companies can master to achieve the full benefits of software agility on an enterprise scale.
This book is invaluable to software developers, testers and QA personnel, managers and team leads, as well as to executives of software organizations whose objective is to increase the quality and productivity of the software development process but who are faced with all the challenges of developing software on an enterprise scale.
Preface
Acknowledgments
About the Author
Part I: Overview of Software Agility
Chapter 1: Introduction to Agile Methods
Chapter 2: Why the Waterfall Model Doesn't Work
Chapter 3: The Essence of XP
Chapter 4: The Essence of Scrum
Chapter 5: The Essence of RUP
Chapter 6: Lean Software, DSDM, and FDD
Chapter 7: The Essence of Agile
Chapter 8: The Challenge of Scaling Agile
Part II: Seven Agile Team Practices That Scale
Chapter 9: The Define/Build/Test Component Team
Chapter 10: Two Levels of Planning and Tracking
Chapter 11: Mastering the Iteration
Chapter 12: Smaller, More Frequent Releases
Chapter 13: Concurrent Testing
Chapter 14: Continuous Integration
Chapter 15: Regular Reflection and Adaptation
Part III: Creating the Agile Enterprise
Chapter 16: Intentional Architecture
Chapter 17: Lean Requirements at Scale: Vision, Roadmap, and Just-in-Time Elaboration
Chapter 18: Systems of Systems and the Agile Release Train
Chapter 19: Managing Highly Distributed Development
Chapter 20: Impact on Customers and Operations
Chapter 21: Changing the Organization
Chapter 22: Measuring Business Performance
Conclusion: Agility Works at Scale
Bibliography
Index
About the Author
Dean Leffingwell is a renowned software development methodologist, author, and software team coach who has spent his career helping software teams meet their goals. He is the former founder and CEO of Requisite, Inc., makers of RequisitePro, and a former vice president at Rational Software, where he was responsible for the commercialization of RUP. During the last five years, in his role as both an independent consultant and as advisor/methodologist to Rally Software, Mr. Leffingwell has applied his experience to the organizational challenge of implementing agile methods at scale with entrepreneurial teams as well as distributed, multinational corporations. These experiences form much of the basis for this book. Mr. Leffingwell is also the lead author of Managing Software Requirements, Second Edition: A Use Case Approach (Addison-Wesley, 2003).
Product details
- ASIN : 0321458192
- Publisher : Addison-Wesley Professional; 1st edition (February 26, 2007)
- Language : English
- Paperback : 384 pages
- ISBN-10 : 9780321458193
- ISBN-13 : 978-0321458193
- Item Weight : 1.45 pounds
- Dimensions : 7.3 x 1 x 9.1 inches
- Best Sellers Rank: #1,850,122 in Books (See Top 100 in Books)
- #2,093 in Starting a Business (Books)
- #2,473 in Software Development (Books)
- #6,860 in Computer Software (Books)
- Customer Reviews:
Important information
To report an issue with this product or seller, click here.
About the author

Recognized as one of the world’s foremost authorities on Lean-Agile best practices, Dean Leffingwell is an entrepreneur and software development methodologist best known for creating SAFe®, the world’s most widely used framework for business agility.
His best-selling books, Scaling Software Agility, Agile Software Requirements, and SAFe® Distilled, form much of the basis of modern thinking on Lean-Agile practices and principles. Founder of several successful startups, including Requisite, Inc. (acquired by Rational), Mr. Leffingwell also served as Chief Methodologist to Rally Software, and prior to that, as Sr. Vice President at Rational Software (now part of IBM). He serves as Chief Methodologist to Scaled Agile, Inc., which he co-founded in 2011.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on Amazon-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
Agile projects are carefully planned, but they are planned differently, and the plan is revised and refined more often. You may also have been told that agile methods have their "sweet spots" around small teams (7 to 12 people), preferably collocated, for short projects (2 to 9 months), making them inapplicable in your own environment of large, long-lived, globally distributed software development endeavors. This too is all changing rapidly as numerous projects around the world are pushing these boundaries, and they are achieving success in higher productivity and higher quality of their software outcomes.
Herein lays Dean's major contribution to be discovered in the body of this book. Rising above the debate between the various families of agile processes--XP, Scrum, Lean, DSDM, FDD, Rational Unified Process (RUP) and so on (which are nicely presented), he establishes what is common among them as a baseline before he proceeds to his main objective of showing how to scale these agile approaches beyond their existing sweet spot. He is not introducing a new agile process to add to this already long roster, but rather he extends them all with a set of new practices, practices that live at a higher level, both technical and managerial, and that embrace and integrate existing established agile practices (the ones with the funny names). In addition to synthesizing the best engineering practices that are common among these methods, he also describe methods aiming at the governance of larger agile projects: topics such as release planning; handling large, distributed teams; establishing the business value of the project; and dealing with large, long-lived developments, to mention only a few.
The author's work is not academic, he's not merely positing some new bold conjectures for you to try out. His advice is rooted in years of active, hands-on practice in many companies, many projects, in a wide range of industries, from life-sustaining medical equipment to software tools, from amusement park rides to large-scale IT infrastructure applications.
Philippe Kruchten
Vancouver, BC Canada
PS:Yes, I am the same guy who wrote the foreword. I have not changed my mind since.
The Rational Unified Process: An Introduction, Third Edition
The Rational Unified Process Made Easy: A Practitioner's Guide to Rational Unified Process
Software Engineering Processes: With the UPEDU
Scaling Software Agility tackles the question "How to do agile development in large systems". The experience in the book seems to mainly be build on one project in BMC. In the first part of the book, Dean goes over the most popular agile methods and gived a quick introduction. He then attempts to extract common parts for the methods. In part two he picks out 7 practices and claims that they scale without modification. In the last part of the book, he adds 7 new practices, which, in his opinion, are needed for large agile projects.
Personally I've been working with a lot of large agile projects and thus was very interested in this book, especially to learn new things or see if Dean had similar problems. I was slightly dissapointed, but let me explain.
One of the fundamental points in the book is that agile development can be executed on team level. The unit of work is what Dean calls "component teams". In his book, he does not cover the question of code ownership, but the component team organization suggests a traditional organization based on the architecture of the system. This is confirmed by the problems he mentions, which are inherent to component teams. These are the need for more architecture, the need for much dependency management between the component teams and several others. Dean keeps with the traditional methods of organizing projects, he doesn't question it. The component teams thus lose part of the end-customer focus and more management and architecture is needed. Slowly parts of waterfall development are re-emerging. The book does NOT cover the organization around feature teams and the scaling of practices like shared code ownership. Also it doesn't talk about continuous integration in relationship to the team structure etc. A missed opportunity.
In part two, Dean describes 7 practices which scale without adjustment. I totally agree that these practices scale, but there is some need for doing them slightly different. As example, "how do we coordinate the different planning meetings?" The book explains the traditional practice but does NOT talk about how to actually scale it. It doesn't mention different problems that might happen and different possible solutions. It seems to just cover the surface of the subject.
The last chapters about how agile development will influence the rest of the organization were good. They touch a subject that is currently rarely covered.
In conclusion, a useful book to read. I would not follow all recommendations and more needs to be written on the subject. Still, definitively worth reading.
Top reviews from other countries
It would have been great if the author were to include more stories and more examples to make it a better read. However, the ample number of lessons and advice make up for that.
However, the title talks about scaling and large enterprise so my expectation was not an agile introduction but i was expecting a book focusing on scaling (sure, introduction is ok, but in this case 2/3 of the book is introduction).
The scaling parts are ok, but on a very high level. There are some challenges described (like architecture, co-location etc) but i feel it miss a lot when it comes to solutions. Sure, there is not one true way to mitigate the challenges, but these areas is where i expected more focus.
In summary, an OK book, but if you already have experience in agile you will not learn a lot more.










