PMI-200 Practice Exam Questions and Answers

A.  

Incremental design and architecture.

B.  

Pair programming.

C.  

Manual regression testing.

D.  

Test-Driven Development (TDD).

A.  

Funds set aside to contain the risk.

B.  

Probability a risk will occur.

C.  

Amount of money the risk will cost if it occurs.

D.  

Amount of damage to the project if the risk occurs.

A.  

Can be used by management for communicating specific corrective direction.

B.  

Are easy to use, reflect the team's progress, and show the team what to do next.

C.  

Are helpful while the team is forming but are less important for more experienced teams.

D.  

Should be kept to a minimum to avoid distracting the team from high-value activities.

A.  

Denoting development sequence

B.  

Estimating development hours

C.  

Indicating priority of a story

D.  

Estimating points of a story

A.  

Release vision, assumptions, action items, and iteration goals

B.  

Prioritized Product Backlog, risks, action items, and release goals

C.  

Estimated iteration velocities, risks, action items, and Release Backlog

D.  

Risks, action items, dependencies, and Release Backlog

A.  

Release plan

B.  

Product roadmap

C.  

Iteration plan

D.  

Product Backlog

A.  

The best customer feedback comes near the end of the project when there is working software to review.

B.  

Project status can be gauged by frequently reviewing completed milestones as reflected in the plan.

C.  

Working solutions are the most accurate way of seeing the progress of the effort.

D.  

Unique skill sets are harnessed when team members play different roles on a project.

A.  

Attempt to resolve the problem directly and immediately during a Daily Scrum meeting.

B.  

Schedule a meeting with them after a Daily Scrum meeting to explore and resolve the issue.

C.  

Ignore the friction because a self-organizing team must sort out team conflict issues.

D.  

Ask for new resources to replace them before the friction undermines the team’s productivity.

A.  

Team members assign estimates by averaging Planning Poker cards.

B.  

The most senior team member prepare the estimates.

C.  

Two or three senior team members estimate and take the average of their times.

D.  

The team work together to agree on estimates in a group setting.

A.  

Story card

B.  

Burndown chart

C.  

Retrospective

D.  

Storyboard

A.  

Work in Process (WIP) and bugs.

B.  

Delays and building what is not needed.

C.  

Defects and features with low value stream values.

D.  

Poor requirements and changing scope.

A.  

For the better.

B.  

Driven by process improvement.

C.  

Driven by teams.

D.  

Forsmallgroups.

A.  

ScrumMaster.

B.  

Product Owner.

C.  

Project Sponsor.

D.  

Scrum team.

A.  

set priorities and identify product features.

B.  

interview new team members for fit.

C.  

approve development plans and tasks.

D.  

set sprint and release schedules.

A.  

Yes, the ScrumMaster should get status updates and distribute new tasks to the team.

B.  

Yes, the ScrumMaster should hold Scrums daily and keep the time to 15 minutes or less.

C.  

No, the ScrumMaster should act in the role of facilitator to foster team self-organization.

D.  

No, the ScrumMaster should allow the Scrum to run as long as is required by the team.

A.  

Individual tasks in the same work area.

B.  

The same task through pair programming.

C.  

The same group of tasks individually.

D.  

Different tasks on the same project.

A.  

Ready to ship when all features are complete.

B.  

Delivered for testing at the end of each day.

C.  

Technologically ready to deploy at any time.

D.  

Deployed after final business approvals.

A.  

Discuss among the team their expectations of how many story points they can address.

B.  

Use a Kanban workflow to identify steps and calculate velocity.

C.  

Use velocity of past iterations or make a calculated guess.

D.  

Discuss with the customer their expectation for the velocity of producing the product.

A.  

Status reports.

B.  

Information radiators.

C.  

Portfolio presentations.

D.  

Project data packages.

A.  

a written description, the story points estimate, and the planned release.

B.  

conversations about the story, a written description, and success criteria about the story.

C.  

the story points estimate, conversations about the story, and an agreed priority.

D.  

tests to determine when the story is done, a written description, and the planned release.

A.  

Release planning

B.  

Sprint planning

C.  

Sprint Retrospective

D.  

Daily Scrum