Disciplined Agile Delivery

Disciplined Agile Delivery
Name	Disciplined Agile Delivery
Abbreviation	DAD
Type	Agile software development framework
Originated	2012
Developer	Project Management Institute

Disciplined Agile Delivery Disciplined Agile Delivery is a hybrid process decision framework for software delivery that combines practices from multiple sources to address enterprise-scale concerns. It integrates strategies from sources associated with Scrum (software development), Extreme Programming, Kanban (development), Lean manufacturing, and Unified Process to provide a context-sensitive approach to delivery. The framework is positioned to support diverse organizational environments such as those seen in Microsoft, IBM, Accenture, Deloitte and other large-scale technology organizations.

Overview

Disciplined Agile Delivery presents a toolkit of practices and life-cycle choices intended to guide teams through inception, construction, and transition activities while allowing tailoring to organization-specific constraints. It synthesizes elements drawn from Scrum (software development), Extreme Programming, Feature-Driven Development, Kanban (development), Lean software development, and the Rational Unified Process lineage championed by IBM. The framework emphasizes enterprise awareness and governance compatible with Project Management Institute, TOGAF, COBIT, and standards used by Amazon (company), Google, Facebook, and other technology firms.

History and Development

Disciplined Agile Delivery emerged from work by practitioners influenced by the Agile software development movement sparked at the Snowbird (Utah) meeting that produced the Manifesto for Agile Software Development. Early contributors referenced techniques popularized by Ken Schwaber, Jeff Sutherland, Kent Beck, and Martin Fowler. It evolved through contributions by consulting organizations and authors with ties to Scott Ambler and Mark Lines before formal adoption discussions with Project Management Institute. Subsequent editions incorporated guidance for scaling influenced by initiatives such as Scaled Agile Framework, Large-scale Scrum, and enterprise efforts from Microsoft Azure DevOps adopters.

Principles and Practices

The framework articulates principles that combine lean, agile, and pragmatic governance, advocating for context-driven decision-making supported by strategies from Lean manufacturing pioneers like Taiichi Ohno and W. Edwards Deming. Practices include iterative planning and continuous integration inspired by Jenkins (software), test-driven development popularized by Kent Beck, pair programming associated with Extreme Programming, and incremental architecture approaches seen in Martin Fowler's writing. Governance and enterprise awareness reference models such as COBIT, TOGAF, and ITIL to align teams with organizational risk, compliance, and security concerns as practiced in large enterprises like Oracle Corporation and SAP SE.

Life Cycle and Process Goals

Disciplined Agile Delivery defines life-cycle phases—Inception, Construction, Transition—that mirror stages from the Rational Unified Process while offering alternatives including exploratory and continuous delivery life cycles similar to patterns used at Netflix (service) and Amazon (company). Process goals map to outcomes like initial funding approval, architecture enablers, and release readiness, incorporating continuous deployment practices influenced by Jez Humble and Dave Farley. The life-cycle options accommodate regulatory environments referencing frameworks used by Financial Industry Regulatory Authority participants and development models applied in NASA projects.

Roles and Responsibilities

Roles in the framework blend familiar agile positions with enterprise-oriented responsibilities. Team-level roles such as Product Owner (a role aligned with Scrum (software development) practices), Team Lead, and Architecture Owner coexist with enterprise roles like Portfolio Manager, Enterprise Architect, and Compliance Officer—titles parallel to positions at Microsoft, Google, IBM, and Accenture. The framework highlights cross-functional teams that incorporate testing, operations, and security specialists akin to practices promoted by DevOps advocates like Gene Kim and organizations adopting Continuous integration pipelines.

Adoption and Tooling

Adoption guidance recommends tailoring the framework to organizational context, leveraging tooling ecosystems such as JIRA (software), Azure DevOps, GitHub, GitLab, Jenkins (software), and Atlassian products to support planning, version control, and automation. Training and certification pathways have been offered by Project Management Institute and consulting firms with programs comparable to certifications from Scrum Alliance, Scaled Agile, Inc., and vendor courses provided by IBM. Enterprise integrations frequently coordinate with portfolio management tools used at SAP SE and Oracle Corporation installations.

Criticism and Evaluation

Critics argue that the framework's synthesis approach can produce complexity and prescriptive decision catalogs that mirror criticisms leveled at Scaled Agile Framework and extensive processes such as the Rational Unified Process. Some practitioners contrast its enterprise governance emphasis with purist agile stances advocated by figures like Alistair Cockburn and Mike Cohn, suggesting potential tension between agility and compliance. Evaluations by consultancy and industry analysts compare adoption outcomes across organizations including Deloitte, McKinsey & Company, and Gartner reports, noting variability in effectiveness dependent on leadership, culture, and tooling environments.

Category:Software development methodologies