PMI-200 PMI Agile Certified Practitioner (PMI-ACP)® Questions and Answers

it is impossible to compare two separate teams on points alone.

Team B’s points will match Team A if Team B gets more senior engineers.

Team B must have help self-organizing so their points match Team A.

Team B’s points will increase if the Product Owner becomes more involved.

Story card

Burndown chart

Retrospective

Storyboard

Project Retrospective

Steering Committee

Release Planning

Sprint Planning

Burn up chart

Product Backlog

Affinity estimate

Cost Benefit Analysis (CBA)

Algorithmic

Computational

Triangulating

Rules of Thumb

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

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

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

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

Agree that documentation should be avoided, since it slows the progress of the team.

Explain that interactions are valued over documentation, but documentation is not forbidden.

Ask the manager if the technical processes mandate that designs be documented.

Ask the Product Owner if it is acceptable for the resources to spend time on documentation.

What is preventing you from completing your work effectively?

What is yourcurrent performance velocity?

Are you on track to complete assigned story points?

How many story pointswill you complete this sprint?

Cost containment

High volume of communication

Shared knowledge

Culture of collaboration

Technique to determine if the software is easy for customer use.

Tool for a customer to verify the business requirements.

Technique to determine if a customer will use a software feature.

Test for determining if a customer will purchase the product.

Work in Process (WIP) and bugs.

Delays and building what is not needed.

Defects and features with low value stream values.

Poor requirements and changing scope.

Lines of code.

Function points

Story points.

Use-case points.

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

Velocity measurement

Relative prioritization

Planning Poker

Release planning

Retrospective.

Stakeholder review.

Scope verification.

Iteration planning.

set priorities and identify product features.

interview new team members for fit.

approve development plans and tasks.

set sprint and release schedules.

Value is delivered more quickly, as software can be released after every iteration.

More customers can be handled simultaneously, as each regularly receives a delivery.

Fewer bugs are introduced, as code is delivered to users more frequently.

Costs are reduced, as less verification is required to regression test each iteration.

Whatever they choose.

Individual projects.

The same set of multiple projects,

The same project.