Disciplined Agile Delivery: A Practitioner's Guide to Agi... and over one million other books are available for Amazon Kindle. Learn more
CDN$ 47.24
  • List Price: CDN$ 74.99
  • You Save: CDN$ 27.75 (37%)
In Stock.
Ships from and sold by Amazon.ca.
Gift-wrap available.
Disciplined Agile Deliver... has been added to your Cart
Have one to sell?
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

Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise Paperback – May 23 2012

See all 2 formats and editions Hide other formats and editions
Amazon Price New from Used from
Kindle Edition
"Please retry"
"Please retry"
CDN$ 47.24
CDN$ 40.75 CDN$ 76.77

Unlimited FREE Two-Day Shipping for Six Months When You Join Amazon Student

Frequently Bought Together

Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise + Leader Effectiveness Training: L.E.T. (Revised): "L.E.T."
Price For Both: CDN$ 64.48

Product Details

  • Paperback: 544 pages
  • Publisher: IBM Press; 1 edition (May 23 2012)
  • Language: English
  • ISBN-10: 0132810131
  • ISBN-13: 978-0132810135
  • Product Dimensions: 17.8 x 3.3 x 22.6 cm
  • Shipping Weight: 862 g
  • Average Customer Review: 5.0 out of 5 stars  See all reviews (4 customer reviews)
  • Amazon Bestsellers Rank: #17,866 in Books (See Top 100 in Books)
  • See Complete Table of Contents

Product Description


“Mark and Scott not only made me think, they reminded me of lots of things that I had forgotten. Things that the agile fashion police have made uncool to talk about. This book is not about fashionable agile; it is about serious change, and it should be required reading for any change leader.”

--Dave West, chief product officer, Tasktop, and former VP and research director Forrester Research


“Finally, a practical down-to-earth guide that is true to agile values and principles while at the same time acknowledging the realities of the business and the bigger picture. You will find no purist dogma here, nor any hype or hyperbole. Ambler and Lines show how to navigate the varied contexts and constraints of both team-level and enterprise-level needs to hit the agile ‘sweet spot’ for your team and attain the real benefits of sustainable agility. I wish I’d had this book ten years ago!”

--Brad Appleton, agile/lean development champion for a large fortune 150 telecommunications company


“We have found the guidance from Disciplined Agile Delivery to be a great help in customizing our PMO governance for agile projects at CP Rail. The book will definitely be on the must-read list for teams using agile delivery.”

--Larry Shumlich, project manager coach, Canadian Pacific Railway


“This book is destined to become the de facto standard reference guide for any organization trying to apply agile/scrum in a complex environment. Scott and Mark provide practical guidance and experiences from successful agile teams on what it takes to bring an end-to-end agile delivery lifecycle to the enterprise.”

--Elizabeth Woodward, IBM agile community leader, coauthor of A Practical Guide to Distributed Scrum


“There are many ways to achieve the benefits of agility, so it’s really encouraging to see a pragmatic and usable ‘umbrella’ description that encapsulates most of these without becoming a diluted kind of ‘best of’ compilation, or a one-size-fits-all. Great reading for anyone orientating themselves in an ever-growing and complex field.”

--Nick Clare, agile coach/principal consultant, Ivar Jacobson International


“Scott and Mark have compiled an objective treatment of a tough topic. Loaded with insights from successful application under game conditions, this book strikes a good balance between progressive agilists looking to accelerate change and conservative organizational managers looking for scalable solutions.”

--Walker Royce, chief software economist, IBM


“Disciplined Agile Delivery, a hybrid and experience-based approach to software delivery, reflects the growing trend toward pragmatism and away from the anti-syncretism that has plagued the software development industry for over 40 years. I commend Scott and Mark for writing this book and showing the leadership necessary to take our profession to the next level.”

--Mark Kennaley, CTO, Software-Development-Experts.com; author of SDLC 3.0: Beyond a Tacit Understanding of Agile


“I’ve seen ‘certified agile’ run rampant in an organization and create more severe problems than it solved. Finally, we have a definitive source on how to apply agile pragmatically with discipline to deliver success. Thanks, Scott and Mark.”

--Carson Holmes, EVP, service delivery, Fourth Medium Consulting, Inc.

About the Author

Scott W. Ambler is Chief Methodologist for IT with IBM Rational, working with IBM customers around the world to help them to improve their software processes. In addition to Disciplined Agile Delivery (DAD), he is the founder of the Agile Modeling (AM), Agile Data (AD), Agile Unified Process (AUP), and Enterprise Unified Process (EUP) methodologies and creator of the Agile Scaling Model (ASM). Scott is the (co-)author of 20 books, including Refactoring Databases, Agile Modeling, Agile Database Techniques, The Object Primer, 3rd Edition, and The Enterprise Unified Process. Scott is a senior contributing editor with Dr. Dobb’s Journal. His personal home page is www.ambysoft.com.


Mark Lines co-founded UPMentors in 2007. He is a disciplined agile coach and mentors organizations on all aspects of software development. He is passionate about reducing the huge waste in most IT organizations and demonstrates hands-on approaches to speeding execution and improving quality with agile and lean techniques. Mark provides IT assessments and executes course corrections to turn around troubled projects. He writes for many publications and is a frequent speaker at industry conferences. Mark is also an instructor of IBM Rational and UPMentors courses on all aspects of software development. His Web site is www.UPMentors.com.

Inside This Book (Learn More)
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index
Search inside this book:

What Other Items Do Customers Buy After Viewing This Item?

Customer Reviews

5.0 out of 5 stars
5 star
4 star
3 star
2 star
1 star
See all 4 customer reviews
Share your thoughts with other customers

Most helpful customer reviews

1 of 1 people found the following review helpful By Amazon Customer on June 22 2012
Format: Paperback Verified Purchase
The book is well structured. First 3 chapters are about Agile basic concepts. We are introduced on the definition of the DAD (Disciplined Agile delivery), its important characteristics and its relationship to all Agile flavors. Even a very knowledgeable reader of Agile, should pay attention on those chapters before reads the rest.
One of `DAD' framework's main characteristic is 'people first'. So the second part of the book (2 chapters) is about people and their roles. There is an excellent description of the roles and the teams. I like the mapping of the traditional roles with the agile roles (See figure in Page 80).
Parts 3, 4, 5 covers the whole lifecycle 'inception 'construction ' release' as it is guided based on DAD Framework.
I am most impressed that Authors covered all serious aspects of Agile SDLC using a 'global' view. There are more than one way to do things within the Agile framework. This book can assist you on your decision making.
Some examples:
Chapter's 8 'Choosing a Work Item management strategy' was one of my favorites. So many books oversimplify the selection of work items. First time I read, how you choose a management strategy for it. Another favorite is Chapter 9 'Choosing the Right Level of Detail- Choose the right type of models-Choosing a Modeling strategy' . It helps tremendously the reader to design his 'agile' approach.
Another favorite was Chapter 10 'Initial Release planning'. Starting with, who does planning , choosing right scope for the plan, choosing planning strategy before goes to formulating the schedule and estimating cost. It helped me to build some solid foundation on planning principals for Agile. Book is full of those 'due diligence' sections for all Agile core SDLC concepts.
Read more ›
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.
Format: Paperback Verified Purchase
“The beauty of agile methods is that they focus us on delivering working software of high business value to our customers early and often”, write Ambler and Lines early in their book. They then lay out a framework of ideas and options to help achieve this overarching goal.

Whereas much of the agile literature focuses on methodologies (usually Scrum) for the Construction Phase, Ambler and Lines take a full lifecycle view. Specific goals are recommended for each phase - Inception, Construction and Transition - and a range of strategies are presented to help achieve those goals. The strategies range from least to most agile, providing the reader with flexibility to tailor an approach best suited to the realities of his or her organization. For example, one goal of the Inception Phase is to identify the vision for the project. Strategies include a detailed vision document, project charter or business case; a lightweight vision statement; vision radiators; and, no shared vision. Pros, cons and considerations are provided for each strategy to assist the reader in making an informed choice.

Another significant departure from the norm is the enterprise view taken by the authors. They cover topics such as enterprise architecture, corporate guidelines and standards, tooling strategies and project governance. These are important considerations for anyone looking to scale agile beyond a few project teams. Having worked in provincial government for the past 33 years, I am well aware of the need to satisfy a range of stakeholder interests and needs beyond one's own limited domain. The beauty of the DAD book is that it acknowledges these realities and provides suggestions for improvement.
Read more ›
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.
Format: Paperback Verified Purchase
Disciplined Agile Delivery (DAD) is a must read for Agile practitioners who are looking for a framework that offers guidance to delivering consumable software products while following the discipline that the project and corporate structure demand. I like that this book covers the different agile methodologies and encompasses them in a common sense approach to project delivery while keeping an eye on risk mitigation.

The book is very well organized. It first introduces the reader to Agile principles and methodologies. After that, it describes the roles within a typical project, followed by the project life cycle. Within each chapter, there is a small mind map the outlines the concepts of the chapter, followed by details for each concept. Once the book gets into the life cycle of the project, the chapters end with a summary table that compares the advantages and disadvantages of strategies covered in that chapter.

If an organization is considering a move towards an Agile approach to I.T. project delivery, then having a flexible, adaptable framework should make Agile an easy sell. I would say with confidence that this book provides that framework.
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.
Format: Paperback
I just finished "Disciplined Agile Delivery". Although dense at times, it was quite an enjoyable read and will be very useful for larger organizations struggling to make agile processes work inside their existing (enterprise) environment. Even smaller companies will find things of value in here. Good stuff.
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 Helpful Customer Reviews on Amazon.com (beta)

Amazon.com: 15 reviews
16 of 18 people found the following review helpful
Agile Done Right!!!! July 11 2012
By T. Anderson - Published on Amazon.com
Format: Paperback
I was excited to see that Mr. Ambler was working on Disciplined Agile Delivery (DAD) and was looking forward to this book. One of the biggest challenges I have is that most of the successful agile teams I interact with are isolated small teams using Scrum out of the box. It is working on the projects that have small teams with small scope, usually building one application in isolation. They don't have to be concerned with enterprise level integration.

The small successful teams I have seen also do no architecture. Although the end result is exactly what you do not want for high modifiability, they simply get it live. Usually a little buggy and slow, but they make it live nevertheless.

That is not true of all the projects I interact with. There are some large enterprise wide Scrum initiatives. The successful ones brought in an external Scrum coach to train them. Because of the complexity of the project they were also forced to do architecture and design. They ended up back at more of an iterative process. By the time they were done modifying the Scrum process, beside some Scrum names, they were much closer to the Unified Process than Scrum.

Until now my primary resource for information, that I also consider good information, implementing agile practices at an enterprise level has been Scaled Agile Framework. It is completely covered in the book Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. The Scaled Agile Framework is great,but I am glad to have this second resource!!! The attempts to sell Scrum of Scrums for dealing with enterprise level concerns has failed miserably.

It has been a wild ride. When it was all about UP, RUP, EUP, PLE, and Waterfall I was always in a battle to trim back the process ceremony in order avoid waste being template zombies. Then the Agile Age of Aquarius took over and I couldn't get anyone to give any thought to anything before riding off into cowboy coding bliss. The majority of the projects went from tons of worthless documents to tons of worthless code!!!!

After spending a lot of time battling the Agile Age of Aquarius coding cowboys I am so thankful some of the leaders in the industry, like the authors of this book, are starting to swing the pendulum back the other way. I just wish people would get that it's about tailoring to meet the needs of a project with the resources available. One shoe size doesn't fit everyone.

The book goes into great detail explaining the need for DAD and break it down into digestible parts. The book has 7 parts. I have listed them below with the chapters in each.

Part 1: Introduction to Disciplined Agile Delivery (DAD)
Chapter 1: Disciplined Agile Delivery in a Nutshell
Chapter 2: Introduction to Agile and Lean
Chapter 3: Foundations of Disciplined Agile Delivery

Part 2: People First
Chapter 4: Roles, Rights, and Responsibilities
Chapter 5: Forming Disciplined Agile Teams

Part 3: Initiating a Disciplined Agile Delivery Project
Chapter 6: The Inception Phase
Chapter 7: Identify a Project Vision
Chapter 8: Identify the Scope
Chapter 9: Identify a Technical Strategy
Chapter 10: Initial Release Planning
Chapter 11: Forming the Team and Work Environment
Chapter 12: Case study: Inception phase

Part 4: Building a Consumable Solution Incrementally
Chapter 13: The Construction Phase
Chapter 14: Initiating a Construction Iteration
Chapter 15: A Typical Day During Construction
Chapter 16: Concluding a Construction Iteration
Chapter 17: Case study: Construction phase

Part 5: Releasing the Solution
Chapter 18: The Transition Phase
Chapter 19: Case study: Transition phase

Part 6: Disciplined Agile Delivery in the Enterprise
Chapter 20: Governing Disciplined Agile Teams
Chapter 21: Scaling Disciplined Agile Delivery
Chapter 22: Adoption and Tailoring
Chapter 23: Overcoming Organizational Impediments

Part 7: Conclusion
Chapter 24: Towards Lean Disciplined Agile Delivery
Chapter 25: Parting Thoughts

DAD is a hybrid of agile methods including Scrum, XP, Agile Modeling, Lean, Agile Data, and the Unified Process. It does what so many successful Agile projects are doing today that are larger in size. It uses what works, when its needed, and leaves the Agile Zealot Elitist Attitude behind. It is so refreshing to read an Agile book without the attitude.

DAD recognizes Scrum's shortcomings as primarily focused on management and brings back architecture and includes agile development practices that are easily excused from most Scrum projects.

DAD includes phases. It includes a project initiation and release activities that are missing from Scrum. DAD has three phases Inception, Construction, and Transition.

DAD also comes in two flavors, basic and advanced. The primary difference is that advanced is for more experienced teams that can take advantage of lean strategies which eliminates the iterations and the work item stack in favor of the work item pool. The book primarily focuses on the basic DAD process.

The only complaint I have about the book is that the diagrams showing the Disciplined Agile Delivery life cycle - Basic, and the Disciplined Agile Delivery life cycle - Advanced should have been full page diagrams. They are too small to read in the book. It is not really a big deal since they are available on the web.

The book is really well written. It is very detailed and also entertaining making very easy to read. Throughout the book "Lessons from the Trenches" sidebars bring real world experience to the topics being covered.

The authors also include a case study for each of the phases they cover based on a project that builds a point of sale system. This gives the reader the opportunity to see the artifact creating activities in action.

All in all I found the book to be an excellent resource for the agilist looking to move beyond small develop teams. It is an absolute must read for enterprise architects and other senior management working in the IT shop.
13 of 16 people found the following review helpful
Many "agile" buzzwords describing a 30 year old process Jan. 23 2013
By Rony Atoun - Published on Amazon.com
Format: Kindle Edition Verified Purchase
Ultimately, when you strip the text of the agile terminology, what you get is an anecdotal description of a standard iterative approach, much better delivered in books like Walker Royce's "Software Project Management - A Unified framework". It reiterates what many software professionals already know: "Iterative" done right is agile. Worse, it brings no concrete metrics to back any of the claims and recommendations. The book addresses another well known fact: Traditional agile (usually meaning Scrum) does not scale up well for Enterprise IT projects requiring large project teams and delivering complex solutions.
The only redeeming value I found in the book is that it concentrates many well known engineering and Project Management best practices, but then again, books like Capers Jones's "Software Engineering Best Practices" do it better and back their findings with facts from well researched studies.
6 of 7 people found the following review helpful
Finally, someone made an agile strategy for the enterprise. Aug. 16 2012
By Shane Willerton - Published on Amazon.com
Format: Paperback
Disciplined Agile Delivery (DAD) adds yet another agile `flavor' to the many currently floating out there. What differentiates DAD from the other Agile flavors is that it incorporates many of the best practices of the non-Agile methodologies in order to achieve what the authors refer to as `Agility@scale'. Too often, agile practices can involve starting from scratch and working in a vacuum. This will work well for small, self-organizing teams working on isolated software development. For the rest of us working in Enterprise I.T., working on small, isolated teams is simply not an option. The integration points too many, the effort too large, infrastructure too intensive or costly and the co-ordination costs are high.
This is where DAD steps in. The authors ambitiously strive to seek a balance between the best of the Agile and Non-Agile project management body of knowledge. Their emphasis is on delivering solutions, not just software. Also, the authors also note the wisdom of leveraging existing infrastructure and enterprise solutions without building from scratch. This is still an Agile approach but one focused more on realities of the medium to large I.T. implementations rather than the small ones. Whereas most Agile approaches strive to keep teams as small as possible, this approach attempts to scale them up for larger projects by creating (potentially) multiple small teams but by putting in place a minimalist project management co-ordination necessary to keep those teams working for the same goals. The authors leverage Lean practices, Extreme Programming (XP), Open Unified Process (OpenUp), Scrum, Agile Modeling and Agile Data approaches, as well as a number of other sources, to scale up the successes that Agile approaches have had on smaller implementations.

All in all, this is a very good book on a very much needed topic. With all the acronyms and frequent project manager-speak, it can be a little rough of a read. This is a good choice for a Project Manager or Team Lead who is struggling to fit their enterprise effort into the small teams recommended by most Agile methods.
4 of 4 people found the following review helpful
Poor coverage of scaling Agile to the Enterprise Sept. 16 2013
By JWM - Published on Amazon.com
Format: Kindle Edition Verified Purchase
Did not cover either the Portfolio or Program levels of Agile infrastructure. Same old info about Agile teams as has been covered before. Uses the Lean buzz word but does not cover Lean innovations like VSD to improve the process or deliverables.
1 of 1 people found the following review helpful
The scaling Agile wars are over and DAD and SAFe won. (despite Ken Schwaber's sour grapes) Sept. 7 2013
By Steven Mather - Published on Amazon.com
Format: Kindle Edition Verified Purchase
DAD provides more piratical 'how to' solutions than a framework like SAFe that is more prescriptive. Agile at scale or for the enterprise does require some prescriptive practices due to the complexities involved. SAFe provides a core framework whereas DAD is very non prescriptive by saying that in a given scenario here are some options of how to resolve a scenario. What I think we will see is a compounded solution for scaling Agile. SAFe will act as the core framework and DAD will provide practical augmentation.

Scott has done a fantastic job of identifying the patterns we face in scaling and this book will be a classic reference for some time.