PMI-ACP Exam Dumps - PMI Agile Questions and Answers

A value stream map is an effective tool for identifying and visualizing the flow of work and the associated delays or handoffs in a process. By mapping out the entire value stream, the team can identify inefficiencies, waste, and bottlenecks, which helps them target areas for improvement. This allows the team to optimize the workflow by reducing unnecessary handovers and delays, which is in line with their goal of improving efficiency.

The presence of a single point of knowledge is a significant risk in agile teams. According to the PMI Agile Practice Guide (Section 4.3.3: Team Structure and Cross-functionality) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 3: Team Performance), agile teams should avoid role silos and promote knowledge sharing. Adding another database administrator helps with both workload distribution and knowledge retention through pairing or mentoring.

Option C is correct: it ensures redundancy and knowledge spread, reducing project risk.

Option A does not address knowledge transfer or team development.

Option B removes the knowledge resource, worsening the risk.

Option D limits knowledge-sharing and still creates a bottleneck.

Step 1: Identify Total Story Points in the Backlog

From the backlog table:

Total story points = 6 + 4 + 8 + 4 + 21 + 7 + 5 + 9 + 3 + 5 = 72

Step 2: Determine the Team ' s Velocity

The risk register mentions a burn reduction of 1 story point per sprint from sprint 4 to sprint 6 due to a holiday schedule. However, assuming a normal velocity of 5 story points per sprint, we can estimate sprint completion.

Normal sprint velocity: 5 story points per sprint

Reduced velocity for sprints 4-6: 4 story points per sprint

Step 3: Calculate Total Sprints Needed

First 3 sprints: 5 points per sprint → 5 × 3 = 15 story points completed

Sprints 4-6: 4 points per sprint → 4 × 3 = 12 story points completed

Remaining story points after sprint 6: 72 - (15 + 12) = 45 story points

Remaining sprints needed at normal velocity (5 story points per sprint): 45 ÷ 5 = 9 sprints

Total Sprints Required

Sprints 1-6: Already planned.

Additional 9 sprints needed.

Total sprints to complete the backlog: 6 + 9 = 15 sprints.

In the context of the chatbot ' s post-release complaints about edge cases in query responses, User Acceptance Testing (UAT) is the most critical step to avoid such situations. UAT ensures that the chatbot meets the stakeholder ' s needs and expectations, which would have included verifying its behavior with real users under real-world scenarios. This step would identify any edge case issues and make sure the chatbot is aligned with business goals before going live.

Knowledge sharing and organizational learning are core elements of scaling agile. According to the PMI Agile Practice Guide (Section 8.4 Organizational Change Management) and the PMBOK® Guide (6th Edition, Section 10.2 Manage Communications), the project manager should actively disseminate lessons learned, best practices, and project outcomes to promote agile adoption across the organization.

Mike Griffiths reinforces in the PMI-ACP Exam Prep Book (Chapter 7: Continuous Improvement) that continuous feedback loops and transparent communication are essential to agile transformation success.

Option D is correct because regular meetings specifically focused on sharing outcomes and learning from the pilot project help embed agile values and improve future implementations.

The correct answer is B – Break the story up and focus on the most valuable parts. Agile promotes progressive elaboration, and large or complex stories (epics) should be broken down into smaller, testable user stories. This practice enables clarity, faster feedback, and more accurate planning.

From the PMI Agile Practice Guide:

“Large stories (epics) should be split into smaller user stories to enable understanding, estimation, and incremental delivery. Stories should be small enough to be completed within an iteration.”

(PMI Agile Practice Guide, Section 5.3 – User Stories and Story Splitting)

Mike Griffiths states:

“When a user story is too large or unclear, the team should break it down into smaller pieces, focusing on the most valuable parts first. Story splitting is a key agile practice.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A discourages collaboration and learning.

C delays the resolution unnecessarily.

D avoids solving the actual problem and abandons valuable work.

Answer: B

────────────────────────────────────

In this scenario, the development team is working closely with different business units to deliver value early and often. This aligns with the agile value of delivering working software frequently, with a preference for shorter timescales. By collaborating with business units, the team is enabling early feedback and adapting to changing requirements, which is a core principle of agile methodologies like Scrum.

The correct answer is D — Up-to-date project radiators.

Information radiators provide at-a-glance visibility into project status, progress, blockers, and other key metrics. Sharing or including these visual tools in extended stakeholder communication ensures transparency and up-to-date awareness, which aligns with agile values.

PMI Agile Practice Guide:

“Information radiators provide immediate and transparent access to project health and status. They reduce the need for formal reporting and keep stakeholders aligned in real time.”

(PMI Agile Practice Guide, Section 5.6 – Information Radiators)

Mike Griffiths:

“Using radiators to keep stakeholders informed improves trust, accelerates decision-making, and supports ongoing engagement.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

A and B are not relevant for stakeholder reporting.

C is too narrow and lacks the holistic view offered by radiators.

Answer: D

When comparing total scope (story points) and velocity, you can calculate the number of sprints each team expects:

Team A: 420 / 30 = 14 sprints

Team B: 280 / 20 = 14 sprints

Even though the story points are different, both teams estimate the same number of sprints, which means they estimate similar effort and duration relative to their own internal baselines. This aligns with the concept that story points are relative and not comparable across teams.

PMI Agile Practice Guide (Section 5.4: Velocity and Relative Estimation) and Mike Griffiths’ PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) explain that velocity is a team-specific measure and cannot be directly compared between teams.

Option D is correct: both teams have estimated the same project size in their own context.

Options A and B incorrectly compare velocity between teams.

Option C is irrelevant; velocity is based on team experience, not technology assumptions.

The correct answer is D — Explain to the team the importance of reducing team size by reducing specializations and bottlenecks and that every team member plays an equal part.

Agile promotes cross-functional, self-organizing teams where all members are responsible for delivering a working product increment. Avoiding specialized silos reduces bottlenecks and improves overall flow. Everyone contributes based on team needs, not personal preferences or status.

PMI Agile Practice Guide:

“Agile teams minimize individual silos by encouraging cross-functional collaboration. Everyone contributes to the team goal, even if the task is outside their core skillset.”

(PMI Agile Practice Guide, Section 6.1 – Team Composition)

Mike Griffiths:

“Specialization often becomes a bottleneck in agile teams. Agile promotes generalizing specialists—team members who are willing to stretch outside their expertise to help the team meet its goals.”

(PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A promotes a command-and-control model—contrary to Agile servant leadership.

B reinforces silos and inefficiency.

C contradicts Agile’s emphasis on team ownership.

Answer: D

—