PMI-ACP Delivery — 10 Questions

Question 1

Which document is most important for defining the product vision?

Accepted Answer

Product Roadmap.. The product roadmap is the artifact that communicates the product vision over time, showing the sequence of releases, themes, and outcomes that realize the vision. It aligns stakeholders and the team on where the product is heading and why, making it the most important document for defining and conveying product vision. While the vision statement itself is concise, the roadmap operationalizes it.

Answer

Team calendar.

Answer

Sprint burndown.

Answer

Meeting minutes.

Question 2

The project stakeholders are unhappy because the delivered features do not align with the current organizational priorities. What should the practitioner do first?

Accepted Answer

Conduct a backlog grooming session with stakeholders to reprioritize based on business value.. When stakeholders report that delivered features don't match current organizational priorities, the root cause is almost always a stale or misaligned product backlog. The Product Owner owns backlog ordering, so the correct first move is to convene stakeholders and the PO to re-evaluate and reprioritize backlog items by business value. This restores alignment before any delivery work continues.

Answer

Ask the team to work overtime to finish the backlog faster.

Answer

Update the release burn-down chart to reflect current progress.

Answer

Change the definition of done to speed up delivery.

Question 3

An agile team is coordinating tasks across multiple cross-functional teams. Which meeting is most effective for synchronizing dependencies?

Accepted Answer

Scrum of Scrums.. The Scrum of Scrums is a scaled-agile ceremony where representatives (usually one per team) from multiple Scrum teams meet regularly to coordinate cross-team dependencies, integration points, and impediments. It is specifically designed to synchronize work across teams that share a product or delivery goal. Daily Stand-ups synchronize work within a single team, not across teams.

Answer

Sprint Retrospective.

Answer

Daily Stand-up.

Answer

Sprint Planning.

Question 4

During sprint planning, a team discovers that their velocity has decreased by 20% over the last two iterations. What should the team do first?

Accepted Answer

Review the retrospective notes from the last two sprints to identify systemic blockers.. A 20% velocity drop over two iterations is a systemic signal, and the retrospective notes from those sprints are the team's own record of what changed — blockers, impediments, and experiments. Reviewing them first lets the team identify recurring root causes before adjusting plans or estimates. This is the empirical, data-driven first step consistent with agile practice.

Answer

Increase the story point estimates to account for the decrease.

Answer

Reduce the team size to improve communication overhead.

Answer

Commit to the same number of story points to pressure the team to improve.

Question 5

A team is coordinating releases across three different scrum teams working on the same product. Which THREE practices should be utilized?

Accepted Answer

Assign a single Product Owner to maintain a unified product backlog.. Option B is correct because when multiple Scrum teams build one product, a single Product Owner with one unified product backlog keeps priorities, value ordering, and acceptance criteria consistent across teams, preventing divergent backlogs. Option D is correct because joint refinement (e.g., shared backlog refinement sessions) lets teams surface and clarify cross-team dependencies, interfaces, and shared acceptance criteria before Sprint Planning, reducing integration risk. Option E is correct because the Scrum of Scrums is the scaled-agile practice for synchronizing multiple teams, where delegates coordinate progress, impediments, and cross-team dependencies. Option A is wrong because reporting directly to a Portfolio Manager for daily tasks breaks Scrum's self-managing team model and the Product Owner's accountability for value. Option C is wrong because deliberately differing iteration lengths across teams on the same product increases synchronization and integration problems rather than avoiding them.

Answer

Require every team to report directly to the Portfolio Manager for daily tasks.

Answer

Mandate that each team has a different iteration length to avoid meeting conflicts.

Question 6

An organization is moving from project-based to product-based funding. How should the agile practitioner advise the team to measure success?

Accepted Answer

Utilize value-based metrics like Net Promoter Score (NPS) and Customer Acquisition Cost (CAC).. Moving from project-based to product-based funding shifts the focus from output and budget adherence to delivered customer and business value. Value-based metrics such as Net Promoter Score and Customer Acquisition Cost directly measure whether the product is achieving meaningful outcomes for users and the business. This aligns with the product mindset's emphasis on outcomes over outputs.

Answer

Report primarily on task completion percentages from the Jira dashboard.

Answer

Track the number of features delivered per quarter.

Answer

Focus on budget adherence and total project spend.

Question 7

A cross-functional team is experiencing long lead times for feature delivery. Which TWO actions would help optimize the end-to-end flow?

Accepted Answer

Map the value stream to identify and eliminate non-value-added activities.. Option B is correct because mapping the value stream makes all steps, handoffs, and delays in the end-to-end flow visible, allowing the team to identify and eliminate non-value-added activities (waste) that inflate lead time. Option E is correct because enforcing a strict Work-In-Progress (WIP) limit constrains the amount of work in the system, reduces multitasking and queue buildup, and improves flow efficiency and throughput, which directly shortens lead times. Outsourcing testing (A) may add coordination overhead and handoff delays rather than optimize flow, and it does not address the root causes of long lead times. Adding a QA gate at the end (C) inserts an additional approval/verification step that can increase wait time and batch size, worsening flow. Doubling daily stand-ups (D) increases meeting overhead without removing the systemic bottlenecks that cause long lead times.

Answer

Outsource the testing phase to a specialized third-party vendor.

Answer

Add a quality assurance gate at the end of the development lifecycle.

Answer

Increase the frequency of daily stand-ups to two times per day.

Question 8

A team is struggling with frequent context switching during their sprint. Which lean technique should the practitioner implement to optimize end-to-end flow?

Accepted Answer

Implement strict Work In Progress (WIP) limits on the Kanban board.. Implementing strict WIP limits on the Kanban board directly addresses context switching by constraining the number of items a team can work on simultaneously. When WIP limits are enforced, team members are forced to finish current work before pulling new tasks, which reduces multitasking and improves flow efficiency. This lean technique is grounded in Little's Law (Cycle Time = WIP / Throughput), meaning reducing WIP directly shortens cycle time and accelerates end-to-end delivery. Thus, WIP limits are the most effective lean tool for optimizing flow and eliminating the waste of context switching.

Answer

Add more team members to distribute the workload.

Answer

Conduct a daily stand-up meeting for longer durations.

Answer

Increase the sprint duration to allow more time for tasks.

Question 9

A team is struggling to maintain a consistent cadence due to external dependencies. Which action best aligns with optimizing end-to-end flow?

Accepted Answer

Implement a formal dependency board to visualize blockers and upstream/downstream impacts.. A dependency board makes external blockers and their upstream/downstream impacts visible to the whole team, which is the core mechanism for optimizing end-to-end flow in Kanban/agile practice. Visualizing dependencies lets the team swarm on blockers, re-sequence work, and escalate early rather than discovering delays at sprint review. This directly addresses the root cause (unmanaged external dependencies) without changing the team's cadence.

Answer

Switch to Kanban to eliminate the need for sprint planning.

Answer

Lengthen the sprint duration to allow more time for external teams to respond.

Answer

Assign a dedicated project manager to track dependency status manually.

Question 10

Which metric is most useful for measuring the team's ability to deliver consistent value per iteration?

Accepted Answer

Velocity.. Velocity measures the amount of work (typically in story points) a team completes per iteration, making it the standard metric for gauging consistent value delivery across sprints. Tracking velocity over time reveals whether the team's throughput is stable, improving, or erratic, which directly reflects their ability to deliver predictably each iteration. It is a team-level metric, not an individual one, aligning with agile principles.

Answer

Individual task duration.

Answer

Team morale survey scores.

Answer

Number of meetings attended.