Velocity Tracking
SyncUp records the outcome of every sprint that closes while it’s installed. These records power velocity views in two places.
Velocity Trend (Product Owner brief)
Section titled “Velocity Trend (Product Owner brief)”The Daily Brief for Product Owners includes a 💰 Velocity Trend card. It shows the last 5 closed sprints in a table:
| Column | What it means |
|---|---|
| Sprint | Sprint name from Jira |
| Completed | Items delivered (Done category at sprint close) |
| Planned | Initial item count (from the earliest snapshot of that sprint) |
| Health | Final Sprint Health score (0–100) |
Above the table, a direction badge summarizes whether velocity is ▲ Trending up, ▼ Trending down, or → Stable, computed from the last two sprints’ completed counts.
Sprint Comparison (Reports tab)
Section titled “Sprint Comparison (Reports tab)”When you have 2+ closed sprints, the Reports tab adds a 📊 Sprint Comparison table under the list of reports. It shows the same last 5 sprints with delivery and health side-by-side — useful for spotting trends across sprints rather than within one.
To drill into any individual sprint’s full report, click its row. See Sprint Autopsy for everything in the report.
How sprint records are created
Section titled “How sprint records are created”A record is written to Forge SQL the moment a Jira sprint moves to Closed (via the avi:jira-software:closed:sprint event). The record uses issue counts — not story points — because Jira’s story-point field is project-specific and not always present.
What’s stored per sprint:
- Sprint name and Jira sprint ID
- Start and end dates
- Planned items (count at first snapshot)
- Completed items (Done category at close)
- Average cycle time
- Final health score
- Scope change percentage
- The full autopsy
reportDataJSON
Reading the numbers
Section titled “Reading the numbers”| Pattern | What it usually means |
|---|---|
| Completed ≈ Planned, stable across sprints | Predictable team. Velocity is a good forecasting input. |
| Planned ≫ Completed, repeatedly | Sprint planning is over-committing. Pull scope back at planning. |
| High variance sprint-to-sprint | Scope is shifting mid-sprint (check Scope Change in each autopsy) or estimates are noisy. |
| Trending up | Team gelling, or scope shrinking. |
| Trending down | Possible burnout, team changes, or growing technical debt. |
When history starts
Section titled “When history starts”Velocity data only exists for sprints that closed while SyncUp was installed. Sprints closed before installation are not retroactively reconstructed.
- Sprint Autopsy — the per-sprint report behind these numbers.
- Sprint Health — the live mid-sprint counterpart.