Programming Books C Java PHP Python Learn more Browse Programming Books
Agile Adoption Patterns: A Roadmap to Organizational Success and over one million other books are available for Amazon Kindle. Learn more
  • List Price: $49.99
  • Save: $11.67 (23%)
Only 5 left in stock (more on the way).
Ships from and sold by
Gift-wrap available.
Agile Adoption Patterns: ... has been added to your Cart
+ $3.99 shipping
Used: Very Good | Details
Condition: Used: Very Good
Access codes and supplements are not guaranteed with used items.
Sell yours for a Gift Card
We'll buy it for $2.00
Learn More
Trade in now
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

Agile Adoption Patterns: A Roadmap to Organizational Success Paperback – July 7, 2008

ISBN-13: 978-0321514523 ISBN-10: 0321514521 Edition: 1st

Buy New
Price: $38.32
22 New from $23.59 15 Used from $7.00
Amazon Price New from Used from
"Please retry"
"Please retry"
$23.59 $7.00

Best Books of the Month
See the Best Books of February
Want to know our Editors' picks for the best books of the month? Browse Best Books of the Month, featuring our favorite new books in more than a dozen categories.

Frequently Bought Together

Agile Adoption Patterns: A Roadmap to Organizational Success + Succeeding with Agile: Software Development Using Scrum
Price for both: $76.28

Buy the selected items together

Shop the New Digital Design Bookstore
Check out the Digital Design Bookstore, a new hub for photographers, art directors, illustrators, web developers, and other creative individuals to find highly rated and highly relevant career resources. Shop books on web development and graphic design, or check out blog posts by authors and thought-leaders in the design industry. Shop now

Product Details

  • Paperback: 408 pages
  • Publisher: Addison-Wesley Professional; 1 edition (July 7, 2008)
  • Language: English
  • ISBN-10: 0321514521
  • ISBN-13: 978-0321514523
  • Product Dimensions: 7 x 0.8 x 9.2 inches
  • Shipping Weight: 1.3 pounds (View shipping rates and policies)
  • Average Customer Review: 4.8 out of 5 stars  See all reviews (16 customer reviews)
  • Amazon Best Sellers Rank: #897,532 in Books (See Top 100 in Books)

Editorial Reviews

About the Author

Amr Elssamadisy ( is a software development practitioner who works with his clients to build better, more valuable software. He and his colleagues at Gemba Systems help both small and large development teams learn new technologies, adopt and adapt appropriate Agile development practices, and focus their efforts to maximize the value they bring to their organizations.


Amr’s technical background and experience in C/C++, Java/J2EE, and .NET allows him to appreciate the problems of development teams and offer them support.


At the same time, he realizes that most problems–even in software–are people problems that are not solved by tools and technology. Therefore, Amr and his colleagues at Gemba Systems focus on issues such as personal agility, team building, communication, feedback, and all the other soft skills that distinguish excellent teams.


Amr is also the author of Patterns of Agile Practice Adoption: The Technical Cluster. He is an editor for the AgileQ at InfoQ, a contributor to the Agile Journal, and a frequent presenter at software development conferences.


Excerpt. © Reprinted by permission. All rights reserved.



In this book, you and I focus on adoption of agile practices. I help you answer basic questions that are on your mind:

  • Where do I start?

  • What practice(s) are best for my particular environment?

  • How can I adopt these practices incrementally?

  • What pitfalls should I watch out for?

Is This Book for You?

Are you adopting one or more Agile practices or seriously thinking about trying out one or more practices on your team? Have you read any of the Agile methodology books on Extreme Programming, Scrum, or Test-Driven Development, and are you theoretically convinced about at least trying the practices?

Or perhaps you're coming off your first project and you've been asked to join another team to help them succeed as you did previously. Of course, every project is different. Are the same practices you used the last time going to be as effective on the next project? It depends! This book helps you get past "It depends!" to determine what practices should be adopted and give you some hints how they may need to be adapted.

Or maybe you are unlucky enough to have been part of a failing Agile project (or possibly are still on one). Read this book to get an idea why the practices you are using may not be applicable. Be agile about your Agile practices.

If any of these scenarios fit, this book is for you. It helps you look at the individual practices and their relationships and gives you a strategy that has been used successfully several times on multiple projects by multiple companies. It also provides you with warnings concerning how practices have gone wrong before and how you can recognize and respond to the problems that occur. This is not just one person's opinion or an untried method. All the patterns you will read about here come from real-world project experience.

Finally, let me say a few words about who this book isn't for:

  • Advanced practitioners who already get agile practices and are looking for new theories or practices. All the information in this book is collected from the experience of multiple projects, so chances are you've already heard about everything here.

  • Beginners who want to start from zero. This book does not adequately describe the practices from ground zero. However, this book will be a good companion to other works that delve more deeply into full agile practices.

The Plan

I give you even more questions that you should consider and answer on your journey toward adopting agile practices. Does this sound too good to be true? It isn't really. Many of us who have been in the Agile community for several years have figured this out the hard waymdby trial and error. This book shares those experiences. Here is an overview of what you will be able to accomplish by reading this book.

  • Understand some of the basic drivers or principles and values that underlie all Agile practices and make them successful.

  • Focus on business value to the customer. List important areas of value to many customers. An example of a business value would be Reduce Cost.

  • Introduce symptoms that occur when business value is not being delivered. I'll call these symptoms smells. An example of a smell related to the Reduce Cost business value is Customer Asks for Everything Including the Kitchen Sink.

  • Tie these business values and smells to individual agile practices.

  • Use the information in the first three items to decide which practices to adopt to increase your business value and remove the smells present at your company. At this point, you will be able to come up with a coarse-grained adoption strategy for your environment.

  • Provide a detailed description of each practice in pattern format, and include adoption information for each practice.

  • Call out practices that work well together as clusters. Relate these clusters to business values and smells. Describe the clusters and adoption strategies as done for the practices.

Structure and Content

This book is organized into several parts and subparts, so a quick overview of the structure and content of those parts is in order. I recommend that you read chapters 1 through 8 straight through and do all the exercises where applicable. This will give you essential context concerning software development so that you and I are on the same page, take you step by step through the creation of an Agile adoption strategy tailored to your organization's context, and introduce you to the pattern format in which all the practices are presented in the pattern catalog.

After you have finished these eight chapters, use Part III of the book as a reference to implement the strategy you've created. Skip around or read straight through. Both will work; you can read the patterns presented independently. Each chapter will help you adopt a particular practice, warn you of pitfalls, and give you references for further reading.

Read the case studies to get a feel for how this approach has translated to other organizations, but bewaremdit gets messy in real-life situations. Finally, the appendixes are chapters that were too useful not to include but didn't quite fit in with the flow of the book. They are short, so feel free to take a look at them at any time throughout your reading.

Part I: Thoughts about Software Development

Part I covers some basic issues of software development and sets the context for the rest of the book. I examine reasons why software development is so difficult. I also look at why adoption of new practicesmdany practices, not just Agile practicesmdare difficult and depend on your personal involvement and commitment. Read the chapters in this section, and keep the ideas in the back of your mind as you go through the rest of the book.

  • Chapter 1 "Learning Is the Bottleneck"

  • Chapter 2 "Personal Agility for Potent Agile Adoption"

Part II: Crafting an Agile Adoption Strategy

Part II starts to get into the meat of the problemmdpicking and choosing Agile practices for your particular context. By the time you are done with these chapters and have completed the exercises, you will have an initial set of practices that your team should start to adopt. Be aware that for the purposes of creating an adoption strategy, I will refer to many practices that are described in the remainder of the book. So don't worry if you have a set of practices to adopt that you do not completely understand yet. Their descriptions are in the later sections.

  • Chapter 3 "Business Value"

  • Chapter 4 "Smells"

  • Chapter 5 "Adopting Agile Practices"

Part III: The Pattern Catalog

Part III is the pattern catalog. The pattern catalog details how to successfully adopt and adapt the practices that you've determined in Part II meet your organization's business goals. This section should be used as a reference to put your adoption plan to practice. Read Chapters 6, 7, and 8 ,and then use the rest on an as-needed basis to execute your adoption strategy. Note that the practices are organized into subparts as well.

  • Chapter 6 "The Patterns of Agile Practice Adoption"

  • Chapter 7 "Goal"

  • Chapter 8 "Cycle"

Part 3.1 Feedback Practices

The feedback practices are predominantly concerned with working as a team and planning functions. They are practices that help you and your team "solve the right problem" by iteratively building your software system and consistently checking whether the system solves the needs of the customer.

  • Chapter 9 "Iteration"

  • Chapter 10 "Kickoff Meeting"

  • Chapter 11 "Backlog"

  • Chapter 12 "Planning Poker"

  • Chapter 13 "Stand-Up Meeting"

  • Chapter 14 "Done State"

  • Chapter 15 "Demo"

  • Chapter 16 "Retrospective"

  • Chapter 17 "Release Often"

  • Chapter 18 "Co-Located Team"

  • Chapter 19 "Self-Organizing Team"

  • Chapter 20 "Cross-Functional Team"

  • Chapter 21 "Customer Part of Team"

  • Chapter 22 "Evocative Document"

  • Chapter 23 "User Story"

  • Chapter 24 "Use Case"

  • Chapter 25 "Information Radiator"

Part 3.2 Technical Practices

The technical practices are concerned with "solving the problem right" by creating and maintaining the code of your software system. They are the bit-head practices that your team will use to build and evolve the software system.

  • Chapter 26 "Automated Developer Tests"

  • Chapter 27 "Test-Last Development"

  • Chapter 28 "Test-First Development"

  • Chapter 29 "Refactoring"

  • Chapter 30 "Continuous Integration"

  • Chapter 31 "Simple Design"

  • Chapter 32 "Automated Functional Tests"

  • Chapter 33 "Collective Code Ownership"

  • Chapter 34 "Pair Programming"

Part 3.3 Supporting Practices

These are not Agile practices per se, but they are practices that you can use to support your team's adoption and introduce change into your organization.

  • Chapter 35 "Coach"


Customer Reviews

4.8 out of 5 stars
5 star
4 star
3 star
2 star
1 star
See all 16 customer reviews
Well written and practical way to introduce agile to organizations based on business value.
Ed Kraay
This same approach is carried on throughout the book, making it very clear what specific benefits you can find from each practice.
James Holmes
It is not necessary to understand what design patterns are, for instance, to understand the patterns in this book.
Kindle Customer

Most Helpful Customer Reviews

11 of 11 people found the following review helpful By Linda Rising on July 30, 2008
Format: Paperback
There are many things I like about this book, not the least of which is that it is true to the "spirit" of patterns and agile -- it does not promise easy answers or quick fixes but offers down-to-earth advice based on experience. The patterns do a good job of capturing that experience but the way the patterns are written, with "threads" of stories throughout is not only convincing but enjoyable reading. I like being able to follow the real-life adventures of the same developers who struggle to solve real problems across several patterns. I also like the case study in Chapter 46 where a real company with real problems does a pretty good job of moving forward, but it's not a "and they all lived happily ever after" scenario. We're overwhelmed with books and advice these days, so it's nice to see someone who offers help and hope but not hype!
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
7 of 7 people found the following review helpful By James Holmes on July 2, 2008
Format: Paperback
Elssamadisy's book is in tough, tough company. How can you compete in the same space as amazing works like Subramaniam and Hunt's Practices of an Agile Developer or Shore and Warden's The Art of Agile Development? Those are tough, tough classics to go against when trying to explain how teams/companies should adopt agile practices.

Amr pulls it off by organizing his material in a fresh form which I found very useful. He hits many of the same points as other works on Agile (smells, process, team empowerment, practices, etc.), but emphasizes the business value of each point. For example, his chapter on User Story lays out the case that user stories are simple documents in their initial draft. The value comes from developers having conversations to flesh out the details and implementation of the story. Product utility is improved, and development costs are reduced.

This same approach is carried on throughout the book, making it very clear what specific benefits you can find from each practice. Additionally, each practice or chapter follows a nice recipe-like format. Start off with business value, move on to a sketch describing the practice, follow up with context of the practice and forces impacting it, then look to why you'd want the particular practice, adoption details, and a bit on the practice's cons and variations.

The book starts out with a high-level overview of agile, then moves on to specific patterns/practices. Each pattern is a short, separate chapter with about 40 patterns in total.
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
5 of 5 people found the following review helpful By Kindle Customer on August 31, 2008
Format: Paperback Verified Purchase
There are many books about the theories and practices that are encompassed in the word "agile". Quite a number of them are quite good in terms of addressing the specific practices and how to implement them. It you want to learn Scrum or XP, there is no shortage of books and how-to materials, along with plenty of advice.

This book, however, addresses the goal of agile adoption from a new perspective - patterns of behavior and thought, and how to specifically leverage and/or address them. It addresses this from the organizational/team perspective, rather than the individual perspective, which makes it particularly valuable for those of us who are working in an organizational transformation/agile adoption environment.

While it might seem that "patterns" would appeal to the techies in its audience, my experience is that Amr has managed to frame his work in terms and concepts that are readily understood by all. This book is readily digestible by non-technical managers and staff, as well as by those of us who have spent/currently spend our time in a technology environment. It is not necessary to understand what design patterns are, for instance, to understand the patterns in this book.

For those who are either anticipating agile adoption or actively engaged in it, or even those who are struggling with what seems to be a failed adoption, this book is required reading. The way in which the patterns are presented, the clear and pragmatic exercises described to help work through them, and the suggestions for ways to approach it all are just what's needed.

Real world, pragmatic, easy to read, and easy to digest - that's what this book is all about.

It will be on my desk and heavily thumbed in short order.
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
3 of 3 people found the following review helpful By Larry Guger on August 18, 2008
Format: Paperback
There are plenty of excellent books available that explain agile practices. What has been missing until now is the guidance to apply them. Amr's approach to achieving agile practices is filling a need that has been felt by many for several years now. Amr takes an excellent approach to identifying the best means of applying agile techniques based on a combination of business needs and project pains. This approach stays focused on delivering business value to the enterprise as they move towards agile practices.

Amr has an excellent writing style that is both concise and entertaining delivering information in a manner that can be absorbed in bite-sized chunks and applied as needed based on the initial needs assessment. After identifying the business needs or pains the best agile practices to deliver the value or reduce the pain are described in a manner that determines which practices will deliver the best value to meet your identified needs.

I highly recommend that you pick up this book if you are either planning to adopt agile practices, struggling to adopt agile practices or are looking to enhance the agile practices that you currently employ. Well done Amr.
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

More About the Author

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

What Other Items Do Customers Buy After Viewing This Item?