What should be taken into account when estimating Story point size?

Question

Options

• AComplexity
• BTeam size
• CNumber of days it will take
• DPriority

• A
  86% (48)
• B
  7% (4)
• C
  5% (3)
• D
  2% (1)

Explanation

Story points estimate the relative effort and complexity of a user story - not how long it takes or how many people work on it. Complexity (A) captures factors like uncertainty, technical difficulty, and interdependencies, which are exactly what story points are designed to measure.

Why the distractors are wrong:

• B (Team size) - Story points are team-agnostic; the same story has the same complexity regardless of how many people are on the team.
• C (Number of days) - Story points deliberately avoid time-based estimates; converting to hours or days defeats the purpose of relative sizing and introduces individual velocity bias.
• D (Priority) - Priority determines order of work, not size; a high-priority story can be trivially simple or enormously complex.

Memory tip: Think of story points like measuring how hard it is to climb a hill, not how long it takes you - complexity is the hill's steepness, not your walking speed or who's with you.

No community discussion yet for this question.