Skip to content

PMI-ACP : Product (Domain 3)

PMI-ACP : Certified Agile Practitioner - Domain 3 - Product

25 questionsmedium

This comprehensive study guide is designed to prepare candidates for the Project Management Institute’s Agile Certified Practitioner (PMI-ACP) exam, specifically focusing on Domain 3: Product. This domain encompasses the strategies, tools, and mindsets required to define, prioritize, and refine a product in an environment of constant change. Drawing from the most respected agile resources, including the Agile Practice Guide, the PMBOK® Guide, and the foundational works of Mike Cohn and Alistair Cockburn, this guide provides a deep dive into the mechanics of value delivery.

The PMI-ACP exam is not a test of rote memorization. As noted by industry experts, the exam is heavily situational, requiring a profound understanding of how agile principles apply to real-world scenarios. Domain 3 focuses on how an agile project manager or team member functions as a servant leader to ensure the product backlog remains healthy, estimates are realistic, and the customer remains at the center of the development lifecycle.

1. The Agile Mindset in Product Delivery

The foundation of product-related tasks in an agile environment is the “Agile Mindset.” This mindset is governed by the four values and twelve principles of the Agile Manifesto. In the context of product delivery, this means prioritizing “individuals and interactions over processes and tools” and “customer collaboration over contract negotiation.”

To be successful in Domain 3, practitioners must transition from “doing agile”—merely following ceremonies—to “being agile,” which involves internalizing values that support rapid value delivery. Agile approaches are framework-agnostic on the exam, meaning a candidate must understand how these values manifest across Scrum, Kanban, Extreme Programming (XP), and Lean. For example, while Scrum focuses on iterative delivery through sprints, Kanban emphasizes flow and the visualization of work. Both, however, serve the same goal: delivering the highest value to the customer in the shortest possible time.

A critical component of this mindset is servant leadership. A servant leader does not dictate tasks but instead “carries food and water” for the team, facilitating their work and removing impediments. In product planning, this involves ensuring the team has a clear vision and the necessary resources to decompose high-level goals into actionable work.

2. Value Decomposition: From Epics to User Stories

Value decomposition is the process of breaking down high-level business requirements into smaller, manageable pieces of work. This ensures that the team can deliver value incrementally and adjust course based on feedback.

Epics

Epics are large bodies of work that cannot be completed in a single iteration. They represent significant features or initiatives. In the early stages of a project, requirements are often captured as epics because the details are not yet clear. As the project progresses, these epics are “sliced” into smaller units known as user stories.

User Stories

The user story is the primary vehicle for defining requirements in agile. It is a brief, high-level statement of a requirement from the perspective of an end-user. The standard format is: “As a [role], I want [feature], so that [benefit].”

The power of the user story lies in its simplicity. It is not a detailed specification but rather a “placeholder for a conversation” between the team and the customer. This collaborative approach ensures that the focus remains on the “why” and the “who” rather than just the “what.”

Vertical Slicing

A key concept in value decomposition is vertical slicing. Unlike traditional “horizontal” layers (where one team might build the database and another the user interface), a vertical slice represents a fully functional piece of a feature that cuts through all layers of the technology stack. This allows the customer to see and test a working piece of the product, providing early validation of the value being delivered.

3. The INVEST Criteria for Quality User Stories

To ensure that user stories are effective and ready for development, agile teams use the INVEST acronym. This set of criteria helps practitioners evaluate the quality of a decomposed requirement:

AttributeDescription
IndependentThe story should be self-contained, with as few dependencies on other stories as possible, allowing it to be developed and delivered in any order.
NegotiableStories are not fixed contracts; they are flexible and open to discussion between the customer and the team.
ValuableEvery story must provide a clear benefit to the end-user or the business.
EstimableThe team must have enough information to provide a realistic estimate of the effort required.
SmallStories should be small enough to be completed within a single iteration (sprint).
TestableThere must be clear acceptance criteria that allow the team to verify the story is finished.

Applying the INVEST criteria during refinement sessions ensures that the team does not take on “bloated” or ambiguous work that could derail an iteration.

4. Backlog Management and Refinement

The Product Backlog is an ordered list of everything that might be needed in the product. It is a living document that constantly evolves as the team learns more about the product and the market.

Backlog Refinement (Grooming)

Backlog refinement is the ongoing process of adding detail, estimates, and order to items in the backlog. It is a collaborative effort involving the Product Owner, the team, and sometimes stakeholders. Key activities include:

  • Removing irrelevant items.
  • Splitting large stories (epics) into smaller ones.
  • Ensuring the highest-priority items are “ready” for the next iteration.
  • Re-estimating items based on new knowledge.

Successful refinement prevents the “bottleneck” effect during sprint planning. By spending time regularly on refinement, the team ensures that they always have a clear “runway” of work that is well-understood and prioritized by value.

Prioritization Techniques

Agile practitioners use various methods to order the backlog. Two common approaches mentioned in study materials are:

  1. MoSCoW: Categorizing items into Must-have, Should-have, Could-have, and Won’t-have (this time). This helps manage stakeholder expectations and focus on critical functionality.
  2. Return on Investment (ROI): Prioritizing features based on the economic value they provide compared to the cost of development.

5. Relative Estimation: A Shift in Perspective

In traditional project management, estimation is often done in “absolute” units like hours or days. Agile flips this by using “relative” estimation. Instead of trying to guess exactly how many hours a task will take, the team compares the effort of one task to another.

Relative estimation is based on the idea that humans are better at comparing sizes than at predicting absolute time. For example, it is easier to say that a “Login Screen” is twice as complex as a “Logout Button” than it is to say the screen will take exactly 4.5 hours.

Story Points

The most common unit for relative estimation is the story point. Story points represent a combination of effort, complexity, and risk. Most teams use the Fibonacci sequence (1, 2, 3, 5, 8, 13, etc.) to assign points, as the increasing gaps between the numbers reflect the increasing uncertainty of larger tasks.

Ideal Time

While story points are the gold standard, some teams use “Ideal Time”—the amount of time a task would take if there were zero interruptions, meetings, or distractions. However, relative units like story points remain the preferred method for long-term planning and velocity tracking.

6. Collaborative Estimation Techniques

Agile estimation is a team sport. It relies on “Wideband” techniques, where multiple perspectives are integrated to reach a consensus, reducing individual bias and improving accuracy.

Planning Poker

Planning Poker is a popular consensus-based estimation game. Each team member holds a deck of cards with numbers (usually Fibonacci). The Product Owner describes a user story, and the team asks clarifying questions. Each member then selects a card representing their estimate and places it face down. When everyone is ready, the cards are revealed simultaneously.

  • If there is a consensus, the estimate is recorded.
  • If there is a wide variance (e.g., one person votes 2 and another 13), the outliers explain their reasoning. The team discusses the story further and re-votes until they reach a common understanding.

T-Shirt Sizing

For high-level estimation, such as during initial product discovery or when dealing with a massive backlog, teams often use T-shirt sizes (XS, S, M, L, XL). This is a quick way to categorize epics without getting bogged down in the precision of numbers.

Wideband Delphi

The Wideband Delphi technique is the broader category under which Planning Poker sits. It involves an anonymous, iterative process where experts provide estimates and then discuss the results to move toward a consensus. This prevents “anchoring,” where the team is influenced by the first person to speak.

7. Work Visualization and Information Radiators

In agile, “making work visible” is a core tenet. Information Radiators are highly visible displays (either physical or digital) that provide the team and stakeholders with an at-a-glance status of the project.

Kanban Boards

A Kanban board is a tool used to visualize work as it moves through various stages of a process. A basic board has columns like:

  • To Do (Backlog)
  • In Progress (Doing)
  • Testing/Review
  • Done

The goal is to optimize the “flow” of work. By using Work-in-Progress (WIP) limits, teams can prevent bottlenecks. If the “Testing” column is full, the team stops taking on new “In Progress” work and helps clear the testing backlog instead.

Task Boards

Similar to Kanban boards, task boards are often used in Scrum to track the specific tasks within a sprint. They provide transparency and help the team stay aligned during the Daily Scrum.

8. Tracking Progress: Burnup and Burndown Charts

Progress in agile is measured by the delivery of working software or product increments. Two primary charts are used to visualize this progress over time.

Burndown Charts

A Burndown Chart shows the amount of work remaining in an iteration (Sprint Burndown) or the entire project (Release Burndown). The vertical axis represents the work (in points or hours), and the horizontal axis represents time.

  • A “healthy” burndown shows a steady downward trend toward zero.
  • If the line stays flat, it indicates the team is not finishing tasks or that “Scope Creep” is occurring.

Burnup Charts

A Burnup Chart shows two lines: the total work in the project (scope) and the work completed to date.

  • Unlike the burndown, the burnup clearly shows changes in scope. If the customer adds ten more stories, the “Total Work” line moves up, while the “Completed Work” line continues its upward climb at the team’s velocity.
  • The point where the two lines meet indicates the estimated completion date.

9. Cumulative Flow Diagrams (CFD) and Flow Metrics

For teams focused on Kanban or Lean, the Cumulative Flow Diagram (CFD) is a sophisticated tool for understanding the health of the project’s delivery system.

A CFD tracks the number of items in each stage of the workflow over time. It provides three critical pieces of data:

  1. Work in Progress (WIP): The vertical distance between the “Started” and “Finished” lines. High WIP often indicates a process bottleneck.
  2. Lead Time: The total time from when an item enters the backlog to when it is completed.
  3. Cycle Time: The time it takes for a team member to actually work on and finish an item once work has begun.

By analyzing the “bands” on a CFD, a practitioner can identify if a team is becoming overloaded or if a specific stage in the lifecycle (such as Quality Assurance) is consistently slowing down delivery.

10. Customer Collaboration and Stakeholder Engagement

Agile product management is rooted in a partnership between the delivery team and the customer. This relationship is managed through active engagement and frequent feedback loops.

The Role of the Product Owner

The Product Owner (PO) acts as the bridge between the customer and the team. Their primary responsibility is to maximize the value of the product. They do this by:

  • Defining the product vision.
  • Owning and prioritizing the Product Backlog.
  • Accepting or rejecting work delivered by the team.
  • Collaborating with stakeholders to ensure the product meets business needs.

Workshops and Face-to-Face Communication

Agile prioritizes face-to-face communication as the most efficient way to convey information. Product discovery often happens in collaborative workshops where stakeholders and the team brainstorm ideas and “story map” the user journey.

Iteration Reviews (Demos)

At the end of every iteration, the team holds a review session to demonstrate the “Potentially Shippable Product Increment” to the customer. This is a crucial feedback loop. The customer provides immediate input, which is then used to refine the backlog for future iterations. This ensures that the product never drifts too far from the customer’s actual needs.

Active Listening and Emotional Intelligence

Effective collaboration requires more than just technical skills. Agile practitioners must employ “Active Listening” strategies to truly understand stakeholder needs and “Emotional Intelligence” to navigate the team dynamics and conflict resolution necessary for high performance.

11. Conclusion: The Path to Adaptive Planning

Domain 3 of the PMI-ACP represents the “engine room” of agile delivery. By moving away from rigid, long-term plans and embracing adaptive planning, teams can navigate the complexities of modern product development. Success in this domain requires a balance of technical rigor—using tools like CFDs and relative estimation—and soft skills like servant leadership and customer collaboration.

As emphasized by experts like Andrew Ramdayal and Joseph Phillips, the key to passing the exam is not just knowing these definitions but understanding the “Agile Mindset” that connects them. Whether you are using Scrum, Kanban, or XP, the goal remains the same: to deliver value early and often, while continuously improving both the product and the process.

Study Questions

Short-Answer Questions

  1. What does the acronym INVEST stand for in the context of user stories?
  2. In Planning Poker, what should the team do if there is a wide discrepancy between the highest and lowest estimates?
  3. What is the primary difference between a Burnup Chart and a Burndown Chart?
  4. Define “Vertical Slicing” and explain why it is preferred in agile.
  5. What is “Lead Time” in a Cumulative Flow Diagram (CFD)?
  6. Who is primarily responsible for prioritizing the Product Backlog?
  7. What is the purpose of a “WIP Limit” on a Kanban board?
  8. How does “Relative Estimation” differ from “Absolute Estimation”?
  9. What is a “Potentially Shippable Product Increment”?
  10. Name two frameworks that are heavily analyzed in the PMI-ACP exam syllabus besides Scrum.

Answer Key with Explanations

  1. Independent, Negotiable, Valuable, Estimable, Small, Testable. These criteria ensure that a user story is high-quality and ready for a team to work on during an iteration.
  2. The outliers explain their reasoning, and the team discusses the story further before re-voting. This collaborative discussion ensures that all risks and complexities are understood by the entire team.
  3. A Burndown Chart shows work remaining, while a Burnup Chart shows work completed against total scope. Burnup charts are particularly useful for visualizing how scope changes over time.
  4. Creating a functional piece of a feature that cuts through all layers of the tech stack. This allows the customer to test actual functionality and provides early value validation.
  5. The total time from when a request is made (enters the backlog) to when it is completed. This metric helps teams understand the customer’s perspective on how long it takes to get things done.
  6. The Product Owner. The PO is the “value maximizer” and must ensure the team is always working on the highest-priority items.
  7. To prevent bottlenecks and optimize flow by restricting how many items can be in a certain stage at once. This encourages the team to “stop starting and start finishing.”
  8. Relative estimation compares tasks to each other (e.g., points), while absolute estimation uses fixed units (e.g., hours). Relative estimation is often more accurate for long-term agile planning due to human psychology.
  9. A piece of the product that is of high enough quality to be released to the customer at the end of an iteration. Even if it isn’t released, it must meet the “Definition of Done.”
  10. Kanban and XP (Extreme Programming). The PMI-ACP is framework-agnostic and requires knowledge of multiple agile disciplines.

Open-Ended/Design Questions

  1. You are a Product Owner for a new mobile banking app. The stakeholders have provided a list of 50 “Must-Have” features. Design a strategy for refining this backlog and getting the team ready for their first sprint.
  2. Describe how you would use a Cumulative Flow Diagram to identify a bottleneck in a software development process where items are consistently getting stuck in the “Security Review” phase.
  3. You are facilitating a Planning Poker session where the team consistently votes “13” or “21” for almost every story. Analyze why this might be happening and propose a way to help the team improve their decomposition.
  4. Imagine a scenario where a high-priority stakeholder demands a major scope change in the middle of a sprint. Using agile principles, design a response that balances stakeholder satisfaction with team performance.
  5. Compare and contrast how “Value” is measured and displayed in a Scrum environment versus a Kanban environment. Which metrics would you prioritize for a team that is struggling with unpredictable delivery dates?

Glossary of Key Terms

  • Agile Manifesto: The foundational document of agility, consisting of four values and twelve principles that guide agile practitioners.
  • Backlog Refinement: The ongoing process of reviewing, detailing, and prioritizing items in the product backlog to ensure they are ready for upcoming work.
  • Burnup Chart: A visual tool that tracks total work completed over time against the total project scope.
  • Cumulative Flow Diagram (CFD): A chart that displays the distribution of work items across different stages of a process to help identify bottlenecks and track flow metrics.
  • Cycle Time: The amount of time it takes to complete a work item once work has actually begun on it.
  • Epic: A large, high-level requirement that must be broken down into smaller user stories before it can be completed by a team.
  • Fibonacci Sequence: A series of numbers (1, 2, 3, 5, 8, 13…) used in relative estimation to reflect the increasing uncertainty as tasks grow in size.
  • Information Radiator: A visible physical or digital display that provides the team and stakeholders with real-time project status.
  • INVEST: A set of criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) used to assess the quality of user stories.
  • Kanban Board: A visualization tool used to manage the flow of work and limit work-in-progress.
  • Lead Time: The total duration from the moment a work item is requested to the moment it is delivered to the customer.
  • Planning Poker: A consensus-based collaborative estimation technique used by agile teams to assign relative sizes to user stories.
  • Product Owner: The role responsible for maximizing product value, defining the product vision, and managing the prioritized backlog.
  • Relative Estimation: An estimation technique that determines the size of a task by comparing it to other tasks rather than using absolute time units.
  • Servant Leadership: A leadership philosophy where the leader’s primary goal is to support and facilitate the team’s success.
  • Story Point: A unit of measure used in relative estimation to represent the combined effort, complexity, and risk of a user story.
  • User Story: A high-level requirement described from the perspective of an end-user, serving as a placeholder for a detailed conversation.
  • Velocity: The measure of a team’s rate of progress, usually calculated as the average number of story points completed per iteration.
  • Vertical Slicing: A technique of decomposing requirements into thin, functional layers that provide end-to-end value to the user.
  • WIP (Work in Progress) Limit: A constraint set on a Kanban board to limit the number of items that can be in a particular state at one time.

Leaderboard

No scores saved yet. Be the first!

25 Questions — PMI-ACP : Certified Agile Practitioner - Domain 3 - Product

Expand any question to reveal the correct answer and explanation.

  1. 1 According to the YourDigitalAid review, what is the primary pedagogical difference between Joseph Phillips' course and Andrew Ramdayal's PMI-ACP prep course?

    Consider which instructor adds 'extra stuff' that might be useful for a different $PMI$ certification.

    Phillips includes coverage of $PMP$ calculations and traditional project management concepts, whereas Ramdayal is strictly focused on the $ACP$ scope.

    Phillips' course provides cross-over content helpful for those pursuing the $PMP$ afterward, while Ramdayal's course is more direct and $50\%$ shorter.

    • ✗ Ramdayal focuses heavily on Lean and Kanban, while Phillips concentrates almost exclusively on Scrum and XP.

      The source material actually states that Phillips touches on Lean and Kanban while Ramdayal spends more time breaking down Scrum and XP.

    • ✗ Phillips approaches the course as an agile project manager, whereas Ramdayal approaches it from the angle of being a Scrum Master.

      The source indicates the opposite: Phillips approaches from the Scrum Master angle and Ramdayal from the agile project manager angle.

    • ✗ Ramdayal's course requires $21$ contact hours to complete, whereas Phillips' course provides $23$ contact hours.

      Both courses are designed to fulfill the $21$ contact hour requirement for the $PMI-ACP$ specifically.

  2. 2 The 'Agile Practice Guide - Second Edition' introduces several modern topics. Which of the following is specifically mentioned as a new inclusion for enterprise-wide initiatives?

    Look for cutting-edge technology and organizational culture themes emphasized in the 2026 updates.

    Psychological safety and $AI$-enabled delivery.

    The second edition expands beyond team-level delivery to include updated guidance on $AI$, distributed work, and psychological safety.

    • ✗ Traditional Waterfall lifecycle modeling.

      While it compares life cycles, traditional waterfall is a predictive approach that was already established; the new edition focuses on modern agility.

    • ✗ Basic Scrum rituals and roles.

      Scrum rituals are foundational agile concepts and would not be considered 'new' or emerging topics in a second edition.

    • ✗ Manual testing protocols for software development.

      The guide emphasizes modern delivery ecosystems like $DevOps$ and $DORA$ metrics rather than manual testing protocols.

  3. 3 In Mike Griffiths' book 'Beyond Agile,' what is the 'buffet-syndrome' he warns project practitioners about?

    Think about the consequences of over-incorporating every possible project discipline or process.

    The tendency of teams to take on too much process, leading to decreased delivery focus.

    The book argues for being ruthlessly selective to avoid the 'buffet-syndrome' of excessive process and the 'agile-myopia' of over-relying on agile alone.

    • ✗ The failure to provide enough diverse agile ceremonies for team members.

      The author actually suggests that high-performing teams may drop certain agile ceremonies to focus more on delivery.

    • ✗ The reliance on a single framework like $SAFe$ or $LeSS$ for all organizational needs.

      This refers to scaling models, which the author contrasts with the 'Beyond Agile' model's situational approach.

    • ✗ The practice of allowing team members to pick their own tasks without a backlog.

      This describes a lack of structure rather than the specific 'buffet-syndrome' defined as process bloat in the text.

  4. 4 According to the $vCare$ Project Management study plan, what should a candidate target as a consistent score on mock exams before scheduling the actual $PMI-ACP$?

    It is a standard benchmark often cited by training providers to indicate a safe margin for passing.

    $70\%$ or above.

    The $vCare$ guide suggests reaching this threshold during the full-length practice exam phase (Weeks $8-9$) to ensure readiness.

    • ✗ $85\%$ or above.

      While a higher score is better, the specific target recommended for scheduling the exam in the source is $70\%$.

    • ✗ $60\%$ or above.

      A $60\%$ score is typically considered too low for a high-difficulty exam like the $PMI-ACP$.

    • ✗ $100\%$ on the first attempt.

      The guide emphasizes understanding the reasoning behind incorrect answers rather than achieving a perfect score immediately.

  5. 5 Which specific agile framework receives only a 'small 5 minute lecture' in Sorin Dumitrascu's course, a point criticized by the YourDigitalAid reviewer?

    This framework is often used for visualizing flow and was specifically mentioned as being under-represented in the $22.5$-hour course.

    Kanban.

    The reviewer noted that despite Kanban questions appearing on the actual exam, Sorin's course gave it very little attention compared to Scrum.

    • ✗ Extreme Programming ($XP$).

      While $XP$ is a core framework, the specific criticism regarding a five-minute lecture was directed at the Kanban coverage.

    • ✗ Lean.

      Lean is mentioned as a framework, but it was not the one highlighted as having a disproportionately short lecture in that specific review.

    • ✗ Scrum.

      The reviewer mentioned that Sorin has a 'huge section devoted to Scrum,' making it the opposite of the criticized short lecture.

  6. 6 According to the $PMI-ACP$ characteristics provided by William C., how does $PMI$ officially categorize its 'study guide' for the certification?

    Consider $PMI$'s historical approach to providing centralized versus decentralized reference materials.

    $PMI$ has never released an official 'study guide' under its brand; it only provides reading lists and source materials.

    Unlike college exams, $PMI$ relies on a list of reference materials (sometimes over $20$ books) rather than a single branded study guide.

    • ✗ The $PMBOK$ Guide is the sole official study guide for the exam.

      The text explicitly states that while the $PMBOK$ is used, there is no single official prep guide, and materials can span many books.

    • ✗ The 'Agile Practice Guide' is the only material needed to pass.

      The sources indicate that candidates should use a wide breadth of study materials beyond just one guide.

    • ✗ The 'Agile Certified Practitioner Handbook' serves as the primary textbook.

      The handbook contains rules and requirements but is not described as a comprehensive prep or study guide for the content.

  7. 7 Mike Griffiths' 'Agile Illustrated' book specifically visualizes which of the following for $PMI-ACP$ candidates?

    The book is described as a 'visual learner's guide' specifically focusing on the behaviors of a leader who serves the team.

    The $62$ Servant Leadership Tasks covered in the exam.

    The book uses mindmaps and cartoons to illustrate the mindset, values, principles, and specific servant leadership tasks required for the $ACP$.

    • ✗ The $49$ process groups of the $PMBOK$ Guide.

      This book focuses on agile mindset and behaviors, not the traditional process groups associated with the $PMP$.

    • ✗ A comparison of $SAFe$, $LeSS$, and $Nexus$ scaling models.

      Scaling models are discussed in 'Beyond Agile,' while 'Agile Illustrated' focuses on core mindset and servant leadership.

    • ✗ The mathematical formulas for Earned Value Management ($EVM$).

      While $EVM$ is part of the $ACP$ knowledge, it is not the primary focus of the 'Agile Illustrated' visual guide.

  8. 8 Based on the $vCare$ Project Management guide, what is the reported salary advantage for $PMI-ACP$ holders compared to non-certified peers in $2026$?

    This figure is used to justify the $PMI-ACP$ as one of the fastest-growing and most respected credentials.

    $15\% - 22\%$.

    This range represents the measurable salary premium reported depending on industry and geography.

    • ✗ $5\% - 10\%$.

      This range underestimates the value of the certification as reported in $PMI$'s Talent Gap data mentioned in the text.

    • ✗ Exactly $40\%$.

      $40\%$ is the median salary uplift mentioned specifically for $CAPM$ in the Learners Ink source, not the $ACP$ range in the $vCare$ source.

    • ✗ $30\% - 50\%$.

      While significant, the specific range cited for $ACP$ premiums in the source material is $15-22\%$.

  9. 9 What content change was introduced to Mike Griffiths' 'PM Illustrated' specifically for the July $2026$ exam update?

    These topics represent the most recent additions to the $PMI$ standards for project and product delivery.

    $AI$, sustainability, and $M.O.R.E.$ content.

    The 2026 update of the book reflects the new $PMBOK$ $8$th Edition and $Agile Practice Guide$ 2nd edition themes.

    • ✗ A full section on $PMBOK$ $6$ process maps.

      The source suggests that $PMBOK$ $6$ is outdated compared to the new 2026 curriculum focus on $PMBOK$ $8$ and adaptive working.

    • ✗ A glossary of over $5,000$ agile terms.

      The book is described as a visual learner's guide using mindmaps and cartoons rather than a massive textual glossary.

    • ✗ A list of $20$ recommended books by $PMI$.

      While $PMI$ has such a list, 'PM Illustrated' is a visual explanation of the syllabus itself, not just a bibliography.

  10. 10 According to the vCare Project Management study plan, what is the focus of the first two weeks of study?

    Candidates are advised to start by looking at the exam blueprint and the underlying 'why' of agile.

    $ECO$ Orientation and Agile Foundations.

    The plan suggests reading the $ECO$ in full and mastering the Agile Manifesto and $12$ principles as everything flows from this foundation.

    • ✗ Full-length mock exams.

      Mock exams are scheduled for Weeks $8-9$ after a conceptual foundation has been built.

    • ✗ Framework deep dives into Scrum and Kanban.

      Framework deep dives follow the foundation phase, occurring in Weeks $3-5$.

    • ✗ Domain mastery of Value-Driven Delivery.

      Mastery of the seven specific domains is planned for Weeks $6-7$.

  11. 11 Which Udemy course is identified as being 'more like a syllabus than an actual course' and is primarily recommended only if accessible for free via enterprise accounts?

    This course is the shortest on the list and serves as an introductory guide on what to study rather than teaching the concepts.

    Chuck Cobb's 'How to Prepare For PMI-ACP Certification'.

    The reviewer suggests that while Chuck is an agile master, the course lacks full review content and acts more as a study guide or syllabus.

    • ✗ Tech Agilist's Practice Exams.

      This is described as a collection of six mock exams with almost $1000$ questions, not a syllabus-style overview.

    • ✗ Andrew Ramdayal's Full Training.

      This is recommended for those wanting a short, succinct way to get their $21$ contact hours quickly.

    • ✗ Sorin Dumitrascu's Agile Training.

      This is a very long ($22.5$ hours) in-depth course, the opposite of a short three-hour syllabus.

  12. 12 The 'Agile Practice Guide - Second Edition' is described as being 'framework-neutral.' What is the primary purpose of this design choice?

    Consider the need for organizations to adapt their delivery models to rapidly changing environments.

    To help practitioners choose fit-for-purpose approaches across predictive, agile, and hybrid life cycles.

    Framework neutrality allows the guide to reflect how agility is practiced across projects, products, and portfolios without favoring one specific methodology like Scrum.

    • ✗ To ensure that Scrum is the only framework mentioned for software development.

      The guide specifically expands to include Lean, Kanban, and hybrid models, which contradicts a Scrum-only focus.

    • ✗ To remove all references to specific methodologies and focus only on the $Agile$ $Manifesto$.

      The guide still covers foundations like Lean thinking and Kanban, but does so in an adaptable way for different environments.

    • ✗ To provide a direct replacement for the $PMBOK$ Guide.

      The guide is intended to complement $PMBOK$ concepts (like $PMBOK$ $8$), not replace them.

  13. 13 According to Greg Mester's blog, which book was previously listed as a $PMI-ACP$ reference but has been removed from the latest versions of the reference list?

    One of the authors of this removed book is a co-author of the Agile Manifesto.

    'Agile Project Management with Scrum' by Ken Schwaber.

    While Mester recommends it for its good examples, he notes it was removed from the most recent $PMI$ reference list.

    • ✗ 'Agile Estimating and Planning' by Mike Cohn.

      This remains a core part of the recommended list as of the posting date.

    • ✗ 'Kanban in Action' by Marcus Hammarberg.

      This was published in $2014$ and is still listed in the current reference material section of the blog.

    • ✗ 'Coaching Agile Teams' by Lyssa Adkins.

      Adkins' book remains a highly recommended resource for agile coaching knowledge on the $ACP$ list.

  14. 14 Brain Sensei's $PMI-ACP$ Exam Simulator contains how many realistic exam questions?

    The number is between $800$ and $900$ and includes unlimited practice retakes.

    $850$.

    The simulator dynamically generates exams from a bank of $850$ questions to provide a new experience each time.

    • ✗ $1,000$.

      While the Tech Agilist course offers almost $1000$ questions, Brain Sensei specifically lists $850$.

    • ✗ $120$.

      $120$ is the number of questions in each of their static exams, but the total bank is much larger.

    • ✗ $1,500$.

      $1,500$ is the question count provided for the Learners Ink $CAPM$ program.

  15. 15 What is the 'M.O.R.E.' acronym mentioned in the context of the $PMBOK$ Guide - Eighth Edition and the updated Agile Practice Guide?

    This acronym is part of the 'emerging practices' section in the new edition of the practice guide.

    A concept related to sustainability and adaptive ways of working.

    The source material mentions $M.O.R.E.$ in connection with sustainability and new concepts for the 2026 exam changes.

    • ✗ A framework for prioritizing user stories in Scrum.

      Priority frameworks like $MoSCoW$ are mentioned elsewhere, but $M.O.R.E.$ is linked to the 2026 standards update.

    • ✗ A list of $62$ servant leadership tasks.

      The tasks are part of Griffiths' 'Agile Illustrated' but are not referred to as $M.O.R.E.$

    • ✗ An acronym for $Mindset$, $Outcomes$, $Roles$, and $Environment$.

      While these are agile terms, the specific $M.O.R.E.$ acronym is associated with the sustainability-focused 2026 curriculum update.

  16. 16 In the comparison of Joseph Phillips versus Andrew Ramdayal, which instructor is described as approaching the course as a 'Scrum Master'?

    Consider the instructor whose course is noted for its high instructor rating and cross-over with traditional project management.

    Joseph Phillips.

    Phillips takes the Scrum Master perspective, whereas Ramdayal approaches it as an agile project manager.

    • ✗ Andrew Ramdayal.

      Ramdayal's approach is stated to be that of an agile project manager.

    • ✗ Both instructors.

      The YourDigitalAid FAQ explicitly notes a difference between their angles of approach.

    • ✗ Neither instructor.

      The reviewer provides a clear distinction between the two roles each instructor represents in their teaching style.

  17. 17 Why does the YourDigitalAid reviewer recommend the 'PM-prep cast' exam simulator despite reviewing several Udemy mock exams?

    Think about the benefits of 'testing fortitude' and familiarity with the software used on the day of the certification.

    It provides high-quality questions with a similar interface to the actual exam and was essential for the reviewer's pass.

    The reviewer states they would not have passed without it, emphasizing quality over the lower price of Udemy resources.

    • ✗ It is significantly cheaper than the Udemy courses.

      The review notes that it costs more money but is worth it for the quality and simulation experience.

    • ✗ It includes the $21$ contact hours required for the exam application.

      While some prep casts offer hours, this specific simulator is recommended for its testing interface and question quality.

    • ✗ It is the only simulator that covers $PMBOK$ $7$.

      The text mentions that some Udemy courses like Sorin's also cover $PMBOK$ $7$; the recommendation for PrepCast is based on realism.

  18. 18 According to the $vCare$ guide, which $ECO$ domains are typically the 'largest two knowledge domains' on the $PMI-ACP$ exam?

    These domains focus on the delivery of business value and the management of those involved in the project.

    Value-Driven Delivery and Stakeholder Engagement.

    These two are highlighted as the most significant domains, and the reviewer feels some courses could be more thorough in covering them.

    • ✗ Agile Mindset and Team Performance.

      While important foundations, they are not identified as the two largest domains by weight in the $vCare$ source.

    • ✗ Adaptive Planning and Problem Detection.

      These are part of the seven domains but do not carry the same primary weighting as Value-Driven Delivery.

    • ✗ Continuous Improvement and Agile Foundations.

      These domains are often tested through scenarios but are not the 'largest' in terms of domain weight.

  19. 19 Mike Griffiths' 'Beyond Agile' model is specifically designed to avoid which common pitfall in the project management industry?

    This term refers to a 'nearsighted' view where one methodology is seen as a universal solution.

    'Agile-myopia' - the belief that agile approaches can best solve every problem.

    The model advocates for situational knowledge, combining leadership, lean, agile, and plan-driven approaches as needed.

    • ✗ The lack of professional certification among team leads.

      While he writes about certification, 'Beyond Agile' is about the situational application of different project disciplines.

    • ✗ The failure to use $AI$ and GenAI in daily standups.

      While his new books cover $AI$, 'Beyond Agile' focuses on broader procedural selectivity and mindset.

    • ✗ The high cost of $PMI$ membership fees.

      The book is a professional delivery guide, not an analysis of membership costs.

  20. 20 Which specific technical delivery standard is linked to the updated coverage of $DevOps$ in the 'Agile Practice Guide - Second Edition'?

    These metrics are standard in the $DevOps$ industry for measuring deployment frequency and lead time.

    $DORA$ metrics.

    The guide includes $DORA$ metrics to help teams measure value delivery and flow in modern ecosystems.

    • ✗ $ISO$ $9001$.

      The text focuses on modern agile standards like $DevOps$ and $DORA$ rather than traditional quality management systems.

    • ✗ $IEEE$ Software Documentation standards.

      Agile delivery metrics like $DORA$ are prioritized over traditional documentation standards in the guide.

    • ✗ $Six$ $Sigma$ Green Belt standards.

      While Lean is mentioned, the specific metrics for modern delivery listed in the 2026 guide are $DORA$.

  21. 21 In the $YourDigitalAid$ review of Tech Agilist’s exams, what is noted as a unique 'Pro' for a relatively new course?

    Look for an indicator of the instructor's level of engagement with student comments.

    The instructor is very responsive and answers critical feedback in the reviews.

    Responsive instructors are valued for keeping new courses updated and clarifying confusing practice questions.

    • ✗ It is the only course that provides $21$ contact hours.

      This course is specifically a practice exam collection and does not provide the training hours.

    • ✗ It is taught by Joseph Phillips.

      The author is Tech Agilist, a different instructor from Joseph Phillips.

    • ✗ It includes a physical copy of the $Agile$ $Practice$ $Guide$.

      The course is a digital mock exam collection on $Udemy$ and does not include physical books.

  22. 22 What is the primary difference between $PMI-ACP$ and role-specific certifications like $CSM$ (Certified ScrumMaster) according to the $vCare$ guide?

    One certification is a broad 'practitioner' credential, while the other is focused on a single 'Master' role.

    The $ACP$ is framework-agnostic and covers multiple methodologies, while $CSM$ focuses exclusively on Scrum.

    The $ACP$ requires verified experience across many frameworks, whereas $CSM$ is role-specific with no experience requirement.

    • ✗ The $CSM$ is significantly harder and requires $100$ hours of study.

      The source material indicates the $PMI$ exams are by far the hardest ones compared to others like $CSM$.

    • ✗ Only the $CSM$ is recognized in software development industries.

      The $ACP$ is described as highly respected in software development, marketing, finance, and healthcare.

    • ✗ The $ACP$ can be earned in a two-day workshop, unlike the $CSM$.

      The $CSM$ is earned in a two-day workshop, while the $ACP$ requires $21$ hours of training and a formal application process.

  23. 23 Mike Griffiths' 'PM Illustrated' guide is based on content from which website created by the author?

    The name of the website is identical to the title of the visual guide book.

    $PMIllustrated.com$.

    The book 'PM Illustrated' is a visual learner's guide inspired by the content of this specific website.

    • ✗ $LeadingAnswers.com$.

      This is Griffiths' blog where he shares leadership insights, but the 'PM Illustrated' book name matches the specific site listed in the text.

    • ✗ $AgileAlliance.org$.

      The Agile Alliance is a partner for the Practice Guide, but not the source of Griffiths' specific visual guide website.

    • ✗ $PMI.org$.

      While he contributes to $PMI$, his illustrated books are based on his independent visual sites.

  24. 24 According to the $YourDigitalAid$ 'Conclusion', which of the following is an essential 'servant leader' trait to understand for the $PMI-ACP$ exam?

    Think of a leader who prioritizes the removal of obstacles to enable team success.

    Facilitating the team and 'carrying food and water' for them.

    This metaphorical phrase emphasizes the leader's role in removing impediments and supporting the team's needs.

    • ✗ Strict enforcement of the project schedule and deadlines.

      Servant leadership focuses on facilitation and support rather than command-and-control enforcement.

    • ✗ Assigning specific daily tasks to team members during standups.

      In agile, teams are self-organizing; a servant leader facilitates rather than assigns individual tasks.

    • ✗ Making all critical technical decisions for the team.

      Technical decisions are typically handled by the cross-functional team, not solely by the leader.

  25. 25 What is the recommended approach for the final two days before a scheduled $PMI-ACP$ exam, according to $vCare$ expert tips?

    Consider the advice regarding mental preparation and avoiding burnout right before a high-stakes test.

    Lighten the load, review key agile principles, rest well, and confirm logistics.

    The tips advise against studying the day before the exam, suggesting that rest and high-level review are more effective.

    • ✗ Take at least two full-length mock exams each day.

      The guide suggests taking the final mock exam three to four days before the actual date, not in the final two days.

    • ✗ Memorize the 'reading list' of $20$ books provided by $PMI$.

      Memorization of laundry lists is noted as being ineffective for the situational nature of the exam.

    • ✗ Focus entirely on the mathematical formulas for $PMP$.

      $PMP$ math is often considered extra 'fluff' for the $ACP$, which is more scenario-based.