- Series: IBM Press
- Paperback: 544 pages
- Publisher: IBM Press; 1 edition (June 2, 2012)
- Language: English
- ISBN-10: 0132810131
- ISBN-13: 978-0132810135
- Product Dimensions: 7 x 1.3 x 8.9 inches
- Shipping Weight: 1.9 pounds (View shipping rates and policies)
- Average Customer Review: 25 customer reviews
- Amazon Best Sellers Rank: #178,659 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.
Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise (IBM Press) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
All Books, All the Time
Read author interviews, book reviews, editors picks, and more at the Amazon Book Review. Read it now
Frequently bought together
Customers who bought this item also bought
“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.
Top customer reviews
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.
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.
This book is essential reading for managers in the software space, IMO. Scott and Mike manage to describe the principles and practices of DAD in a manner that does not come across as evangelistic like so many Agile books and proponents do. They are frank about the complexities of modern business and acknowledge the shortcomings and the advantages of both Agile and traditional methods. Their DAD framework is customisable with excellent advice and practical examples on how to implement it in the real world. They readily acknowledge that 'one size does NOT fit all' and that the same goes for Agile. It's clear they speak from years of experience and are experts in this domain.
If you want a book that describes both principles and practices, gives you guidance, options and suggestions without evangelistic and dogmatic decrees, then this is the book for you. It covers software delivery in an end to end fashion and will find a permanent place on my virtual bookcase.
If you are looking for an overview, start with Scott and Mark's other book first "Introduction to Disciplined Agile Delivery". When you are ready for details, get this book. Plan to read it a little at a time over several weeks to give yourself time to think about each part and let it sink in.