During backlog refinement, an agile team must assign story points to a brand-new user story. Which approach best reflects how teams typically arrive at the story-point value?
They multiply the story's expected business value by its cost of delay to obtain a point score.
They total the ideal engineering hours and round to the nearest Fibonacci number.
They compare the new story's effort, complexity, and risk to a previously completed reference story whose point value is already known.
They assign one point for every individual technical task required to implement the story.
Story points are a relative measure. Teams first agree on a reference story they have already completed (or another anchor in their story-point matrix). When a new backlog item appears, they discuss its effort, complexity, and risk and then choose the point value that most closely matches the reference story. This keeps estimates consistent over time and avoids equating points with hours. Converting hours, basing points on business-value math, or simply counting tasks ignores the relative-comparison principle.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are story points and why are they used in Agile?
Open an interactive chat with Bash
How do teams determine the size of a known task for estimation?
Open an interactive chat with Bash
How do story points improve predictability in Agile planning?
Open an interactive chat with Bash
Project Management Professional
Agile
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
Project Management Package Join Premium for Full Access