Committed
Completed
Avg Velocity
-
pts / sprint
Last 3 Sprints
-
pts avg
Trend
-
vs overall avg
Avg Committed
-
pts / sprint
Completion Rate
-
completed ÷ committed
| Sprint Name | Committed SP | Completed SP | Notes |
|---|
Sprint length:
- working days
Average Velocity
Your team's expected story points per sprint
Section 1 history suggests - pts
pts / sprint
🗓 Org Holiday Library (0 saved)
▾
Add team members below to calculate capacity.
| Name | Role | Focus % | PTO Days | Co. Hols | Avail Days | SP / Day | Total SP |
|---|
Team Total Capacity
0 SP
%
ceremonies, admin, unplanned work
Effective:
0 SP
Enter Average Velocity in Section 2 to generate a recommendation.
SP
Recommended Commitment
- SP
⚠ AMBER
Add capacity and velocity to generate a recommendation.
Member Breakdown
| Member | Role | Avail Days | SP Capacity | % of Total |
|---|
Flow metrics work from one row per ticket (with created and completed dates). Import a Jira issue CSV export, or fetch issues straight from the Jira API. Nothing leaves your browser; your token is never saved.
📂
Drop a Jira issue CSV export here, or click to browse
One row per issue · needs Created & Completed (Status Category Changed) dates
Benchmark thresholds and annotations live in ⚙ Settings (top-right).
A fair, leave-aware rota for who leads each ceremony this sprint. It uses the active team's members and sprint dates. If someone is on leave, the next-fairest teammate covers automatically, and everyone's turn balances over time.