PMI-200 Practice Questions

A.  

Teach the team the appropriate agile principle, obtain consensus, and drive adoption.

B.  

Allow another team member to prepare those documents that do not appear to bring value.

C.  

Notify the project manager about other documentation techniques, and identify which documents bring value and which do not.

D.  

Follow the existing process to avoid conflicts.

A.  

Implementing a systematic approach to automate integration, testing, and deployment activities

B.  

Increasing the frequency of stakeholder meetings to gather feedback on feature priorities

C.  

Leveraging regular reviews, feedback loops, and lessons learned to adjust at key milestones

D.  

Organizing training sessions for end users to ensure effective utilization of the planning tool

A.  

Project sponsor and project team

B.  

Scrum master

C.  

Product owner

D.  

Stakeholders and project team

A.  

To produce a fast return on investment

B.  

To reduce risk as quickly as possible

C.  

To gain competitive advantage as soon as possible

D.  

To maintain visibility with project stakeholders

A.  

Conduct an architectural spike immediately to decide how the functionality will be determined.

B.  

Work with the product owner to avoid the risk by determining if their requirements could be met with reporting or a similar functionality.

C.  

Continue the priority defined by the product owner on the backlog for the functionality they determined to be the highest priority.

D.  

Identify this as a risk, decide on the response, and prioritize spike to determine the solution on the product backlog.

A.  

Daily standups

B.  

Iteration and release planning

C.  

Training in areas of weakness

D.  

Iteration

A.  

Implement the story since the team is running behind schedule.

B.  

Create a spike to finalize the story's technical approach.

C.  

Transfer the story to a scrum team experienced in solving similar problems.

D.  

Ask the product owner to reduce the story's priority and wait until more technical details are available.

A.  

Add code cleanup activities to the product backlog and request prioritization by the product owner

B.  

Add code cleanup activities to the next iteration and request clarification from the product owner

C.  

Add code cleanup activities to the next iteration and ask the product owner to end the current iteration

D.  

Add code cleanup activities to the next release backlog and request documentation from the product owner

A.  

Add a task to the product backlog to allow the team time to investigate and experiment prior to estimating.

B.  

Add a task to the product backlog to allow the team to apply a wideband Delphi estimation technique.

C.  

Add a task to the product backlog to allow the team to apply planning poker to estimate the effort.

D.  

Add a task to the product backlog to allow the team to apply a three-point estimation technique.

A.  

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.

B.  

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.

C.  

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

D.  

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