PMI-200 Practice Questions

A.  

Re-estimate the project.

B.  

Finish the product as it was initially planned.

C.  

Try to include as many changes as possible.

D.  

Ask the product owner for approval to proceed.

A.  

Ask the developers to keep their estimation so that the team is transparent with their level of understanding of work.

B.  

Agree with the team to keep their estimation as the final number of story points will be the average of all team members.

C.  

Propose to consider the estimations of only senior developers and have the junior developers learn from them.

D.  

Encourage the team to keep their estimation as this will help surface different constraints and assumptions that others might have missed.

A.  

Plan for the second release to include regulatory changes and new features.

B.  

Hold off making changes during the current release because the regulatory changes cannot be planned for.

C.  

Verify the team is building the product in increments which can be adapted at the last minute if necessary.

D.  

Monitor regulatory discussions to get a head start on the upcoming regulatory changes.

A.  

The importance of customer-centric product development practices over product-centric approaches.

B.  

Deliver working software often with a preference for shorter timescales and changing requirements

C.  

The belief that contributions and interactions are more important to success than processes and tools.

D.  

The best architectures, requirements, and designs emerge from self-organizing teams.

A.  

Speak to the agile lead about the concerns.

B.  

Follow the agile lead's instructions.

C.  

Increase the time worked to meet objectives.

D.  

Speak to all team members about the concerns.

A.  

The agile team should engage stakeholders regarding the proposed designs and ensure that sufficient engagement occurs throughout the project in an adaptive way.

B.  

The agile practitioner should inform the stakeholders that the Ul has already been approved by the project team and the project sponsor, so the team is committed to staying the course.

C.  

All stakeholders should go through the approved project charter and the business requirements document to reduce the number of late changes or requests.

D.  

The stakeholders should contact the project sponsor to get the project halted until new requirements are agreed upon.

A.  

Estimate the project team's capacity.

B.  

Determine how much work can be delivered.

C.  

Calculate how much work will fit into the next iteration.

D.  

Estimate items in the product backlog.

A.  

The team neglected to account for support and maintenance costs associated with other supported products

B.  

The team discovered that previously accepted work could be greatly improved and added story points associated with thatwork.

C.  

The team realized that some stories were underestimated relative to other stories and reestimated as needed

D.  

The team learned that the product owner needed to increase the output in the next release

A.  

Review established ground rules with the team

B.  

Ask team members specific questions to identify the cause

C.  

Encourage the team to continue working to maintain the iteration's schedule

D.  

Meet with the product owner and stakeholders to discuss the issue

A.  

Engage the change management team to determine prioritization of the backlog.

B.  

Allow the stakeholders to decide on the priority and build the backlog.

C.  

The entire team should discuss and prioritize the backlog factoring in stakeholder input.

D.  

Only the agile team lead and team need to decide how to prioritize the project deliverables.