Skip to content
PMPCAPM

Story Points

Story points are a unit of measure for expressing the overall effort, complexity, and uncertainty involved in completing a Product Backlog item, used for relative estimation rather than measuring time.

Share:

Explanation

Story points represent relative sizing. Rather than estimating how many hours a task will take, the team compares items against each other to determine relative complexity. A story estimated at 5 points is roughly two-and-a-half times the effort of a 2-point story. Common scales include the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21) and T-shirt sizes (XS, S, M, L, XL).

The value of story points lies in their abstraction. Different team members may work at different speeds, but they generally agree on relative complexity. Over time, a team's velocity (the number of story points completed per sprint) becomes a reliable predictor of how much work the team can take on in future sprints.

Story points are estimated by the Developers, not by the Product Owner or management. Techniques like Planning Poker are commonly used for collaborative estimation. The key is that the team reaches consensus on relative size.

Key Points

  • Measure relative effort, complexity, and uncertainty rather than time
  • Common scales: Fibonacci sequence or T-shirt sizes
  • Estimated by the Developers through collaborative techniques
  • Used to calculate team velocity and forecast future capacity

Exam Tip

Story points measure relative effort, not absolute time. If an exam question converts story points directly to hours, that approach is incorrect.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Part of

Agile & Hybrid

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.