Sprint health pulse template
A ready-to-use template for mid-sprint health checks—confidence levels, blocker tracking, scope changes, and team morale with recommended frequency and routing.
A sprint health pulse gives managers a structured signal about how the sprint is progressing between planning and the retrospective. This template defines the questions, recommended schedule, routing configuration, and how to interpret results—so you can set it up once and start collecting actionable data immediately.
Template questions
Question 1: Confidence level
Type: Scale (1-5)
Prompt: “How confident are you that our sprint goal will be met?”
Scale labels: 1 = Not confident, 3 = Uncertain, 5 = Very confident
This is the single most valuable signal in the pulse. Track the team average over time—a declining average mid-sprint is the earliest indicator that something needs attention.
Question 2: Blockers
Type: Yes/No with conditional follow-up
Prompt: “Are you currently blocked on anything?”
Follow-up (if yes): “What is blocking you and who might help unblock it?”
The yes/no structure produces a clean blocker rate metric. The follow-up text captures enough context for a manager to act without scheduling a meeting.
Question 3: Scope changes
Type: Multiple choice
Prompt: “Has the scope of your work changed since sprint planning?”
Options: No change / Minor additions / Significant additions / Work was removed
Scope change data is crucial for diagnosing why sprints miss their goals. If the answer is consistently “significant additions,” the problem is not execution—it is planning discipline.
Question 4: Team morale
Type: Scale (1-5) or emoji
Prompt: “How are you feeling about the sprint so far?”
Scale labels: 1 = Struggling, 3 = Neutral, 5 = Great
Morale correlates with velocity more than most teams realize. A two-point drop in average morale over consecutive pulses is a leading indicator of delivery problems.
Question 5 (optional): One improvement
Type: Free text
Prompt: “What is one thing that would make this sprint go better?”
This open-ended question often surfaces actionable insights that the structured questions miss. Review these manually—they are where the team tells you what they actually need.
Recommended schedule
Frequency: Twice per sprint
Timing: Schedule the first pulse at the sprint midpoint (day 5 of a 10-day sprint) and the second at the 75% mark (day 7-8). This cadence catches problems early enough to course-correct while avoiding survey fatigue.
Day and time: Mid-morning on a weekday works best—team members have started their day but are not yet deep in focus work. Avoid Mondays (too early for meaningful reflection) and Fridays (low response rates).
Response window: Give the team 4-6 hours to respond. Send a single reminder halfway through the window if needed.
Routing and notification setup
Results destination: Post a summary to a team lead or manager channel after the response window closes. Do not post individual responses to public channels unless the team explicitly opts in.
Blocker escalation: If a blocker response includes a mention of another team or external dependency, consider routing it to the relevant owner automatically via a workflow trigger.
Trend alerts: Set up a workflow that flags when the team confidence average drops below 3.0 or the blocker rate exceeds 40%. These thresholds indicate a sprint at meaningful risk.
Reading the results
Healthy sprint signals
- Confidence average above 3.5
- Blocker rate below 20%
- No significant scope changes reported
- Morale stable or trending upward
At-risk sprint signals
- Confidence average between 2.5 and 3.5
- Blocker rate between 20% and 40%
- Multiple team members reporting scope additions
- Morale declining from the previous pulse
Sprint in trouble
- Confidence average below 2.5
- Blocker rate above 40%
- Significant scope changes combined with declining confidence
- Morale below 2.5 on average
When you see at-risk or trouble signals, act within 24 hours: address blockers, renegotiate scope with stakeholders, or have a quick team sync to reset priorities. The point of the pulse is to surface these signals early enough that intervention is still possible.
Customization tips
Rename questions to match your team’s vocabulary. If “sprint goal” is not a concept your team uses, substitute “milestone” or “planned deliverables.” Keep the structure—scale, yes/no, multiple choice—even if you change the wording. And resist the urge to add more questions: four or five keeps the pulse under two minutes, which is the threshold for consistent participation.
FAQ
- What does a sprint health pulse template measure?
- Confidence in meeting the sprint goal (1-5 scale), active blockers (yes/no with details), scope changes since planning, and team morale—giving managers a real-time health signal without waiting for the retro.
- How often should a sprint health pulse run?
- Twice per sprint is the recommended frequency—once at the midpoint and once at the 75% mark. This provides enough data to act on without causing survey fatigue.
- How should managers read the pulse results?
- Look for trends rather than individual answers. Dropping confidence scores, rising blocker counts, or declining morale across the team signal a sprint at risk. Stable or improving scores mean the sprint is on track.