PMI Agile Certified Practitioner (ACP) Practice Exam

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the PMI Agile Certified Practitioner Exam with multiple choice questions and flashcards. Each question includes explanations to help you gear up for your test!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


Why is Affinity Estimation used in Agile practices?

  1. To create user stories

  2. To rapidly group user stories of similar size

  3. To determine the sprint length

  4. To evaluate team performance

The correct answer is: To rapidly group user stories of similar size

Affinity Estimation is a technique commonly used in Agile practices to rapidly group user stories or tasks based on their relative size or complexity. This method involves team members discussing and sorting items into categories that reflect their estimations, typically using a visual representation. The primary benefit of this approach is that it allows the team to quickly reach a consensus on the effort involved in delivering various user stories without needing extensive discussions or detailed calculations. By grouping user stories of similar size, the team can better understand the scope of the work ahead, prioritize tasks effectively, and create a shared understanding of project requirements. This enhances planning and facilitates smoother sprint execution, as team members can select user stories to work on that align with their capacity and the sprint goals. In contrast, other options do not accurately reflect the purpose of Affinity Estimation. While creating user stories is a crucial activity in Agile, Affinity Estimation specifically focuses on sizing them rather than their creation. The determination of sprint length is generally based on team velocity and capacity rather than estimation techniques, and evaluating team performance typically involves metrics or retrospective discussions rather than a method for sizing tasks.