PMI PMI-200 PMI Agile Certified Practitioner (PMI-ACP)® Exam Practice Test

If the team is committing to an appropriate amount of work for the iteration.

How much work each team member is capable of completing during an iteration.

How much work teams that are similar in size are capable of completing during an iteration.

If the Product Owner is prioritizing work appropriately in preparation for iteration planning.

the business requirements are vague or inadequate for an iteration.

a technology is understood well and has been used for a while, but needs a problem to be debugged.

there is insufficient time to refactor, but there is a need to resolve a specific problem.

a specific technicalQUESTION NO:needs to be answered, stopping work on the spike as soon as it answers that question.

After coding the story, but before user acceptance testing begins

After writing the story, but before coding begins

At the start of Product Backlog prioritization planning

After estimating the Product Backlog, but before Sprint planning begins

team lacks domain knowledge.

business needs are prioritized over the system design.

developers do not understand the tasks related to the story.

team has no experience in estimating.

Release vision, assumptions, action items, and iteration goals

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

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

Risks, action items, dependencies, and Release Backlog

Fast-Flexible-Flow

Optimize the Whole

Deliver Early and Often

Eliminate Waste

Ask the team members to table the discussion until after the meeting is over.

If the item is really important, allow the discussion to expedite resolution of the issue.

Abruptly end the daily standup meeting and schedule another meeting to discuss the issue.

Ask the team how they would like to use the daily standup meeting for that day.

The ability to bypass the change-management process, inserting new requirements and changes directly into the team as they meet daily

The early and continuous delivery of valuable software, providing increased visibility and the opportunity for more frequent adjustments

Increased access to the project and less reliance on formal reports and status meetings to better understand the current work and the risks the team is accepting

The team’s flexibility to make changes mid-iteration as business needs or priorities change, increasing the ability of the team to meet project commitments

Agreeing on a due date.

Sharing information.

Agreeing on the design.

Pair programming.

procurement processes by requiring vendors to ship materials as needed.

project cost management by making incremental payments on contracts.

customer satisfaction by specifying project shipping dates in the contract.

project Return on Investment (ROI) by releasing individual features to market.

9

10

12

15

Regression

Pareto

Qualitative

Monte Carlo

shifting from a controlling mindset to a facilitating mindset

directing the work in a more incremental fashion

only assigning tasks for the nextiteration

giving up control and rotating management through the team

Identify and communicate upcoming milestones.

Display the level of effort and resources utilized.

Identify dependencies between sprints or iterations.

Display the remaining work across time.

Report progress of the work effort, what work will be done next, and review impediments to progress.

Prioritize the Product Backlog, generate development and testing estimates, and plan the next iteration.

Provide a demonstration of the features developed during the iteration, get feedback from users, and begin testing.

Identify what worked well, what did not work well, and what actions should be taken to improve the process.

Relative cost

Customer value

Development effort

Dependencies

prioritizes the work for each iteration.

directs the activities of the team.

provides leadership, guidance, and coaching.

manages the project scope and budget.

Maximizing the amount of work not done

Delivering early and continuously

Welcoming changing requirements

Deciding at the last responsible moment

A well-planned and well-documented process is documented for each of the iterations in the project.

Users including project team members participate in the planning process for the project plan.

End users participate and assist in the design process from the beginning of the project.

A high level brainstorming process is conducted for the project team and the project sponsor.

Split the stories into smaller ones to allow the customer to choose the pieces that they want.

Have the team provide guidance into where their priorities lie to the customer.

Provide additional technical details to give the customer insight into technical challenges.

Have the team rewrite the stories with additional details to clarify requirements.

Customer at the start of the iteration.

Customer as late as possible during the iteration.

Tester after the team has finished the coding.

Development team at the start of the iteration.