Skip to content

PMI-ACP : Delivery (Domain 4)

PMI-ACP : Certified Agile Practitioner - Domain 4 - Delivery

25 questionsmedium

The PMI Agile Certified Practitioner (PMI-ACP) certification represents a broad, framework-agnostic validation of a professional’s ability to lead and execute within various agile environments. Domain 4, focused on Delivery (often integrated with Value-Driven Delivery and Team Performance in various Examination Content Outlines), is a critical pillar of the exam. This domain tests a practitioner’s capability to deliver high-value results through flow optimization, continuous validation, and proactive problem resolution.

This guide synthesizes information from leading industry resources and accredited training materials to provide a factually dense and comprehensive overview of the essential concepts required to master the Delivery domain.


1. The Agile Mindset and the Philosophy of Delivery

The foundation of agile delivery is not found in a specific toolset, but in the Agile Manifesto and its twelve underlying principles. Successful delivery requires moving beyond simply “doing agile”—which involves following rituals—to “being agile,” which necessitates an internal transformation of how value is perceived and realized.

The Value-Driven Approach

Agile delivery prioritizes the realization of value early and often. Unlike traditional predictive models, agile frameworks seek to deliver functional increments to stakeholders throughout the project lifecycle. This approach reduces the “talent gap” and ensures that the project remains aligned with shifting market needs, which is particularly relevant in high-growth industries like digital transformation, software development, and healthcare.

Servant Leadership in Delivery

Delivery is facilitated by a servant-leadership model. In this context, the practitioner’s role is to support the team by “carrying food and water”—an analogy for removing impediments and providing the necessary resources for the team to succeed. Servant leadership focuses on fostering an environment where individuals and interactions are prioritized over processes and tools, ensuring that the team can maintain a sustainable pace of high-quality delivery.


2. Framework-Agnostic Execution: Scrum, Kanban, and XP

The PMI-ACP is unique because it does not limit delivery to a single methodology. A master practitioner must understand how to apply and combine various frameworks based on the specific needs of the project.

The Scrum Framework

Scrum is the most widely adopted agile framework and is characterized by its specific roles (Product Owner, Scrum Master, and Team) and time-boxed iterations known as Sprints. Delivery in Scrum is managed through ceremonies:

  • Sprint Planning: Setting the delivery goals for the iteration.
  • Daily Scrum: A brief daily coordination meeting focused on progress and blockers.
  • Sprint Review: A demonstration of the increment to stakeholders to validate value.
  • Sprint Retrospective: An internal team meeting focused on process improvement.

Extreme Programming (XP)

XP is heavily focused on technical excellence and high-quality software delivery. It introduces specific practices that ensure continuous validation, such as pair programming, collective ownership, and a rigorous focus on testing. XP principles are often integrated into other frameworks to improve the technical robustness of the delivered product.

Kanban and Lean

Kanban focuses on the continuous flow of work rather than fixed iterations. It is a visual system for managing work as it moves through various stages of a process. Lean thinking, which underpins Kanban, emphasizes the elimination of waste and the optimization of the entire value stream. In a delivery context, Kanban is used to identify bottlenecks and ensure that the team is not overwhelmed by an excessive amount of work in progress.


3. Optimizing Execution Flow and WIP Limits

Flow optimization is the practice of ensuring that work moves through the delivery pipeline as efficiently as possible. This is primarily achieved by managing Work in Progress (WIP) and applying the principles of Little’s Law.

Little’s Law and WIP Limits

Little’s Law provides a mathematical foundation for understanding flow. While practitioners need not always perform complex calculations on the exam, they must understand the relationship between WIP, cycle time, and throughput.

  • WIP Limits: By restricting the amount of work the team can take on at any one time, teams can reduce multitasking and context switching.
  • The Relationship: Reducing WIP generally leads to a decrease in cycle time (the time it takes for a single item to move from start to finish), which in turn improves the predictability and speed of delivery.

Identifying Bottlenecks

Flow optimization requires a constant awareness of where work is piling up. Visualizing the workflow—often through a Kanban board or information radiators—allows the team to see where the process is stalled. Addressing these bottlenecks is a core responsibility of the agile practitioner to ensure a steady stream of value delivery.


4. Continuous Validation: TDD, CI/CD, and Refactoring

To ensure that delivery is not just fast but also high-quality, agile teams employ continuous validation techniques. These practices are designed to detect problems as early as possible in the lifecycle.

Test-Driven Development (TDD)

TDD is a technical practice where tests are written before the actual code. This ensures that the delivery is guided by requirements and that the resulting increment is naturally verified. TDD fosters a “fail fast” mentality, allowing the team to identify and resolve defects immediately.

Continuous Integration and Continuous Delivery (CI/CD)

CI/CD refers to the automated process of merging code changes and delivering them to a testing or production environment.

  • Continuous Integration (CI): Developers frequently merge their changes into a central repository, where automated builds and tests are run.
  • Continuous Delivery (CD): The practice of ensuring that the code is always in a deployable state, allowing for rapid releases to the customer.

Refactoring

Refactoring is the process of improving the internal structure of the code or product without changing its external behavior. It is a critical practice for maintaining the “Definition of Done” and ensuring that technical debt does not accumulate and impede future delivery cycles.


5. Agile Metrics: Velocity, Cycle Time, and Throughput

Agile delivery relies on empirical data to measure performance and predict future outcomes. Practitioners must distinguish between metrics that track activity and those that measure actual value delivery.

Velocity

Velocity is a measure of the amount of work a team can complete during a single iteration (Sprint). It is typically measured in story points or hours. While velocity is useful for internal team planning and estimating future capacity, it should not be used as a tool for comparing different teams, as story points are relative to each specific team’s estimation.

Cycle Time vs. Lead Time

  • Cycle Time: The amount of time an item spends in the “working” state until it is completed. It measures the efficiency of the team’s internal process.
  • Lead Time: The total time from when a request is made until it is delivered to the customer. This provides a stakeholder-centric view of delivery speed.

Throughput

Throughput measures the number of items delivered over a specific period. This metric is essential for Kanban-based teams to understand their capacity and set realistic expectations for stakeholders.


6. Proactive Risk Management in Delivery

Risk in an agile project is managed through transparency, frequent validation, and specific architectural or experimental tasks.

Spikes: Architectural and Functional

A “spike” is a time-boxed effort used to research a technical or functional uncertainty.

  • Architectural Spikes: Used to explore technical feasibility or evaluate a new tool.
  • Functional Spikes: Used to understand a complex requirement or user story. Spikes reduce risk by providing the team with the knowledge needed to estimate and execute work more accurately.

Risk-Adjusted Backlogs

In agile delivery, the Product Backlog is not static. A risk-adjusted backlog incorporates risk response activities (such as spikes or mitigation tasks) alongside functional user stories. By prioritizing these items, the team ensures that high-risk elements are addressed early in the project, preventing late-stage failures.

Risk Burnup Charts

A risk burnup chart provides a visual representation of the total “risk exposure” of a project over time. As risks are identified, mitigated, or retired, the chart shows the effectiveness of the team’s risk management strategies. This is a critical information radiator for stakeholders concerned with project stability.


7. Lean Thinking and Waste Reduction

Agile delivery is deeply rooted in Lean principles, which focus on delivering value by eliminating “muda” (waste). Waste reduction is essential for maintaining a high velocity and ensuring team performance.

The Seven Wastes of Lean

In a delivery context, waste includes anything that does not add value to the final product. Common examples include:

  • Partially done work: Work that is not completed and therefore cannot provide value.
  • Extra processes: Unnecessary steps or documentation that do not improve the product.
  • Task switching: The time lost when team members move between unrelated tasks.
  • Waiting: Delays caused by dependencies or slow approvals.
  • Defects: The cost of rework and fixing errors.

Value Stream Mapping

Value stream mapping is a technique used to visualize the entire process of delivery, from initial concept to final release. By mapping out every step, teams can identify areas where waste occurs and implement changes to streamline the flow of value to the customer.


8. Continuous Improvement through Retrospectives

The primary mechanism for improving delivery is the retrospective. This ceremony allows the team to reflect on their processes and identify specific, actionable improvements for the next iteration.

The Retrospective Framework

A standard retrospective, as outlined by experts such as Esther Derby and Diana Larsen, typically follows a five-step structure:

  1. Set the Stage: Prepare the team and establish a safe environment.
  2. Gather Data: Create a shared picture of what happened during the iteration.
  3. Generate Insights: Identify patterns and root causes.
  4. Decide What to Do: Select one or two high-impact improvements to implement.
  5. Close the Retrospective: Summarize the meeting and appreciate the team’s efforts.

Fostering Psychological Safety

For a retrospective to be effective, team members must feel safe to speak honestly about failures. Agile practitioners must facilitate these meetings with emotional intelligence, ensuring that the focus remains on process improvement rather than assigning individual blame.


9. Root Cause Analysis: 5 Whys and Fishbone Diagrams

When delivery issues arise, teams must look beyond the symptoms to find the underlying cause. Root Cause Analysis (RCA) tools are vital for effective problem resolution.

The 5 Whys

The 5 Whys is a simple but powerful technique for uncovering the root cause of a problem. By asking “Why?” repeatedly (usually five times), the team can move past the surface-level excuse to the core systemic issue.

Fishbone (Ishikawa) Diagrams

The Fishbone diagram is a visual tool used to categorize the potential causes of a problem. Causes are typically grouped into categories such as People, Process, Tools, and Environment. This structured approach helps the team brainstorm and visualize the various factors contributing to a delivery failure, ensuring a comprehensive resolution.


10. Value-Driven Measurement and Scaling

Delivery must ultimately be measured by its impact on the organization and the customer. As projects grow in complexity, practitioners must also understand how to scale these delivery practices.

Outcome-Focused Measurement

While flow metrics (like velocity and cycle time) are important for team health, stakeholders are primarily interested in outcomes. This involves measuring:

  • Customer Satisfaction: Validated through reviews and feedback loops.
  • Return on Investment (ROI): Ensuring that the cost of delivery is justified by the value generated.
  • Net Promoter Score (NPS): A measure of customer loyalty and product success.

Scaling Frameworks

When multiple teams are working on a single product, delivery becomes more complex. Frameworks such as SAFe (Scaled Agile Framework), LeSS (Large-Scale Scrum), and DA (Disciplined Agile) provide structures for coordinating multiteam environments. These frameworks ensure that despite the increased scale, the teams remain aligned with the agile mindset and maintain a continuous flow of value.

DevOps and DORA Metrics

Modern agile delivery often integrates DevOps practices to bridge the gap between development and operations. The DORA (DevOps Research and Assessment) metrics provide a standard for measuring the effectiveness of this integration:

  • Deployment Frequency: How often code is successfully released.
  • Lead Time for Changes: The time it takes to go from code committed to code running in production.
  • Change Failure Rate: The percentage of deployments that cause a failure in production.
  • Time to Restore Service: How quickly the team can recover from a failure.

Study Questions and Answer Key

Short-Answer Questions

  1. What is the primary purpose of a “Spike” in agile delivery?
  2. How does limiting Work in Progress (WIP) affect cycle time according to Little’s Law?
  3. In the context of the 5 Whys technique, what is the goal of asking “why” multiple times?
  4. What is the difference between Lead Time and Cycle Time?
  5. What role does refactoring play in the agile delivery process?
  6. Why is Test-Driven Development (TDD) considered a “fail fast” practice?
  7. What are the five steps of a successful retrospective?
  8. What is the main objective of Value Stream Mapping?
  9. How does a risk-adjusted backlog differ from a standard product backlog?
  10. What is the significance of the “Definition of Done”?

Detailed Answer Key

  1. Answer: The primary purpose of a spike is to perform research or prototyping to reduce technical or functional uncertainty. Explanation: By spending a time-boxed amount of effort on a spike, the team can gain the knowledge necessary to estimate or execute complex tasks more effectively.
  2. Answer: Limiting WIP generally results in a decrease in cycle time. Explanation: According to the principles of Little’s Law, reducing the number of items being worked on simultaneously reduces multitasking and context switching, which allows individual items to move through the process faster.
  3. Answer: The goal is to move past surface-level symptoms to identify the underlying systemic root cause of an issue. Explanation: By repeatedly questioning why a failure occurred, teams can address the core problem rather than just applying a temporary fix to a symptom.
  4. Answer: Lead Time measures the duration from the initial request to final delivery, while Cycle Time measures the duration from when work actually starts to when it is completed. Explanation: Lead Time is a customer-centric metric reflecting total wait time, whereas Cycle Time is a process-centric metric reflecting team efficiency.
  5. Answer: Refactoring involves improving the internal structure of a product without changing its external functionality to maintain quality and reduce technical debt. Explanation: It ensures the product remains easy to maintain and extend, preventing the accumulation of “messy” code that could slow down future delivery.
  6. Answer: TDD requires writing tests before code, which means any logic errors or requirement misunderstandings are caught the moment the code is written. Explanation: This immediate feedback loop prevents defects from moving further down the delivery pipeline, making them much cheaper and easier to fix.
  7. Answer: Set the Stage, Gather Data, Generate Insights, Decide What to Do, and Close the Retrospective. Explanation: This structured framework ensures that the team moves logically from identifying what happened to implementing actionable improvements for the future.
  8. Answer: The objective is to visualize the entire flow of delivery to identify and eliminate non-value-added waste. Explanation: By seeing the end-to-end process, teams can pinpoint bottlenecks and unnecessary steps that do not contribute to customer value.
  9. Answer: A risk-adjusted backlog includes specific risk-reduction tasks and responses alongside traditional functional features. Explanation: This ensures that high-risk items are prioritized and addressed early, rather than focusing solely on features and leaving risks for late in the project.
  10. Answer: It provides a clear, shared understanding of the quality standards and criteria a piece of work must meet before it is considered “delivered.” Explanation: This ensures consistency across the team and prevents the delivery of low-quality or incomplete increments to the stakeholders.

Open-Ended / Design Questions

  1. Designing a Delivery Dashboard: If you were tasked with creating an information radiator for a team struggling with high cycle times and frequent rework, which metrics would you prioritize and why? How would you visualize these to encourage team-led problem-solving?
  2. Scenario Analysis: A team is currently using Scrum but finds that their Sprints are constantly disrupted by “urgent” unplanned maintenance requests. Design a hybrid approach that incorporates Kanban principles into their existing Scrum framework to manage these interruptions without losing the benefits of time-boxed iterations.
  3. Waste Identification: Conduct a hypothetical Value Stream Map for a software feature that takes six weeks to move from “Requested” to “Released,” even though actual development time is only five days. Identify three likely areas of Lean waste and propose specific agile practices to mitigate them.
  4. Risk Management Strategy: You are leading a project involving a highly experimental new technology. Design a risk management strategy that uses Spikes, Risk-Adjusted Backlogs, and Risk Burnup charts. Explain how these tools will interact to keep the project on track and the stakeholders informed.
  5. Retrospective Facilitation: You notice that your team’s retrospectives have become stale, with members rarely offering new ideas and the same issues recurring. Design a retrospective using the five-step framework that incorporates a new RCA tool (like Fishbone) to re-engage the team and find a permanent solution to a recurring bottleneck.

Glossary of Key Terms

  • Agile Manifesto: The foundational document of the agile movement, emphasizing individuals, interactions, and customer value over rigid processes.
  • Bottleneck: A point in a delivery process where work accumulates faster than it can be processed, slowing down the entire system.
  • CI/CD (Continuous Integration/Continuous Delivery): A set of practices and automated tools used to integrate code changes frequently and ensure the product is always in a releasable state.
  • Cycle Time: The amount of time it takes for a work item to move from “in progress” to “completed.”
  • Definition of Done (DoD): A shared checklist of criteria that a product increment must meet to be considered officially complete and of high quality.
  • DORA Metrics: A set of four key metrics (Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service) used to measure DevOps performance.
  • Fishbone (Ishikawa) Diagram: A root cause analysis tool used to visually categorize and brainstorm the potential causes of a problem.
  • Information Radiator: A highly visible display, such as a whiteboard or digital screen, used to share real-time project status and metrics with the team and stakeholders.
  • Kanban: A visual delivery framework focused on continuous flow, managing WIP, and optimizing throughput.
  • Little’s Law: A principle of flow stating that the average cycle time is proportional to the amount of work in progress divided by the throughput.
  • Refactoring: The internal cleanup of code or product structures to improve quality and maintainability without altering external behavior.
  • Risk Burnup Chart: A visual tool that tracks the total risk exposure of a project over time, showing how risks are being mitigated or retired.
  • Servant Leadership: A leadership philosophy where the leader’s primary goal is to serve and support the team by removing obstacles and fostering growth.
  • Spike: A brief, time-boxed task used to research a technical or functional uncertainty to reduce project risk.
  • Story Point: A relative unit of measure used by agile teams to estimate the size, complexity, and effort required for a user story.
  • Test-Driven Development (TDD): A development practice where automated tests are written before the actual code to ensure accuracy and quality.
  • Throughput: The number of work items or units of value a team delivers over a specific period.
  • Value Stream Mapping: A Lean technique used to document and analyze the sequence of steps required to deliver a product to a customer.
  • Velocity: The total number of story points or work units a team completes during a single iteration.
  • WIP (Work in Progress): The number of work items that have been started but are not yet finished.

Leaderboard

No scores saved yet. Be the first!

25 Questions — PMI-ACP : Certified Agile Practitioner - Domain 4 - Delivery

Expand any question to reveal the correct answer and explanation.

  1. 1 According to the comparison provided by YourDigitalAid, what is a primary instructional difference between Joseph Phillips' course and Andrew Ramdayal's course?

    Consider which instructor incorporates material from a broader range of PMI certifications into their training.

    Phillips focuses heavily on PMP concept crossover, while Ramdayal provides a more direct, exam-specific scope.

    Phillips includes traditional project management calculations and PMP material, whereas Ramdayal's content is more succinct and focused strictly on the ACP requirements.

    • Ramdayal approaches the role as a 'Scrum Master' while Phillips approaches it as an 'Agile Project Manager.'

      The source material actually states the opposite; Phillips comes at the angle of being a Scrum Master, while Ramdayal focuses on the Agile Project Manager perspective.

    • Phillips spends more time on XP and Scrum disciplines, whereas Ramdayal focuses on Lean and Kanban.

      The source indicates that Ramdayal breaks down Scrum and XP more thoroughly, while Phillips provides broader touches on Lean and Kanban.

    • Ramdayal's course is significantly longer, totaling 13 hours of video content compared to Phillips' 9 hours.

      In reality, Phillips' course is the longer one at 13 hours, while Ramdayal's course is shorter at 9 hours.

  2. 2 The 'Agile Practice Guide – Second Edition' introduces which specific modern delivery topics that were not emphasized in the previous team-level focus?

    Look for concepts related to current technological shifts and global ethical considerations.

    AI-enabled delivery and sustainability

    The second edition expands its scope to include contemporary considerations like Artificial Intelligence and environmental sustainability in project delivery.

    • Basic Scrum rituals and the Agile Manifesto

      These are foundational concepts that have been part of Agile practice and documentation since its inception.

    • Standard Waterfall Gantt charts and critical path method

      The guide focuses on enhancing agility and value delivery rather than returning to purely predictive project management tools.

    • Traditional PRINCE2 governance and ITIL v3 foundations

      The guide is framework-neutral but remains focused on Agile and adaptive practices, not specific traditional governance frameworks.

  3. 3 In the context of Mike Griffiths' 'Beyond Agile' model, what is the primary warning given to experienced project practitioners?

    Think about a term that describes being short-sighted regarding a single methodology.

    The danger of 'Agile-myopia,' or believing every problem is best solved by Agile approaches.

    The model encourages being ruthlessly selective and situational rather than assuming Agile is the universal solution.

    • The necessity of increasing the number of Agile ceremonies to improve productivity.

      Griffiths actually found that the most productive teams spent less time on Agile ceremonies and more time on actual delivery.

    • The risk of ignoring traditional PMP calculations like Earned Value Management.

      While the book layers in ideas, the focus of the warning is on the blind application of Agile processes regardless of value.

    • The failure to implement scaling models such as SAFe or LeSS in all environments.

      Griffiths contrasts his model with these scaling frameworks, suggesting that too much process leads to 'buffet-syndrome'.

  4. 4 For a candidate attempting the PMI-ACP exam in late 2026, what is the mandatory requirement for contact hours of Agile training?

    This number is specifically mentioned across multiple course reviews as the 'education requirement'.

    21 contact hours

    PMI requires exactly 21 hours of documented training from a certified course or professional to be eligible for the exam.

    • 35 contact hours

      This is a common requirement for the PMP certification, not the PMI-ACP.

    • 23 contact hours

      The CAPM certification requires 23 contact hours, which differs from the ACP requirement.

    • 60 contact hours

      This exceeds the requirement and is likely confused with the PDUs needed for renewal over a 3-year cycle.

  5. 5 Which Domain of the Examination Content Outline (ECO) is cited by vCare Project Management as focusing on identifying, prioritizing, and resolving project impediments?

    The name of the domain mirrors the procedural action of finding and fixing issues.

    Problem Detection and Resolution

    This domain specifically deals with the proactive identification of risks and the resolution of issues hindering progress.

    • Continuous Improvement

      While related, this domain focuses on product, process, and people evolution rather than specific impediment resolution.

    • Value-Driven Delivery

      This domain focuses on delivering high-value increments to stakeholders rather than the tactical removal of blockers.

    • Adaptive Planning

      This domain concerns the iterative nature of planning based on feedback rather than issue detection.

  6. 6 When comparing the PMI-ACP to the Certified ScrumMaster (CSM) credential, which factor distinguishes the PMI-ACP in 2026?

    Consider the variety of methodologies the candidate must master for each certification.

    It is framework-agnostic, covering Scrum, Kanban, Lean, and XP.

    The PMI-ACP tests a broad spectrum of methodologies, whereas the CSM is specifically role-based and focused only on Scrum.

    • It can be earned through a simple two-day workshop with no experience requirement.

      This describes the CSM; the PMI-ACP requires verified Agile project experience and a formal application.

    • It is significantly easier to pass because it focuses only on terminology.

      The source material indicates that the PMI-ACP is considered much harder and more rigorous than role-specific certifications.

    • It does not require any continuing education to remain active once earned.

      PMI credentials generally require a Continuing Certification Requirements (CCR) cycle to maintain active status.

  7. 7 Which book by Mike Griffiths is specifically designed as a 'Visual Learner’s Guide' that has been updated for the July 2026 exam change including 'M.O.R.E.' content?

    The title suggests a format that uses drawings and cartoons to aid memory.

    PM Illustrated

    This book uses mindmaps and graphics to explain the syllabus and was specifically updated for the July 2026 changes.

    • Agile Fundamentals

      This is described as a streamlined intro book with exam preparation components removed.

    • User Stories Applied

      This book is written by Mike Cohn, not Mike Griffiths, and focuses specifically on requirements.

    • Kanban in Action

      This book was written by Marcus Hammarberg and Joakim Sunden, focusing exclusively on Kanban.

  8. 8 According to the source materials, why is memorizing 'laundry lists' of responsibilities insufficient for passing the PMI-ACP exam?

    Think about the format of the questions you will encounter during the test.

    The exam questions are situational and expect you to know how to respond in specific environments.

    Questions are designed to test the application of principles in real-world project scenarios rather than rote memorization.

    • The Examination Content Outline (ECO) is changed every three months to prevent memorization.

      The ECO is revised based on industry research, but there is no indication it is changed quarterly.

    • PMI provides an official study guide that renders outside memorization unnecessary.

      The source material explicitly states that PMI has never released an 'official' स्टडी guide under their brand.

    • The exam primarily uses mathematical formulas where concepts are secondary.

      Agile concepts and mindset are central to the exam, with calculations being only a small portion of the syllabus.

  9. 9 In the 'Agile Books listed by PMI-ACP' resource, which 2010 book is specifically recommended for its perspective on learning about coaching for ScrumMasters?

    The title of the book contains the specific professional activity it aims to improve.

    Coaching Agile Teams by Lyssa Adkins

    The author Greg Mester notes he liked this book specifically for the learning provided from a coaching perspective.

    • Agile Estimating and Planning by Mike Cohn

      This book focuses on estimation and scheduling rather than coaching dynamics.

    • Kanban by David J. Anderson

      This book is the definitive guide for implementing the Kanban method in a technology business.

    • Exploring Scrum by Dan Rawsthorne

      This book covers the fundamentals of the Scrum framework rather than specifically focusing on the coach role.

  10. 10 What is described as the 'Agile mindset' in the context of the PMI-ACP exam prep materials?

    Focus on the difference between superficial adherence to a process and deep comprehension of its purpose.

    Understanding the values and principles that drive 'being Agile' rather than just 'doing Agile.'

    The exam tests whether a practitioner can apply Agile values to complex situations rather than just following mechanics.

    • The ability to memorize the 12 principles of the Agile Manifesto verbatim.

      Memorization is less important than the situational application of the underlying values.

    • Preferring Agile for every project regardless of the environment or life cycle suitability.

      A true Agile practitioner understands when and why to select a specific life cycle, including hybrid models.

    • Ensuring the team follows the Scrum Guide without any deviations or tailoring.

      Agile emphasizes 'individuals and interactions over processes and tools,' which often necessitates tailoring.

  11. 11 Which calculation-related topic is mentioned as being specifically analyzed in Joseph Phillips' PMI-ACP prep course?

    Consider a Lean technique that helps identify waste in a process flow.

    Value Stream Mapping

    This is a Lean concept used to analyze the flow of materials and information, which Phillips covers alongside PMP calculations.

    • Total Float and Free Float

      These are traditional Critical Path Method concepts typically associated with the PMP rather than the core Agile ACP focus.

    • Black-Scholes Model

      This is a financial derivative model and is not part of the PMI-ACP knowledge domains.

    • Six Sigma Green Belt standard deviations

      While related to quality, these are part of a separate certification path (CSSGB).

  12. 12 According to the Brain Sensei simulator details, how many 'Realistic Exam Questions' are provided to users in their question bank?

    This number is between 800 and 900.

    850

    The simulator dynamically generates exams from a bank of 850 questions to ensure a new experience during retakes.

    • 1,500

      This higher number is associated with the CAPM training bank from Learners Ink.

    • 120

      This is the number of questions in the 'Static' practice exams provided by the simulator.

    • 1,000

      While Tech Agilist offers 'almost 1,000' questions, Brain Sensei specifically lists 850.

  13. 13 The source material mentions that PMI-ACP holders report measurable salary advantages. What is the reported percentage premium for certified individuals?

    The range begins with a value that is five points higher than ten.

    $15\% - 22\%$

    Depending on the industry and geography, PMI-ACP holders earn significantly more than their non-certified peers.

    • $36\% - 44\%$

      This much higher range is specifically mentioned for CAPM-certified professionals in the Santa Clarita area.

    • $5\% - 10\%$

      This is a conservative estimate that does not reflect the actual data reported in the Talent Gap report.

    • $50\%$

      While salary uplifts are significant, a $50\%$ premium is not supported by the cited data.

  14. 14 Which Agile framework is described as being 'heavily analyzed' in terms of rituals, the role of an Agile project manager, and team member roles in the Joseph Phillips course?

    This framework is the most popular Agile methodology and features roles like the Product Owner.

    Scrum

    The review highlights that Scrum, alongside XP and Kanban, is a core focus, with particular attention to its specific rituals.

    • Waterfall

      Waterfall is a predictive methodology and is not an Agile framework analyzed for rituals in an ACP course.

    • PRINCE2

      PRINCE2 is a project management methodology, not an Agile framework analyzed for 'rituals' in this context.

    • Six Sigma

      Six Sigma is a process improvement methodology focused on quality and variance, not an Agile framework.

  15. 15 What is one 'Pro' of Sorin Dumitrascu's Agile Certified Practitioner training program mentioned in the YourDigitalAid review?

    Consider the version of the Project Management Body of Knowledge that the instructor reviews.

    It includes an accurate review of the PMBOK 7.

    Despite other weaknesses, the reviewer confirms that the course accurately covers the PMBOK 7 based on their reading of the text.

    • It is the shortest course available, taking only 3 hours to complete.

      The course is actually one of the longest at 22.5 hours.

    • It provides a robust bank of 2,000 practice questions.

      The review notes as a 'Con' that there are no practice exams included in this course.

    • The lecture style is highly energetic and engaging for the learner.

      The review describes the lecturer as monotone, which is listed as a 'Con'.

  16. 16 In the study plan suggested by vCare, what should a candidate focus on during Weeks 1-2?

    This phase involves looking at the exam blueprint and the core values of the methodology.

    ECO Orientation and Agile Foundations

    The plan suggests downloading the ECO and understanding the Agile Manifesto and its 12 principles before diving into frameworks.

    • Full-Length Practice Exam Phase

      Taking mock exams is suggested for Weeks 8-9, after the knowledge base has been built.

    • Framework Deep Dives for Scrum and Kanban

      Systematic study of major frameworks is allocated to Weeks 3-5 of the study plan.

    • Targeted Review of weak domains only

      Targeted review based on exam data is the final step in Week 10.

  17. 17 A student review of Andrew Ramdayal's course mentions his 'hybrid accent' and 'street sense' guidance. Which specific part of the process did his guidance help the student with most?

    Think about the administrative step required before you are allowed to sit for the test.

    The PMI application process

    The student specifically mentions following Ramdayal's guidance to fill out and submit their application, which was then approved.

    • Mastering Value Stream Mapping formulas

      While important, the review focuses on the instructor's help with the administrative and logistical hurdles of certification.

    • Learning how to code in an XP environment

      The PMI-ACP is a practitioner certification for project leaders, not a coding workshop.

    • Understanding the history of the Agile Manifesto co-authors

      The review emphasizes 'street sense' regarding the application and exams, not academic history.

  18. 18 Which Domain of the PMI-ACP ECO accounts for 'Continuous Improvement' and what does it foster?

    This domain is the last of the seven and deals with 'Kaizen' principles.

    Domain VII; it fosters improvement in product, process, and people.

    The domain is designed to ensure the team and the organization are constantly evolving to be more effective.

    • Domain I; it fosters the initial selection of the Agile methodology.

      Domain I is typically 'Agile Mindset' rather than the iterative improvement domain.

    • Domain IV; it fosters team building through icebreaker exercises.

      Team Performance is a separate domain that deals with collaboration and empowerment.

    • Domain V; it fosters the creation of long-term predictive project plans.

      Domain V is 'Adaptive Planning,' which focuses on iterative planning rather than fixed long-term plans.

  19. 19 The review of Chuck Cobb's course mentions it is 'more like a syllabus than an actual course.' What is one specific resource he provides to help students study?

    It is a large, static file that a student can save and read offline.

    A massive downloadable document containing everything needed to study

    Although the video content is short, Cobb provides a comprehensive written guide for self-directed learners.

    • A deck of 500 physical flashcards mailed to the student

      The resource provided is a digital document, not physical flashcards.

    • Access to a private VR simulation of an Agile stand-up

      While innovative, this is not a resource mentioned in the description of Cobb's course.

    • A voucher for $100 off the PMI membership fee

      Instructors generally do not provide direct monetary discounts on PMI membership fees.

  20. 20 Why does YourDigitalAid suggest that students should study in an area where they will take the exam?

    The advice focuses on the psychological state of the candidate.

    Comfort is key to performing well on the test.

    Being familiar with the environment can help reduce anxiety and improve focus during the actual 3-hour exam.

    • It is required by PMI's online proctoring rules for environmental validation.

      While proctoring has rules, the suggestion here is a personal study tip for student comfort.

    • To ensure that the student has high-speed internet access during study.

      This is a logistical requirement for the exam, but the tip specifically mentions 'comfort' as the reason.

    • Because Agile ceremonies must be performed in the same location daily.

      This misinterprets the 'Daily Stand-up' concept, which concerns timing and focus, not a mandatory physical location.

  21. 21 What common misconception about 'Agile ceremonies' does Mike Griffiths address in his 'Beyond Agile' book?

    Consider the relationship between the time spent in meetings and the time spent actually working.

    That more time spent in ceremonies leads to higher productivity.

    Griffiths observed that high-performing teams actually drop ceremonies that no longer add value to focus on delivery.

    • That ceremonies should be held at midnight to avoid disrupting work.

      This is an impractical suggestion and is not discussed in the text.

    • That ceremonies are the only way to communicate in an Agile environment.

      Agile encourages face-to-face communication, but it does not mandate that all communication happen within formal ceremonies.

    • That ceremonies must be led by a certified PMP to be valid.

      Ceremonies like the Daily Scrum are led by the team or Scrum Master, not necessarily a PMP.

  22. 22 In the review of Tech Agilist's practice exams, what is highlighted as the 'value' of the practice tests according to a student testimonial?

    It relates to the feedback provided after a student selects an option.

    The very detailed descriptions of why an answer is correct or incorrect.

    A student notes that these explanations are perhaps more valuable than the course material itself for learning.

    • The ability to cheat and see the answers before answering.

      This would defeat the purpose of a practice exam and is not cited as a value.

    • The fact that the questions are identical to the actual exam questions.

      Practice questions are 'similar,' but PMI does not release actual current exam questions to providers.

    • The inclusion of a free Agile Scrum Master certificate with every test taken.

      No such certificate is mentioned as part of the practice exam package.

  23. 23 Mike Griffiths' 'Agile Illustrated' focuses on illustrating which specific set of tasks covered in the PMI-ACP exam?

    The number is in the sixties and relates to a leadership style centered on serving the team.

    62 Servant Leadership Tasks

    The book provides a visual overview of these specific tasks to help Scrum masters and servant leaders support their teams.

    • 49 Process Groups

      This number refers to standard PMP processes, which is not the focus of this Agile-specific illustrated guide.

    • 12 Principles of Project Management

      While it covers the 12 Agile Principles, the 62 tasks refer specifically to Servant Leadership.

    • 100 Software Engineering Rituals

      The book is focused on project management and leadership behaviors, not engineering rituals.

  24. 24 Which specific Agile estimation concepts are listed by Andrew Ramdayal as part of the 'Agile Foundations and Frameworks' domain?

    Consider terms related to story-based requirements and a theoretical measure of time without distractions.

    User stories, Ideal time, and Estimation control limits

    These are key technical concepts that ACP candidates must master to manage project scope and time iteratively.

    • Beta distribution and Three-point estimation

      These are traditional PERT estimation techniques more common in predictive PMP studies.

    • Parametric estimating and Analogous estimating

      While usable in Agile, these are standard project management terms rather than the 'Foundations' focus mentioned for Ramdayal.

    • Monte Carlo simulations for schedule risk

      Monte Carlo is a complex statistical tool and is not listed as a foundation concept for the Ramdayal course.

  25. 25 What is the 'Verdict' on taking the Joseph Phillips practice exam course if a student is 'strapped for cash'?

    The advice suggests prioritizing a specific 'simulator' tool over this practice exam set.

    Don't bother; money is better spent on the PM-prep cast's exam simulator.

    The reviewer suggests that the PrepCast simulator is a more valuable investment for a final benchmark before the real exam.

    • It is a must-buy because it is the only source of 120-question timed exams.

      The review suggests other resources are more updated and better structured for the current exam.

    • It is free for all PMI members, so cash is not an issue.

      Udemy courses and simulators typically require a separate purchase and are not part of basic PMI membership.

    • Wait for a 90\% discount on Black Friday before purchasing.

      While Udemy has sales, this is not the specific advice given in the text's verdict.