PMI-ACP Exam Dumps - PMI Agile Certified Practitioner (PMI-ACP)

The correct answer is A – To participate in establishing a shared vision as a member of the team.

Stakeholder engagement ensures alignment between the team and business needs. Early and continuous involvement helps define product vision, clarify priorities, and ensure that the delivered product meets customer expectations.

From the PMI Agile Practice Guide:

“Engaging stakeholders early and often increases transparency, encourages shared ownership, and ensures that the product being developed aligns with business value.”

(PMI Agile Practice Guide, Section 4.2 – Stakeholder Engagement)

Mike Griffiths reinforces:

“Projects are more successful when stakeholders co-create the product vision and maintain involvement. Agile teams encourage active participation to ensure delivery of value.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 – Stakeholder Engagement)

Why other options fall short:

B (acceptance criteria) is mainly defined by the Product Owner, not all stakeholders.

C is typically owned by the development team.

D is not a core stakeholder responsibility in Agile.

Answer: A

══════════════════════════════════════════════════

The team lead should work to resolve the conflict by negotiating with the project director. Since the lead developer cannot complete their work due to the request for a detailed testing plan, the team lead should seek to limit the scope of the documentation request. By negotiating for fewer details or a reduced scope of testing documentation, the team can continue their work on the iteration while still meeting the project director's needs. This approach balances the need to progress with development and address the request without causing significant delays.

The correct answer is A – Use the DISC framework with each team member.

The DISC model (Dominance, Influence, Steadiness, and Conscientiousness) is a well-established behavioral assessment tool used to understand communication preferences, motivators, and individual work styles. Agile leaders may use tools like DISC to foster emotional intelligence, improve collaboration, and re-engage disengaged team members.

From the PMI Agile Practice Guide:

“Effective agile leaders understand individual team members' communication styles and motivations. Tools such as DISC or MBTI can help assess personality preferences and enable better coaching.”

(PMI Agile Practice Guide, Section 6.2 – Coaching Agile Teams)

Mike Griffiths notes:

“Behavioral models such as DISC support the development of emotionally intelligent teams. They help leaders tailor their coaching and communication approaches to individual needs.”

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

Why other options are incorrect:

B (MoSCoW) is a prioritization technique, not a tool for personal engagement.

C (Hiring a SAFe coach) is overkill and not the most direct or relevant response.

D (BDUF – Big Design Up Front) is a traditional approach unrelated to team dynamics or motivation.

Answer: A

In Agile, it's important to continuously refine and prioritize requirements while managing dependencies. The team should work collaboratively to identify and prioritize the key dependencies that must be resolved to ensure that the user stories meet the Definition of Ready (DoR) criteria. By focusing on the highest priority dependencies first, the team can maintain progress while adapting to changes, rather than getting stalled trying to resolve all dependencies at once. This allows for more flexibility and efficient delivery.

The correct answer is C – Ensure the team captures the technical dependencies as issues within the backlog and prioritize based on value optimization. In Agile, technical considerations are factored into backlog refinement and sprint planning. Dependencies should be visualized and managed as part of adaptive planning while still striving to deliver maximum value.

From the PMI Agile Practice Guide:

“Backlog items with technical dependencies should be identified and addressed collaboratively. Agile teams balance value with feasibility and technical constraints to optimize delivery.”

(PMI Agile Practice Guide, Section 5.3 – Backlog Refinement and Adaptive Planning)

Mike Griffiths explains:

“While business value drives prioritization, technical constraints influence the ordering of stories. Agile planning is adaptive; dependencies and delivery risks are identified early and managed through backlog reordering.”

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

Incorrect options:

A may discard valuable features unnecessarily.

B risks accumulating technical debt and incomplete work.

D shifts responsibility away from the team and PO unnecessarily.

Answer: C

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

In agile, when uncertainty exists around a technical or functional aspect of work, the team can use aspike—a time-boxed research or prototyping activity—to explore the unknown. According to thePMI Agile Practice Guide (Section 5.2 User Stories and Spikes),spikes are ideal when the team lacks information or confidenceabout a proposed solution and needs to experiment before committing.

Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning)explains thatspikes are used to investigate technical approaches, prove concepts, or explore new technologies, and they provide the team with the insight and confidence needed to proceed with less risk.

Option Ais correct because a spike would allow the team to explore the new framework in a controlled way.

Other options such asIshikawa diagrams (B),pre-mortems (C), andtrend analysis (D)are useful in other contexts, but not suitable for increasing confidence in new technical implementation approaches.

Effective stakeholder engagement starts withshared understanding and agreement on goals and requirements. ThePMI Agile Practice Guide (Section 7.2 Stakeholder Engagement)emphasizes the need tocollaborate with stakeholders early and often, especially on prioritization and epic-level expectations.

Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement)underscores thatmisunderstandings are reduced when all parties are aligned on what "done" means, and epics and requirements arecollaboratively defined.

Option Ais correct: agreement and shared understanding reduce misalignment and conflict.

Option Bintroduces unnecessary delays in planning.

Option Cis useful but insufficient if initial requirements are misunderstood.

Option Dmay help in contract terms but doesn’t solve day-to-day misalignment.

The scrum master should first remind the team of the purpose and goals of each scrum event (such as the daily standup, sprint planning, sprint review, and retrospective) to ensure that they remain focused on their intended outcomes. The scrum master can then implement a policy that ensures discussions that deviate from the scope of the event are stopped. This approach keeps the team on track, prevents time-wasting conversations, and helps maintain the efficiency of the events.

This method empowers the team to stay focused on what is essential for each event and encourages self-management while still providing room for relevant discussions. In doing so, the team can achieve the desired outcomes of each scrum event without unnecessary delays.