PMI-ACP Domain 4: Delivery (28%) - Complete Study Guide 2027

Domain 4 Overview: What is Delivery?

PMI-ACP Domain 4: Delivery represents the largest portion of the exam alongside Domain 1: Mindset, accounting for 28% of all scored questions. This domain focuses on the practical execution of agile projects, encompassing planning, implementation, quality assurance, and continuous improvement practices that drive successful project outcomes.

The Delivery domain emphasizes hands-on agile practices that practitioners must master to successfully deliver value to customers. Unlike the more conceptual aspects covered in other domains, Domain 4 tests your understanding of specific techniques, tools, and methodologies used in day-to-day agile project execution.

Key Delivery Concepts and Terminology

Understanding core delivery terminology is essential for exam success. The PMI-ACP exam difficulty often stems from nuanced differences between similar concepts across different agile methodologies.

Fundamental Delivery Terms

• Sprint/Iteration: Time-boxed development cycles, typically 1-4 weeks in duration
• Velocity: Measure of team's delivery capacity over time
• Burndown Chart: Visual representation of work remaining versus time
• Definition of Done (DoD): Shared understanding of work completion criteria
• Working Agreement: Team-established norms and practices
• Cadence: Regular rhythm of team activities and ceremonies
• Lead Time: Total time from request to delivery
• Cycle Time: Time to complete work once started

Agile Planning Levels

Planning Level	Time Horizon	Primary Focus	Key Artifacts
Strategic	6-12 months	Vision, Roadmap	Product Vision, Release Plan
Release	2-6 months	Feature Sets	Release Backlog, Roadmap
Iteration	1-4 weeks	User Stories	Sprint Backlog, Tasks
Daily	24 hours	Task Completion	Task Board, Impediments

Agile Planning Approaches

Effective agile planning balances flexibility with predictability. The exam tests your knowledge of various planning techniques and when to apply them appropriately.

Story Mapping and User Story Prioritization

Story mapping provides a visual approach to organizing user stories based on user journey and business value. This technique helps teams understand the bigger picture while planning incremental delivery.

Estimation Techniques

• Planning Poker: Consensus-based estimation using relative sizing
• T-Shirt Sizing: High-level estimation using size categories (XS, S, M, L, XL)
• Affinity Estimation: Silent grouping of similar-sized items
• Dot Voting: Quick prioritization technique using dots or stickers
• #NoEstimates: Movement advocating for delivery without traditional estimation

Release Planning Strategies

Release planning connects product strategy with delivery execution. Teams must balance feature completeness, quality standards, and market timing when planning releases.

Key release planning considerations include:

• Minimum Viable Product (MVP) definition
• Feature prioritization matrices (MoSCoW, Kano Model)
• Dependencies and constraints analysis
• Risk assessment and mitigation planning
• Stakeholder communication and expectation setting

Execution and Implementation Practices

Domain 4 heavily emphasizes practical execution techniques across different agile frameworks. Understanding when and how to apply specific practices is crucial for exam success.

Scrum Implementation Practices

Scrum remains the most widely adopted agile framework, and the exam extensively covers its ceremonies, artifacts, and roles in delivery contexts.

Kanban Flow Management

Kanban emphasizes continuous flow and work-in-progress (WIP) limits. Key concepts include:

• WIP Limits: Constraints on work items in each process stage
• Pull Systems: Work initiated based on capacity, not schedule
• Flow Efficiency: Ratio of value-adding time to total lead time
• Cumulative Flow Diagrams: Visual representation of work flow over time

Extreme Programming (XP) Technical Practices

XP contributes essential technical practices that support high-quality delivery:

• Test-Driven Development (TDD)
• Pair Programming and Mob Programming
• Continuous Integration and Deployment
• Refactoring and Code Quality
• Simple Design and YAGNI (You Aren't Gonna Need It)

Quality Assurance and Testing

Quality is built into agile delivery processes rather than inspected at the end. The exam tests understanding of various quality practices and their integration into delivery workflows.

Testing Strategies in Agile

Agile testing approaches include:

• Test Automation: Automated unit, integration, and acceptance tests
• Behavior-Driven Development (BDD): Specification by example using natural language
• Acceptance Test-Driven Development (ATDD): Defining acceptance criteria before development
• Exploratory Testing: Simultaneous learning, test design, and execution
• Risk-Based Testing: Focusing testing efforts on highest-risk areas

Definition of Done (DoD)

The Definition of Done ensures consistent quality standards across all delivered work. A comprehensive DoD typically includes:

• Code written and peer-reviewed
• Unit tests created and passing
• Integration tests passing
• Acceptance criteria met
• Documentation updated
• Code deployed to staging environment
• Product Owner acceptance obtained

Metrics and Progress Tracking

Agile metrics support transparency and continuous improvement rather than micromanagement. The exam covers various measurement approaches and their appropriate applications.

Team Performance Metrics

Metric	Purpose	Frequency	Primary Users
Velocity	Planning & Forecasting	Per Sprint	Team, Product Owner
Burndown	Progress Tracking	Daily	Team, Scrum Master
Lead Time	Flow Optimization	Per Item	Team, Management
Cycle Time	Process Efficiency	Per Item	Team, Process Owners
Defect Rate	Quality Monitoring	Per Sprint/Release	Team, Quality Assurance

Information Radiators

Visual management tools promote transparency and shared understanding. Common information radiators include:

• Task Boards: Visual representation of work status
• Burndown/Burnup Charts: Progress visualization
• Team Working Agreements: Shared norms and practices
• Impediment Lists: Current blockers and resolution status
• Release Roadmaps: High-level delivery timeline

Risk Management in Agile Delivery

Agile approaches manage risk through short feedback loops, early delivery, and adaptive planning rather than extensive upfront risk analysis.

Risk Identification and Mitigation

Common agile risk management practices include:

• Risk-Adjusted Backlog: Prioritizing high-risk items for early validation
• Spike Solutions: Time-boxed research to reduce technical uncertainty
• Minimum Viable Product (MVP): Early validation of core assumptions
• Fail-Fast Principles: Quick identification and resolution of failures
• Continuous Integration: Early detection of integration issues

Impediment Management

Impediments are obstacles that slow or stop team progress. Effective impediment management involves:

• Daily identification during standup meetings
• Categorization by type and impact
• Assignment of resolution ownership
• Tracking until complete resolution
• Root cause analysis for recurring impediments

Continuous Improvement Practices

Continuous improvement is fundamental to agile delivery success. The exam tests knowledge of various improvement techniques and their practical application.

Retrospective Techniques

Retrospectives drive team improvement through regular reflection and action planning. Popular retrospective formats include:

• Start/Stop/Continue: Identifying behaviors to change
• Glad/Sad/Mad: Emotional perspective on recent work
• 4Ls (Liked/Learned/Lacked/Longed For): Comprehensive reflection framework
• Sailboat: Visual metaphor for progress and obstacles
• 5 Whys: Root cause analysis technique

Kaizen and Process Optimization

Kaizen emphasizes small, continuous improvements over large, disruptive changes. In agile contexts, this translates to:

• Regular process refinement
• Elimination of waste (muda)
• Standardization of effective practices
• Experimentation with new techniques
• Measurement and validation of improvements

Study Strategies for Domain 4

Domain 4's practical focus requires hands-on understanding rather than memorization. Effective preparation strategies include:

Since Domain 4 represents such a significant portion of the exam, it's crucial to understand how it connects with other domains covered in the complete guide to all four content areas. The delivery practices you'll be tested on must be implemented within the context of the right mindset, effective leadership, and solid product management principles.

Recommended Study Approach

1. Framework Comparison: Create comparison matrices for Scrum, Kanban, XP, and SAFe practices
2. Practice Application: Work through scenario-based questions that test practical application
3. Metric Calculation: Practice calculating velocity, burn rates, and cycle times
4. Tool Familiarity: Understand common agile tools and their applications
5. Case Study Analysis: Review real-world examples of successful agile delivery

Consider utilizing practice tests that specifically focus on Domain 4 scenarios. The practical nature of this domain makes simulation-based learning particularly effective.

Sample Questions and Explanations

Understanding the types of questions you'll encounter helps focus your preparation efforts. Here are examples of Domain 4 question styles:

Scenario-Based Question Example

Question: A Scrum team's velocity has been consistently declining over the past three sprints. The team reports increasing technical debt and longer testing cycles. What should the Scrum Master recommend?

Options:

• A) Extend sprint length to accommodate testing needs
• B) Allocate capacity each sprint for technical debt reduction
• C) Add more team members to increase capacity
• D) Remove testing from the Definition of Done

Correct Answer: B) Allocate capacity each sprint for technical debt reduction

Explanation: Technical debt requires systematic attention to prevent further degradation. Allocating specific capacity addresses root causes while maintaining quality standards.

Metrics Interpretation Question

Question: A team's cumulative flow diagram shows widening gaps between "In Progress" and "Done" columns. What does this indicate?

Correct Interpretation: This pattern suggests bottlenecks in the completion process, likely indicating WIP limits are too high or there are constraints in downstream processes.

For more comprehensive practice with these types of questions, the best PMI-ACP practice questions guide provides detailed explanations and additional examples specifically focused on Domain 4 scenarios.

Integration with Other Domains

Domain 4 doesn't exist in isolation. Successful delivery requires integration with concepts from other domains:

• Mindset Integration: Delivery practices must align with agile values and principles
• Leadership Connection: Servant leadership supports effective delivery team dynamics
• Product Alignment: Delivery execution must serve product vision and customer value

Understanding these interconnections is essential for answering complex scenario questions that span multiple domains. The comprehensive PMI-ACP study guide provides detailed guidance on managing these domain intersections effectively.

As you prepare for the exam, remember that success requires more than just memorizing practices and techniques. You need to understand when and how to apply different approaches based on team context, organizational culture, and project constraints.