| name | sprint-progress-report |
| description | Generate a comprehensive sprint progress report from Jira with velocity metrics, burndown analysis, blocker identification, and team workload distribution. Use when preparing sprint reviews, standups, or tracking sprint health mid-cycle. |
Sprint Progress Report
Query Jira to build a detailed sprint progress report including velocity, burndown, completion rates, and blockers.
Instructions
Phase 1: Sprint Data Collection (Jira Agent)
- Identify the current sprint:
- Get the active sprint from the team's Jira board
- Collect sprint name, start date, end date, and goal
- Fetch all sprint issues:
- Stories, tasks, bugs, and subtasks in the sprint
- For each: key, summary, status, assignee, story points, priority, labels
- Fetch sprint history (for velocity):
- Last 3-5 completed sprints
- Committed vs. completed story points per sprint
Phase 2: Metrics Calculation
- Burndown Metrics:
- Total committed story points
- Completed story points
- Remaining story points
- Percentage complete
- Days remaining in sprint
- Projected completion (on track / at risk / behind)
- Velocity:
- Average velocity over last 3-5 sprints
- Current sprint pace vs. average
- Velocity trend (increasing, stable, decreasing)
- Issue Distribution:
- By status (To Do, In Progress, In Review, Done)
- By type (Story, Bug, Task)
- By assignee (workload balance)
- By priority (Critical, High, Medium, Low)
Phase 3: Blocker & Risk Analysis
- Identify blockers:
- Issues with
blocked status or blocker label
- Issues with no activity for >2 days while In Progress
- Issues with unresolved dependencies
- Identify risks:
- High-priority items still in To Do with <3 days remaining
- Unassigned items
- Items added mid-sprint (scope creep)
- Items removed from sprint (scope reduction)
Output Format
## Sprint Progress Report
**Sprint**: Sprint 24 - "Platform Reliability"
**Period**: Feb 3 - Feb 14, 2026 | **Days Remaining**: 5
**Sprint Goal**: Improve platform monitoring and reduce incident response time
### Summary
| Metric | Value |
|--------|-------|
| Committed | 34 story points (15 issues) |
| Completed | 21 story points (9 issues) |
| Remaining | 13 story points (6 issues) |
| Completion | 62% |
| Projection | On Track (avg velocity: 32 pts) |
### Burndown Status
- **Ideal pace**: 24.3 pts should be done by now
- **Actual pace**: 21 pts completed
- **Gap**: 3.3 pts behind ideal - recoverable with current velocity
### Issue Breakdown
| Status | Count | Story Points |
|--------|-------|-------------|
| Done | 9 | 21 |
| In Review | 2 | 5 |
| In Progress | 3 | 5 |
| To Do | 1 | 3 |
### Velocity Trend (Last 5 Sprints)
| Sprint | Committed | Completed | Rate |
|--------|-----------|-----------|------|
| Sprint 23 | 30 | 28 | 93% |
| Sprint 22 | 35 | 32 | 91% |
| Sprint 21 | 28 | 30 | 107% |
| **Average** | **31** | **30** | **97%** |
### Blockers & Risks
1. **BLOCKER**: PLAT-456 "Fix flaky integration test" - blocked by environment issue, 3 days stale
2. **RISK**: PLAT-489 "Add PagerDuty agent pagination" (5 pts) - still in To Do with 5 days left
### Team Workload
| Assignee | Done | In Progress | Remaining |
|----------|------|-------------|-----------|
| @dev1 | 8 pts | 3 pts | 2 pts |
| @dev2 | 8 pts | 2 pts | 0 pts |
| @dev3 | 5 pts | 0 pts | 3 pts |
| Unassigned | 0 | 0 | 8 pts |
Examples
- "Generate a sprint progress report for the current sprint"
- "Show me sprint velocity and burndown"
- "Are we on track to complete this sprint?"
- "What are the blockers in the current sprint?"
- "Show team workload distribution for this sprint"
Guidelines
- Always calculate projected completion based on historical velocity, not optimistic estimates
- Flag sprints as "at risk" if completion rate is below 80% at the midpoint
- Highlight scope changes (issues added or removed mid-sprint) separately
- If story points are not used, fall back to issue count
- Keep the report scannable - lead with the summary, details below
- Include the sprint goal prominently so progress can be evaluated against intent
