Story points are only useful if a point means roughly the same amount of work every time. Most teams never check. If an 8 actually takes fifteen times as long as a 1, every velocity chart built on the raw numbers rewards splitting work into small tickets and hides the cost of big ones. These additions let you check, and correct for it.
Story Point Distribution (Velocity)
One row per estimate that closed work in the period (for example 1, 2, 3, 5, 8, 13), showing how many tasks closed at that size and their points. Beside each:
- Median time — how long tasks of that size really took, with the middle half of the range on hover.
- Cost / SP — hours per point relative to your cheapest estimate (1.00×). This is time, not money. A 13 at 2.40× means each of its points took 2.4 times as long as the cheapest size's.
- Suggested weight — the weight that would make every estimate cost the same time per point.
Time is measured over your Estimation baseline window, across every estimated task in the company, so a small filtered selection is not judged on its own handful of tasks.
The card's headline is weighted work: tasks × weight, beside the raw story points. Admins can set company weights from the card's weights icon, or click Apply suggested weights and save. Until weights are saved, each estimate simply counts its own points, so nothing changes until you choose to.
The settings gear chooses which clock the time is measured on (Active work by default; also Start of work, Lead time, Lifecycle or Custom) and the minimum number of timed tasks an estimate needs before we show its time (default 10). Below the minimum, the cell shows a dash, and hovering it tells you how many timed tasks it had and how many it needs, rather than showing a number from three tickets. Team-restricted readers never go below 10.
What to do with it: if your larger estimates cost far more per point than your small ones, either re-weight, or retrain the scale in your next planning session. And bear in mind that the clock and the statuses your View counts as work change the answer. Compare like with like.
Elapsed Time per SP and Lifecycle Time per SP (Time Tracking)
Two new cards: the median clock hours per story point across delivered tasks. Lower is better. Each has its own gear to pick its clock, and its title follows that clock, so the card always says what it measured. They default to Start of work ("Elapsed") and Lifecycle. They replace the SP / Active Work Hour card that used to sit on Velocity (see metric changes, September–October 2026).
Delivery Pace (Time Tracking)
One question: is a story point getting faster or slower to deliver than it used to? Delivery Pace compares hours per story point in the selected period with your trailing history (90 days by default):
- Positive means faster: at +15% your history needed 15% more hours per point than the current period (roughly 13% less time per point now). Negative means slower.
- The subtitle shows the two figures it compared, current first, such as 120 vs 138 h/SP, so the percentage is never a black box.
- The clock is configurable, as above, and defaults to Start of work.
On the Dashboard, the per-person component of Team Performance is now Effort pace: the same comparison for one person against their own history, measured in active-work hours. Because it uses a different hours basis, the team's Delivery Pace is not the sum of its members' Effort pace.
Read this if you used the old card. The name Delivery Pace was previously used for a different metric, on a 100-means-on-pace scale. That card is gone, and Estimation Predictability has been redefined under this name. The metric-change note has the details.
Story Point Distribution, the time-per-SP cards and Delivery Pace are on every plan. Delivery Pace's contribution to the Organization Health score is on Business and Enterprise.