PMI-ACP Practice Questions

A.  

The objective, iterations and underlying features, iteration timelines, other pre-release activities, dependencies, and responsible team.

B.  

The key objectives and a brief description of each user story to be delivered in each iteration release timelines and release dependencies

C.  

The developer who will work on a specific feature and key DevOgs engineering activities to be performed during each iteration for the code integration.

D.  

The sequence of user stories to be developed in each iteration, along with their start and end timelines, dependencies, and responsible team.

A.  

Communicate the importance of the business need to the team and refine the product backlog.

B.  

Ask the team to discuss the changes to the features with the customer.

C.  

Meet with the agile team lead to prioritize the requirements.

D.  

Discuss and prioritize the requirements with the team.

A.  

Explain to the client that the sprint deadline is approaching and the feature can be included in the next iteration.

B.  

Remind the team and the client of the importance of assessing the risks of these features before deciding to include them

C.  

Negotiate with the team to add the additional features in this sprint because they are important requirements.

D.  

Ask the client for an extension of the deadline to enable delivery of this sprint with the additional features.

A.  

The team member that is complaining should talk individually with the scrum master to remove impediments.

B.  

They should ask for more details about the impediments and then resolve them when the team has more time to investigate.

C.  

The team member that is complaining should address the impediments in daily scrum, communicating them directly.

D.  

Team members should state that they need to prioritize their work instead of responding to daily emails about impediments.

A.  

Be transparent with all the stakeholders and make them aware of the issues encountered and the current project's status.

B.  

Ensure the agile leader documents a risk in the risk register and communicates the risk to the project sponsor.

C.  

Support the team's decision, and since the team is confident about being able to resolve the issues in time, do not raise the issues as risks with the stakeholders.

D.  

Ask the product owner to make a decision as to whether or not all the stakeholders should be kept informed about the current project's status.

A.  

Team members are sending more emails to the team.

B.  

The duration of feedback cycles has increased.

C.  

The velocity has increased by having the new team work on items.

D.  

New team members requested to move meetings due to time differences.

A.  

Include it in the product backlog and use a new indicator to annotate that it is technical debt

B.  

Include it in the product backlog as a low-priority issue

C.  

Since it is not a part of Agile methodologies, it should not be tracked

D.  

Have team members maintain personal lists of issues and consolidate the lists during review

A.  

Inform the stakeholder that all updates are provided in the sprint review sessions and encourage them to attend.

B.  

Create and update bi-weekly project status reports for the stakeholder who requested the report.

C.  

Escalate this to the stakeholder's supervisor because this is an unreasonable request.

D.  

Ignore the stakeholder's request and continue working on the project as they have been for the past six weeks.

A.  

They most likely used a process that was successfully used for other projects; what has worked before is less likely to fail.

B.  

They most likely discussed the best approach for this project with the team and will adapt and tailor the approach periodically by reviewing and verifying the scope with the customer.

C.  

They most likely requested an increase in the management reserve; this will help the project manager to be more flexible during change requests and risk response activities.

D.  

They most likely implemented a predictive approach; this approach might limit the freedom of making changes but secures the project from unknown risks.

A.  

Set up weekly calls with the key stakeholders to participate in iteration reviews and release decisions.

B.  

Analyze the impacts of these constraints on the project followed by a report sent to the sponsor to anticipate any risk of delays.

C.  

Set up a meeting with the client to review the scope and timelines to manage expectations.

D.  

Encourage the team to build increments and ensure the customer provides early feedback for a minimum viable product.