Introduction
The Disciplined Agile Delivery (DAD) Framework is a process decision framework that provides lightweight guidance to help teams make their own process decisions. Created by Scott Ambler and Mark Lines, DAD recognizes that “context counts” – every team is unique and faces different situations. Unlike prescriptive methodologies, DAD offers a toolkit of strategies and practices, allowing teams to choose what works best for their specific context. It extends beyond construction to address the full delivery lifecycle, making it essential for enterprise agile transformations and complex software delivery environments.
Core Concepts & Principles
The Four Foundational Principles
- People First: Teams are made up of people, and people are the primary determinant of success
- Learning Oriented: Teams should experiment and learn continuously to improve
- Full Delivery Lifecycle: Address all aspects from project initiation to deployment and operations
- Enterprise Awareness: Teams operate within organizational and enterprise constraints
Key DAD Beliefs
- Context Counts: Every team situation is unique and requires tailored approaches
- Choice is Good: Multiple ways exist to achieve the same outcome
- Optimize Flow: Focus on delivering working solutions efficiently
- Pragmatic: Balance idealism with practical business realities
The Three Phases Philosophy
- Inception: Identify stakeholders, scope, and approach
- Construction: Build consumable solutions incrementally
- Transition: Deploy solutions into production successfully
Step-by-Step Implementation Process
Phase 1: Inception (Team Storm-and-Form)
- Identify Stakeholders: Map all people affected by or affecting the solution
- Define Initial Scope: Establish high-level requirements and constraints
- Form Team: Assemble team members with necessary skills
- Align on Vision: Create shared understanding of project goals
- Initial Risk Assessment: Identify and plan for major risks
- Choose Architecture Strategy: Select technical approach and tooling
Phase 2: Construction (Prove Architecture Early)
- Establish Development Rhythm: Set iteration/sprint cadence
- Implement Core Architecture: Build foundation early
- Develop Incrementally: Deliver working software regularly
- Validate Continuously: Get stakeholder feedback frequently
- Evolve Requirements: Adapt scope based on learning
- Maintain Technical Excellence: Ensure code quality and documentation
Phase 3: Transition (Deploy with Confidence)
- Finalize Solution: Complete remaining functionality
- User Acceptance Testing: Validate solution meets needs
- Production Readiness: Ensure infrastructure and operations support
- Deploy Solution: Move to production environment
- Support Handoff: Transfer to operations/maintenance team
- Retrospective: Capture lessons learned for future projects
Key Techniques & Tools by Category
Process Blade Categories
Disciplined DevOps Layer
| Process Blade | Purpose | Key Practices |
|---|---|---|
| Continuous Integration | Integrate work frequently | Automated builds, testing, code quality checks |
| Continuous Deployment | Release frequently | Automated deployment pipelines, feature toggles |
| Database Management | Manage data effectively | Database refactoring, data migration strategies |
| Configuration Management | Manage environments | Infrastructure as code, environment consistency |
Value Stream Layer
| Process Blade | Purpose | Key Practices |
|---|---|---|
| Architecture Strategy | Guide technical decisions | Architecture modeling, technology selection |
| Product Management | Maximize product value | Roadmap planning, stakeholder collaboration |
| Data Management | Govern data assets | Data modeling, privacy compliance, quality assurance |
| Security | Build secure solutions | Threat modeling, security testing, compliance |
Role Definitions
Primary Roles
- Product Owner: Represents stakeholder community, prioritizes work
- Team Lead: Agile/servant leader, removes impediments, facilitates
- Team Member: Delivers solution, cross-functional contributor
- Architecture Owner: Guides architectural decisions, mentors team
- Stakeholder: Anyone affected by or who affects the solution
Supporting Roles
- Specialist: Subject matter expert in specific domain
- Independent Tester: Validates solution quality
- Integrator: Coordinates integration activities
- Domain Expert: Provides business knowledge and validation
Lifecycle Options
Agile Lifecycles Comparison
| Lifecycle | Best For | Characteristics | Team Size |
|---|---|---|---|
| Scrum-based | Co-located teams, stable requirements | Sprint-based, ceremonies | 5-9 people |
| Kanban-based | Continuous flow, maintenance | Pull-based, WIP limits | Variable |
| Continuous Delivery | DevOps mature, frequent releases | Pipeline-focused | Variable |
| Lean Startup | High uncertainty, innovation | Hypothesis-driven, pivoting | Small |
| Program | Large initiatives | Multiple coordinated teams | 10-100+ people |
Process Decision Points
Major Decision Categories
Lifecycle Decisions
- Iteration Length: 1-4 weeks based on team maturity and stakeholder needs
- Release Frequency: From daily to quarterly based on business needs
- Work Item Size: Stories, features, or epics based on complexity
- Planning Horizon: Sprint, release, or roadmap level planning
Technical Decisions
- Architecture Approach: Emergent vs. intentional architecture
- Testing Strategy: Manual, automated, or hybrid approaches
- Documentation: Minimal viable, comprehensive, or just enough
- Tool Selection: Open source, commercial, or hybrid toolchain
Team Organization Decisions
- Team Structure: Feature teams, component teams, or hybrid
- Skill Distribution: Specialists, generalists, or T-shaped professionals
- Location Strategy: Co-located, distributed, or hybrid
- Coordination Approach: Scrum of Scrums, scaling frameworks, or custom
Comparison Tables
DAD vs Other Frameworks
| Framework | Scope | Prescriptiveness | Lifecycle Coverage | Enterprise Focus |
|---|---|---|---|---|
| DAD | Full delivery | Guidance-based | Complete | High |
| Scrum | Development | Prescriptive | Construction only | Low |
| SAFe | Enterprise | Highly prescriptive | Complete | Very High |
| LeSS | Large Scale | Moderately prescriptive | Construction focus | Medium |
| Spotify Model | Organization | Descriptive | Organizational | Medium |
Measurement & Metrics
| Category | Metrics | Purpose | Frequency |
|---|---|---|---|
| Team Performance | Velocity, cycle time, quality | Team improvement | Weekly/Sprint |
| Solution Quality | Defect rates, technical debt | Product health | Continuous |
| Stakeholder Value | Customer satisfaction, ROI | Business alignment | Monthly/Release |
| Process Effectiveness | Lead time, flow efficiency | Process optimization | Continuous |
Common Challenges & Solutions
Challenge: Stakeholder Alignment
Symptoms: Conflicting priorities, scope creep, unclear requirements Solutions:
- Regular stakeholder demos and feedback sessions
- Clear product ownership and decision-making authority
- Transparent backlog prioritization process
- Structured change management procedures
Challenge: Technical Debt Accumulation
Symptoms: Slowing velocity, increasing defects, maintenance burden Solutions:
- Allocate 15-20% of capacity to technical debt reduction
- Implement definition of done that includes quality standards
- Regular architecture reviews and refactoring
- Automated code quality monitoring and gates
Challenge: Scaling Coordination
Symptoms: Integration issues, duplicate work, communication gaps Solutions:
- Clear interface definitions between teams
- Regular cross-team synchronization meetings
- Shared architectural vision and standards
- Communities of practice for knowledge sharing
Challenge: Enterprise Constraints
Symptoms: Compliance requirements, legacy systems, organizational resistance Solutions:
- Enterprise-aware practices and governance alignment
- Incremental transformation approach
- Clear compliance and audit trails
- Change management and communication strategies
Best Practices & Practical Tips
Team Formation Tips
- Skills Balance: Ensure T-shaped professionals with both depth and breadth
- Size Optimization: Keep teams between 5-11 members for optimal communication
- Co-location Preference: Physical proximity improves collaboration when possible
- Psychological Safety: Create environment where team members can express concerns
Stakeholder Engagement
- Regular Touchpoints: Weekly demos, monthly reviews, quarterly planning
- Multiple Channels: Formal meetings, informal conversations, collaboration tools
- Visual Communication: Use models, prototypes, and working software
- Feedback Loops: Short cycles for validation and course correction
Quality Practices
- Test-Driven Development: Write tests before code for better design
- Continuous Integration: Integrate code changes multiple times daily
- Code Reviews: Peer review all code changes before integration
- Definition of Done: Clear criteria for completed work items
Risk Management
- Early Risk Identification: Address architectural and technical risks first
- Spike Solutions: Time-boxed investigations for high-risk items
- Incremental Delivery: Reduce risk through frequent value delivery
- Stakeholder Validation: Regular confirmation of solution direction
Implementation Strategies
Getting Started Approach
- Assessment: Evaluate current team maturity and organizational context
- Training: Provide DAD framework education to team and stakeholders
- Pilot Project: Apply DAD to single team/project for learning
- Retrospective: Capture lessons and adjust approach
- Scale Gradually: Expand to additional teams based on success
Common Adoption Patterns
- Bottom-Up: Teams adopt practices organically, scales through success
- Top-Down: Leadership mandates adoption with training and support
- Middle-Out: Project managers and coaches drive transformation
- Hybrid: Combination approach based on organizational dynamics
Success Factors
- Leadership Support: Executive sponsorship and resource commitment
- Coach Availability: Experienced practitioners to guide teams
- Cultural Readiness: Organization openness to experimentation and change
- Measurement Focus: Clear metrics to track progress and success
Process Blade Deep Dive
Critical Process Blades for Success
Inception Activities
- Stakeholder Analysis: Identify all affected parties and their needs
- Vision Creation: Develop shared understanding of solution goals
- Risk Assessment: Identify technical, business, and organizational risks
- Team Formation: Assemble necessary skills and establish working agreements
Construction Activities
- Requirements Modeling: Capture and evolve solution requirements
- Solution Architecture: Design and evolve technical architecture
- Programming: Implement solution using quality practices
- Testing: Validate solution meets requirements and quality standards
Transition Activities
- Solution Deployment: Move solution to production environment
- User Training: Prepare end users for solution adoption
- Support Documentation: Create materials for ongoing maintenance
- Lessons Learned: Capture insights for future projects
Resources for Further Learning
Essential Reading
- “Disciplined Agile Delivery” by Scott Ambler and Mark Lines
- “An Executive’s Guide to Disciplined Agile” by Scott Ambler and Mark Lines
- “Choose Your WoW!” by Scott Ambler and Mark Lines
- “The Disciplined Agile Framework” online resources at disciplinedagile.org
Online Resources
- Disciplined Agile Consortium: Official community and resources
- DA Browser: Interactive tool for exploring process decisions
- PMI Disciplined Agile: Professional certification and training programs
- Scott Ambler’s Blog: Regular insights and updates on DA practices
Training & Certification
- Disciplined Agile Scrum Master (DASM): Entry-level certification
- Disciplined Agile Senior Scrum Master (DASSM): Advanced practitioner level
- Disciplined Agile Coach (DAC): Expert-level coaching certification
- Local Training Providers: PMI Authorized Training Partners worldwide
Tools & Platforms
- DA Browser: Process decision support tool
- Azure DevOps: Microsoft’s application lifecycle management platform
- Jira: Atlassian’s project management and issue tracking
- Confluence: Documentation and collaboration platform
Community Resources
- LinkedIn Groups: Disciplined Agile communities and discussions
- Local Meetups: Face-to-face learning and networking opportunities
- Conferences: Agile Alliance, PMI, and DA-specific events
- Podcasts: Disciplined Agile Podcast and related agile content
Remember: DAD is about making informed process decisions based on your unique context. Start with the fundamentals, experiment with practices, measure results, and continuously adapt your approach. The goal is not to follow DAD perfectly, but to use it as a guide for building your team’s optimal way of working.