Under what circumstances would a team use Affinity Estimation Technique instead of Planning Poker?

Question

Options

• AIf more details are needed during Sprint Planning
• BIf there is a large number of stories to estimate
• CIf there is a small number of stories to estimate

• A
  3% (1)
• B
  94% (30)
• C
  3% (1)

Explanation

Affinity Estimation is designed for speed and scale - teams physically group user stories by relative size, making it ideal when there are many stories to estimate quickly (option B), such as during backlog refinement with dozens or hundreds of items. Option A is incorrect because needing more details during Sprint Planning points to a breakdown in requirements, not a reason to switch estimation techniques. Option C is the opposite of the right answer - Planning Poker is perfectly efficient for a small number of stories and is actually preferred then, since its discussion-driven process adds value when time isn't a constraint. Memory tip: Think of "Affinity" as "Affinity for abundance" - you reach for it when stories are too numerous for individual discussion, letting the team sort and cluster stories visually in a fraction of the time Planning Poker would take.

No community discussion yet for this question.