Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise

  • 10h 16m
  • Mark Lines, Scott Ambler
  • IBM Press
  • 2012

It is widely recognized that moving from traditional to agile approaches to build software solutions is a critical source of competitive advantage. Mainstream agile approaches that are indeed suitable for small projects require significant tailoring for larger, complex enterprise projects. In Disciplined Agile Delivery, Scott W. Ambler and Mark Lines introduce IBM’s breakthrough Disciplined Agile Delivery (DAD) process framework, which describes how to do this tailoring. DAD applies a more disciplined approach to agile development by acknowledging and dealing with the realities and complexities of a portfolio of interdependent program initiatives.

Ambler and Lines show how to extend Scrum with supplementary agile and lean strategies from Agile Modeling (AM), Extreme Programming (XP), Kanban, Unified Process (UP), and other proven methods to provide a hybrid approach that is adaptable to your organization’s unique needs. They candidly describe what practices work best, why they work, what the trade-offs are, and when to consider alternatives, all within the context of your situation.

Disciplined Agile Delivery addresses agile practices across the entire lifecycle, from requirements, architecture, and development to delivery and governance. The authors show how these best-practice techniques fit together in an end-to-end process for successfully delivering large, complex systems--from project initiation through delivery.

Coverage includes

  • Scaling agile for mission-critical enterprise endeavors
  • Avoiding mistakes that drive poorly run agile projects to chaos
  • Effectively initiating an agile project
  • Transitioning as an individual to agile
  • Incrementally building consumable solutions
  • Deploying agile solutions into complex production environments
  • Leveraging DevOps, architecture, and other enterprise disciplines
  • Adapting your governance strategy for agile projects

Based on facts, research, and extensive experience, this book will be an indispensable resource for every enterprise software leader and practitioner--whether they’re seeking to optimize their existing agile/Scrum process or improve the agility of an iterative process.

About the Authors

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 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 UPMentors.com.

In this Book

  • Disciplined Agile Delivery in a Nutshell
  • Introduction to Agile and Lean
  • Foundations of Disciplined Agile Delivery
  • Roles, Rights, and Responsibilities
  • Forming Disciplined Agile Delivery Teams
  • The Inception Phase
  • Identifying a Project Vision
  • Identifying the Initial Scope
  • Identifying an Initial Technical Strategy
  • Initial Release Planning
  • Forming the Work Environment
  • Case Study: Inception Phase
  • The Construction Phase
  • Initiating a Construction Iteration
  • A Typical Day of Construction
  • Concluding a Construction Iteration
  • Case Study: Construction Phase
  • The Transition Phase
  • Case Study: Transition Phase
  • Governing Disciplined Agile Teams
  • Got Discipline?
SHOW MORE
FREE ACCESS

YOU MIGHT ALSO LIKE

Rating 4.5 of 39 users Rating 4.5 of 39 users (39)
Rating 5.0 of 1 users Rating 5.0 of 1 users (1)