How do story points work in LocalPM?

Story points are an optional estimate of how much effort a story will take. LocalPM doesn't impose a scale; you decide what the numbers mean.

Adding or changing points

1. Open the story from the Backlog view (or create a new one with New Story).
2. Type a number in Story Points.
3. Select Create or Update.

Leave the field empty if you haven't estimated the story yet. Unestimated stories count as zero in the totals below.

Where points appear

• Story cards and rows: the Backlog shows a "pts" badge and board cards show the number.
• Dashboard: each project card shows completed points out of total points.
• Project Overview: Total Points and Points Done tiles.
• Epics: each epic shows its total points and points done.
• Sprints: each sprint totals the points of the stories assigned to it.
• Reports: the Velocity chart compares committed points (all points in the sprint) with completed points (points on stories marked Done) for each completed sprint.

A story's points only count as completed when its status is Done. Work that's In Review doesn't count yet.

Choosing a scale

Most teams use a Fibonacci-style sequence such as 1, 2, 3, 5, 8, 13, which makes it clear that bigger items carry more uncertainty. Whatever you choose, stay consistent, because velocity is only meaningful when a "5" means roughly the same thing every sprint.

Points and capacity

Team members in LocalPM have a separate capacity value. LocalPM doesn't convert between points and capacity for you, so treat them as two inputs to your sprint planning conversation. See How do I add team members and set capacity?

LocalPM doesn't include a burndown chart. For velocity, see What reports does LocalPM include?

Further reading: Why Story Points Matter and How to Estimate Them Consistently and Velocity Charts Explained: What They Do and Don't Tell You.