PMI-ACP Practice Questions

A.  

Ask the agile practitioner to help write the user stories.

B.  

Ask the agile team to facilitate a story-writing workshop.

C.  

Ask subject matter experts (SMEs) to help write the user stories.

D.  

Ask the agile practitioner to facilitate a story-writing workshop.

A.  

Put the client first.

B.  

Create a safe environment.

C.  

Practice continuous delivery.

D.  

Manage risk.

A.  

Develop and distribute a high-level summary of how Agile offers greater benefit than predictive to mid-level managers and let them decide if it should be distributed to lower-level workers.

B.  

Develop and distribute a high-level summary of competing vendors' product alignment and Agile project execution to the Product Owner for approval.

C.  

Develop and distribute a high-level summary of how Agile offers greater benefits than predictive to all members of the organization.

D.  

Develop and distribute a high-level summary of how Agile offers greater benefits than predictive to the organization's executive directors, and if executive directors agree with the summary, distribute it organization-wide.

A.  

Report this as a blocker and ask senior management to provide the right subject matter experts (SMEs) until all the outstanding issues can be dosed.

B.  

Identify the key business stakeholders and invite them to day-long sessions until all the dependencies and outstanding issues can be closed.

C.  

Identify the key dependencies that need to be resolved in order of priority level so the user stories can meet the definition of ready (DoR) criteria.

D.  

Report this as a blocker and ensure the product owner is able to deprioritize the issues so the user stories can meet the definition of ready (DoR) criteria.

A.  

Assign the spike to another resource to continue research for the long-term solution

B.  

Re-establish the spike; encourage experimentation and collaborate with the team

C.  

Stop experimentation and negotiate the short-term solution with the customer

D.  

Schedule a root-cause analysis with the development team on the main issues with the spike

A.  

Collaborate with the product owner to reprioritize the product backlog, thus ensuring that more features will be completed before the release.

B.  

Ask the team lead to calculate the team's target velocity according to the project plan, and assign additional resources to increase capacity.

C.  

Focus on velocity and schedule concerns during the retrospective to inspect, adapt, and improve the process and plans.

D.  

Reestimate the backlog items from the release, ensuring that contingency is included to set stakeholder expectations.

A.  

The entire team is responsible for quality and each team member is accountable for ensuring the success of every component.

B.  

The entire team is responsible for quality, but each team member's role may vary as stated in the definition of done (DoD).

C.  

The entire team is responsible for quality and QA is responsible for surprises, gaps, and other intricacies that may have been overlooked.

D.  

Quality is the responsibility of the entire team, and the Product Manager defines the functionality from end to end.

A.  

Work with the scrum master to give the stakeholder access to the related information radiator

B.  

Invite the stakeholder to the next sprint planning session so they can ask questions of the team

C.  

Ask the team to prepare the requested data in the next iteration

D.  

Direct the stakeholder to the project team so they can provide more data

A.  

Proceed with the work only after the contract is amended.

B.  

Discuss the value of the change for the project with the customer.

C.  

Evaluate effort and impact and ask for steering committee and shareholder approval.

D.  

Stick with the contract terms and agree to review the requirement if time allows.

A.  

Invite the team to iteration review meetings

B.  

Obtain agreement from the product owner on business requirements

C.  

Request that regular reports are sent to stakeholders

D.  

Confirm managers and stakeholders are invited to product review meetings