A team estimates a Story using the Planning Poker technique. The team decides to allocate five Story points to the Story, because the Developers estimated two points and the Testers estimated three…

Question

Options

• APoints are assigned by the Scrum Master, not by the team.
• BPoints are assigned for the overall Story, not for parts of the Story.
• CPoints are never estimated, but always determined beforehand.
• DThe team forgets to ask the Product Owner about the estimate.

• B
  88% (21)
• C
  4% (1)
• D
  8% (2)

Explanation

In Planning Poker, story points represent the total effort for the entire story as a unified estimate agreed upon by the whole team - not a sum of individual role-based estimates. Splitting points by "Developers get 2, Testers get 3" misunderstands the technique; the team should discuss until reaching consensus on one number for the whole story.

Why the distractors are wrong:

• A is incorrect because the Scrum Master facilitates but does not assign story points - estimation is a Developer team responsibility.
• C is incorrect because story points are always estimated collaboratively, not predetermined.
• D is a red herring; the Product Owner clarifies scope and acceptance criteria but does not participate in the effort estimate itself.

Memory tip: Think of a story point like a price tag on a complete meal - you don't separately price the chef's labor, the dishwasher's time, and the server's time and add them up. You price the meal as one thing. Story points = one estimate for the whole story, not a sum of parts.

No community discussion yet for this question.