PK0-005 Tools and Documentation Practice Question

A project team is using planning poker to estimate user stories. What is the purpose of this technique?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

To reach a consensus on story point estimates

Planning poker is a consensus-based estimation technique that uses story points to achieve team agreement on effort.

Answer analysis

For each option: why learners choose it and why it is or isn't the right answer here.

✗
To define the product backlog
Why it's wrong here
Planning poker estimates effort for stories already in the backlog; it does not define or create the backlog itself. Backlog definition occurs during product backlog refinement or grooming sessions, where items are written, split and ordered before estimation.
✗
To identify risks in user stories
Why it's wrong here
Risk identification is separate from estimation.
✓
To reach a consensus on story point estimates
Why this is correct
Planning poker has each team member privately select a card representing their story point estimate, then discuss discrepancies until convergence. This iterative reveal-and-discuss cycle produces a shared consensus estimate, directly satisfying the stem's stated purpose rather than merely averaging individual guesses.
✗
To assign tasks to team members
Why it's wrong here
Planning poker yields consensus-based effort estimates, not task assignments. Assigning tasks to team members happens during sprint planning's task breakdown or daily stand-ups; planning poker would be correct when the team needs to size user stories in story points.

Go deeper