User Guide
How to: Monitor Sprint Health
A step-by-step guide for engineering managers and Scrum masters to use Pulse AI for daily sprint monitoring.
What Pulse AI Tracks for Sprints
Navigate to Sprints & Delivery Overview for a full view of all active Scrum boards.
| Metric | What It Means |
|---|---|
| Active Sprints | All currently running sprints across the org |
| At Risk | Sprints at 115–149% utilisation - scope reduction recommended |
| Avg Carryover Rate | % of incomplete issues carried from the previous sprint. > 20% = chronic overcommitment |
| Active Blockers | Unresolved blocker-priority issues across all sprints |
Step 1: Check Utilisation on the Sprint View
- Navigate to Sprint & Delivery → Sprints & Delivery
- Look at the At Risk summary card - any number > 0 needs attention
- Click into the sprint table to see per-sprint utilisation badges
Risk badges:
| Badge | Utilisation | Action |
|---|---|---|
| On Track | < 100% | No action needed |
| Tight | 100–114% | Monitor daily, defer low-priority items |
| At Risk | 115–149% | Reduce scope, review blockers |
| Overcommitted | ≥ 150% | Immediate scope reduction required |
See Sprint Risk Thresholds → for the full reference.
Step 2: Check the Carryover Rate
The Avg Carryover Rate card shows the percentage of incomplete issues carried from the previous sprint.
- < 10%: Healthy - team is planning well
- 10–20%: Monitor - may indicate estimation drift
- > 20%: Act - review sprint planning process and story sizing
Ask the Pulse AI Assistant: "What is the average carryover rate across all boards over the last 3 sprints?"
Step 3: Check Active Blockers
High blocker counts depress the Sprint & Delivery Pulse Score.
- Note the Active Blockers card count
- Ask the Pulse AI Assistant: "Which issues in the current sprint are blocked and by what?"
- Escalate or resolve blockers before they spill into the next sprint
Step 4: Use the Boards Sub-View
- Toggle to the Boards sub-tab (top of the Sprint & Delivery section)
- Review board name, associated project, sprint count, and average velocity
- Low velocity boards may indicate under-resourced teams or poor sprint hygiene
Step 5: Ask the Pulse AI Assistant
Use these prompts on the Sprint & Delivery section:
- "Which stories in this sprint are at risk of not completing?"
- "What is the average carryover rate across all boards over the last 3 sprints?"
- "Show me the top 5 stories to defer from the overcommitted sprint."
- "Generate a JQL filter for all overdue items in the current sprint."
See AI Prompt Playbook → for more prompts.
Step 6: Re-scan Before Standups
- Go to Settings → Scan Schedule → Run Now before your daily standup
- This ensures sprint data reflects the latest Jira state
- After the scan, the Sprint Pulse Score and all cards will reflect current data