PMI-200 Exam Dumps - PMI ACP Questions and Answers

A list of templates to be used to create the project vision

A list of project stakeholders and user stories

A checklist for future acceptance tests for project deliverables

A list of questions for the team and customer representative

Complete the test cases before creating the story in the backlog

Define the detailed business requirements so that the team can continue with development

Define the user stones with just enough details so the team can collaborate continuously

Ensure the acceptance criteria includes testing scenarios, so the team can do thorough testing

Team members are sending more emails to the team.

The duration of feedback cycles has increased.

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

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

Meet individually with each team member to identify the issues and relay information to the remaining members through status reports.

Establish a live video feed between the dispersed teams to enable spontaneous engagement and collaboration on issues.

Request that the customer co-locate the team to overcome the communication issues, as this is the only method to ensure agility.

Inform the customer of the challenges and lower velocity of the project to accommodate for the slower delivery pace.

Encourage the product owner and team to reprioritize the features and select ones which can be delivered without any dependencies

Encourage the team to continue with the current plan, do what they can. and carry forward the work not done to the next iteration

Ensure the team captures the technical dependencies as issues within the backlog and prioritize based on value optimization

Ensure that the required subject matter experts (SMEs) are engaged by the product owner to help with backlog prioritization

Inform the product owner's manager so that corrective action may be taken.

Communicate this to the product owner, and offer to help facilitate discussions with the team.

Encourage a team member to raise this during the retrospective to ensure that the product owner is aware.

Escalate this issue to the sponsor so that corrective action may be taken.

Conduct a requirements gathering workshop.

Deliver the basic requirements iteratively.

Have the product owner fill out the requirements backlog.

Have the stakeholders fill out the backlog before starling the project.

Issue fixed agendas and a decision log for all scrum events to ensure that only relevant agenda points are discussed and decisions are appropriately captured.

Remind the team of the purpose of each scrum event, and implement a policy that long conversations deviating from the scope of each event will be stopped.

Ask the product owner to conduct these discussions in individual meetings with the team members.

Remind the team that staying on topic during meetings is part of being a self-managing team.

Commit to a specific feature set for delivery

Explain that a commitment will be provided after planning

Have the team estimate in story points to commit to a specific set of features

Use the team's historical velocity to calculate a range of features that can be delivered

Building openness and transparency on the project's health and status

Facilitating conflict resolution among executive team members

Using active stakeholder involvement to build features in an incremental and iterative approach

Seeking continuous feedback from executive team members