Story Points

Story points are related to time, but they are not the same as time.

A story point is a relative estimate of the size of a user story. It considers:

FactorMeaning
EffortHow much work may be required
ComplexityHow difficult the work is
UncertaintyHow unclear or risky the work is
DependenciesWhether the story depends on other people, teams, systems, or information

Your slides explain that story points are used for relative sizing and consider complexity, effort, uncertainty, and dependencies, while hours are better used for task breakdown inside a sprint.

Simple example

StoryStory pointsPossible meaning
Add a button label change1 pointVery small, low risk
Create login page3 pointsModerate work
Build password reset with email verification5 pointsMore effort and testing
Build recommendation engine13 pointsLarge, complex, uncertain

A 5-point story does not always mean 5 hours. It means the team believes it is roughly bigger than a 3-point story and smaller than an 8-point story.

How story points connect to time

Story points become useful over multiple sprints through velocity.

Velocity = average story points completed per sprint.

For example:

SprintCompleted story points
Sprint 122
Sprint 226
Sprint 324

Average velocity = about 24 story points per sprint.

So if the remaining backlog has 96 story points, the team may estimate:

96 ÷ 24 = 4 sprints

So story points help forecast time at the sprint/release level, not at the individual-hour level.

Explanation

You can say:

Story points are not hours. Story points are a relative measure of story size. After a team completes a few sprints, we can use their average velocity to estimate how many sprints are needed to finish the backlog.

Good classroom warning

Avoid saying:

1 story point = 1 hour

That is usually not correct.

Better:

For this team, based on past performance, 20 story points may usually fit into a 2-week sprint.

So the relationship is:

Story points → help calculate velocity → velocity helps forecast time.

Leave a Reply