Story Points Completed Per Week Report
Last updated: October 27, 2026
Story Points Completed Per Week (shown in Span as Estimate Completed / Week) is the average number of story points one person completes in a week, adjusted for time off.
Why it matters
Raw point totals change with the length of the period, team size, and how much vacation people took. The per-week rate removes those effects, so you can compare Q4 with Q2, a 3-person team with an 8-person team, or a high-vacation summer with the rest of the year. It answers: what is our steady weekly pace when people are available to work?
Total Story Points Completed | Story Points Completed Per Week |
|---|---|
Absolute volume | Rate of delivery per person |
Changes with period length and absences | Adjusts for time off and period length |
Good for sprint outcomes and "what got done" | Better for trends and comparing periods or teams |
How it works
Story Points Per Week = (Total Story Points Completed ÷ Active Days) × 7Total Story Points Completed sums the latest estimate on every issue whose current status is Done, placed on its completion date. Issues without an estimate add nothing.
Active Days counts every calendar day, weekends included, that each person in scope was employed and not out of office, summed across people. Vacation, sick leave, parental leave, and other out-of-office days drop out.
× 7 turns the daily rate into a weekly rate. Because weekends count as active days, multiplying by 7 gives the same result as a 5-day week for a team that never works weekends.
Span credits each issue to its most recent assignee who maps to a person in Span. The value shows with one decimal place, for example 12.4 points per person per week.
Setup
Connect Jira or Linear. For Jira, Span reads the story point field set on the integration, or the field it detected as story points. For Linear, it reads the issue estimate.
Make sure issues carry story points consistently.
Connect a calendar (Google or Microsoft) or an HRIS for out-of-office days. Choose the source in Settings → Org Calendar → Out of Office Days Source.
Set up team membership in Span.
Find the metric in Insights → Productivity → Velocity → Issue lifecycle, on team and person pages, and in custom reports and dashboards. Search for "Estimate Completed / Week". Break it down by person, team, team hierarchy, job family, IC level, and issue type, over any date range or by week, month, or quarter.
Things to know
Worked example: a 5-person team completes 80 story points in a 2-week period (14 calendar days each). Person A was out 4 days, Person C 2 days, and Person E 6 days; B and D were out 0. Active days = 10 + 14 + 12 + 14 + 8 = 58. Rate = (80 ÷ 58) × 7 = 9.7 points per person per week. Across the team's 5 people, that's a pace of about 48 points a week when everyone is available.
Weekends count as active days: work done on weekends counts too. A company holiday counts as an active day unless people mark it out of office.
Per person, not per team: a team value divides the team's total points by its total active days, so people who were available more days weigh more.
Everyone in scope counts in the denominator, whether or not they write code or take tickets.
Latest estimate, not sprint-start estimate: re-estimating an issue after completion changes history. Sprint Tracking uses the estimate as of sprint end instead.
Sub-tasks and epics count: if your team puts points on both a story and its sub-tasks, both count. Jira's velocity chart ignores sub-task estimates, so Span can read higher.
Why it differs from Jira or Linear: your tracker shows raw totals per sprint. Span shows a per-person weekly rate across all done issues in the date range, adjusted for active days.
Scales differ across teams: Span doesn't normalize point scales. Compare each team's trend and consistency rather than absolute values when teams estimate differently.
Use with care in performance reviews: individual rates depend on work complexity, mentoring, and other factors. Treat it as one data point among many.
Inconsistent estimates: if your team doesn't estimate consistently, use Issues Completed / Week instead.
Getting started. Review 6 to 8 weeks of history to set a baseline, note the average and range, understand outliers, and look at trends over 4 or more weeks rather than single weeks. Consistent pace is usually more valuable than a rising one, and lower velocity during onboarding or tech-debt work can be the right trade-off.
Related articles
Total Story Points Completed Report
Estimate Completed / Week Report
How to read Span's "/ week" metrics
Need help?
Contact your Span account team or reach out to support@span.app.