PMI-ACP Practice Questions

A.  

Coach the product owner to update only the acceptance criteria.

B.  

Instruct the agile team to fix the user stories during the next retrospective.

C.  

Facilitate a user story workshop with the agile team.

D.  

Inform the product owner's manager that the work items provide insufficient detail.

A.  

Set up individual status meetings and find ways to make sure issues are resolved in advance so that time is not wasted for all team members during the standups

B.  

Add time to the standups to accommodate issue-resolution discussions so that everyone is up to date on the decisions made

C.  

Change the standups to weekly status meetings with a longer duration to allow team members to resolve issues collaboratively

D.  

Ask team members to raise issues during standups and then discuss resolution options with specific members in separate conversations

A.  

The team is being proactive by discussing how to better balance demands and capacity and make sure they have the right competencies.

B.  

The team shows respect for one another by listening to everyone's opinions and valuing human interaction during face-to-face meetings.

C.  

The team is providing one another with fast feedback to find those responsible for any mistakes so they can be avoided in the future.

D.  

The team eliminates potential waste by discussing who should be responsible for future risk management by actively applying the pi an-do-check-act (PDCA) method.

A.  

The team will be unable to understand the iteration's status

B.  

The team will be unable to judge the project design's validity

C.  

The team cannot give accurate updates to management

D.  

Team collaboration cannot be measured effectively

A.  

Raise an impediment that resource tasks will be blocked and notify the Product Owner

B.  

Ask the delivery manager for a temporary resource

C.  

Ask the Scrum Master to assign that team member's tasks to the next available resource

D.  

Assume the team member's tasks to meet iteration goals and notify the Product Owner

A.  

The Kanban approach relies on storyboards.

B.  

The Kanban approach focuses on adaptive, simultaneous workflows.

C.  

There are no work-in-process limits in the Kanban approach.

D.  

Kanban teams employ a pull system.

A.  

Bring up the new member's impediments at the next meeting to demonstrate team support of input

B.  

Assure the new member that inputs on impediments are valued and demonstrate this at the next meeting

C.  

Have a senior lead work with the new member to avoid a negative impact on team productivity

D.  

Privately work with the new member to address any impediments

A.  

Take a few minutes to speak with the developer after the daily coordination meeting and provide clarification.

B.  

Follow the appropriate channels by contacting the product owner and asking them to address the issue with the team.

C.  

Wait until the sprint review to explain how the product increment needs to be changed to be acceptable.

D.  

Speak up immediately during the daily coordination meeting and clarity the issue to avoid any further confusion.

A.  

Replace the team member with a more collaborative individual.

B.  

Permit the team member to continue influencing because agile teams are self-organizing.

C.  

Ask probing questions to other team members to encourage dissenting viewpoints.

D.  

Intervene if the team's velocity drops.

A.  

Refocus the sprint review meetings to demonstrate working software and seek feedback on the product.

B.  

Reach out to other, more experienced teams to seek input as to how to present the technical details in a more informative manner.

C.  

Explain the importance of the technical architecture and design presentations and improve the presentation format.

D.  

Invite technical managers and architects who will be a more appropriate audience to their sprint reviews.