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
```markdown
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) |
| ``` |
|
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
1---2name: sprint-progress-report-23description: 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.4---56# Sprint Progress Report78Query Jira to build a detailed sprint progress report including velocity, burndown, completion rates, and blockers.910## Instructions1112### Phase 1: Sprint Data Collection (Jira Agent)131. **Identify the current sprint**:14 - Get the active sprint from the team's Jira board15 - Collect sprint name, start date, end date, and goal162. **Fetch all sprint issues**:17 - Stories, tasks, bugs, and subtasks in the sprint18 - For each: key, summary, status, assignee, story points, priority, labels193. **Fetch sprint history** (for velocity):20 - Last 3-5 completed sprints21 - Committed vs. completed story points per sprint2223### Phase 2: Metrics Calculation241. **Burndown Metrics**:25 - Total committed story points26 - Completed story points27 - Remaining story points28 - Percentage complete29 - Days remaining in sprint30 - Projected completion (on track / at risk / behind)312. **Velocity**:32 - Average velocity over last 3-5 sprints33 - Current sprint pace vs. average34 - Velocity trend (increasing, stable, decreasing)353. **Issue Distribution**:36 - By status (To Do, In Progress, In Review, Done)37 - By type (Story, Bug, Task)38 - By assignee (workload balance)39 - By priority (Critical, High, Medium, Low)4041### Phase 3: Blocker & Risk Analysis421. **Identify blockers**:43 - Issues with \`blocked\` status or \`blocker\` label44 - Issues with no activity for >2 days while In Progress45 - Issues with unresolved dependencies462. **Identify risks**:47 - High-priority items still in To Do with <3 days remaining48 - Unassigned items49 - Items added mid-sprint (scope creep)50 - Items removed from sprint (scope reduction)5152## Output Format5354\`\`\`markdown55## Sprint Progress Report56**Sprint**: Sprint 24 - "Platform Reliability"57**Period**: Feb 3 - Feb 14, 2026 | **Days Remaining**: 558**Sprint Goal**: Improve platform monitoring and reduce incident response time5960### Summary61| Metric | Value |62|--------|-------|63| Committed | 34 story points (15 issues) |64| Completed | 21 story points (9 issues) |65| Remaining | 13 story points (6 issues) |66| Completion | 62% |67| Projection | On Track (avg velocity: 32 pts) |68\`\`\`6970## Examples7172- "Generate a sprint progress report for the current sprint"73- "Show me sprint velocity and burndown"74- "Are we on track to complete this sprint?"75- "What are the blockers in the current sprint?"76- "Show team workload distribution for this sprint"7778## Guidelines7980- Always calculate projected completion based on historical velocity, not optimistic estimates81- Flag sprints as "at risk" if completion rate is below 80% at the midpoint82- Highlight scope changes (issues added or removed mid-sprint) separately83- If story points are not used, fall back to issue count84- Keep the report scannable - lead with the summary, details below85- Include the sprint goal prominently so progress can be evaluated against intent
caipe-io