Scrum Master Playbook
Your complete guide to using SprintINSite for sprint analytics, team health monitoring, and data-driven retrospectives inside Jira Cloud.
What is SprintINSite?
SprintINSite is a Jira Cloud app that gives Scrum Masters real-time visibility into sprint health, team workload balance, predictive completion analytics, scope forensics, and cross-sprint performance trends — all without leaving Jira.
It lives directly inside your Jira project as a dedicated app page, so there’s no context-switching, no external dashboards, and no manual data exports. Every metric updates live from your board data.
Getting Started
Accessing SprintINSite
- Navigate to your Jira project in the left sidebar
- Click Apps in the project navigation bar (or look for SprintINSite INV in the top navigation tabs)
- The SprintINSite dashboard loads directly inside your project page
Selecting a Sprint
At the top of the dashboard you’ll see a Select Sprint bar with pill-shaped buttons for each sprint. Sprints are colour-coded:
| Colour | Meaning |
|---|---|
| Blue (ACTIVE) | The currently running sprint |
| Grey (CLOSED) | Completed sprints available for review |
Refreshing Data
Click the Refresh button in the top-right of the sprint header card to pull the latest data from Jira. Use this after making board changes mid-sprint.
The Six Tabs
SprintINSite organises its analytics into six tabs. Each tab serves a distinct purpose in your Scrum Master workflow.
1 Overview Tab
Purpose: Your sprint-at-a-glance command centre.
When to use it: Daily standups, mid-sprint check-ins, stakeholder updates.
Key Metrics
| Metric | What It Tells You | Healthy Range |
|---|---|---|
| Issues | Total issue count in the sprint | Varies by team |
| Total Points | Sum of story points committed | Compare to velocity |
| Done | Points completed and percentage | Should track toward 100% |
| Completion Probability | AI-predicted likelihood of finishing all work | 70%+ = on track |
| Workload Score | How evenly work is distributed (out of 100) | 80+ = balanced |
| Commitment Integrity | Whether scope has stayed stable since sprint start | 90%+ = disciplined |
| Current Velocity | Points completed per day in this sprint | Compare to historical |
| Days Remaining | Calendar days left in the sprint | Context for all other metrics |
Visual Elements
- Sprint Timeline — Horizontal bar showing elapsed vs. remaining time, plus the baseline lock date
- Work Status Distribution — Donut chart breaking down Done (green), In Progress (blue), and To Do (orange)
- Overall Sprint Completion — Progress bar showing percentage complete
- Alerts & Recommendations — Actionable warnings such as unassigned work, concentration risk, and scope changes
Scrum Master Actions
- Completion probability below 60%: Facilitate a mid-sprint scope discussion. Use the alerts section to identify items to descope.
- Workload score below 70: Check the Workload tab for rebalancing opportunities.
- Commitment integrity below 90%: Investigate scope changes in the Scope Forensics tab.
2 Prediction Tab
Purpose: AI-powered sprint outcome forecasting.
When to use it: Sprint planning validation, mid-sprint risk assessment, stakeholder confidence reporting.
Key Metrics
| Metric | What It Tells You |
|---|---|
| Completion Probability | Percentage likelihood all committed work finishes by sprint end |
| Current Progress | Actual percentage of points completed right now |
Visual Elements
- Sprint Timeline — Shows Day X of Y with days remaining
- Work Distribution — Horizontal stacked bars showing Done, In Progress, and To Do
- Velocity Analysis — Current velocity vs. required velocity to complete all remaining work
The prediction engine compares your current burn rate against the remaining work and time. If current velocity exceeds required velocity, you’re ahead of pace.
Scrum Master Actions
- Probability > 80%: Team is on track. Consider pulling in stretch goals.
- Probability 50–80%: Monitor daily. Identify blockers in standup.
- Probability < 50%: Escalate. Facilitate scope negotiation with the Product Owner immediately.
3 Workload Tab
Purpose: Team capacity balance and workload equity analysis.
When to use it: Sprint planning (validate load distribution), mid-sprint (catch imbalances early), retrospectives (discuss fairness).
Key Metrics
| Metric | What It Tells You |
|---|---|
| Balance Score (out of 100) | How evenly work is distributed across the team. 100 = perfectly even. |
Visual Elements
- Workload Distribution Pie Chart — Each team member’s share of total sprint workload
- Detailed Breakdown Table — Team Member, Share (%), Distribution bar, Deviation from ideal, Status
- Capacity Planning Cards — Team Size, Ideal Load, Current Load
Scrum Master Actions
- Balance Score < 70: Review who is overloaded and who has capacity. Facilitate redistribution.
- One person owns > 50%: Flag single-point-of-failure risk. Consider pair programming or task splitting.
- Current Load > Ideal Load × 1.3: Team is over-committed. Discuss descoping with the PO.
4 Scope Forensics Tab
Purpose: Track every scope change since the sprint started.
When to use it: When commitment integrity drops, during retrospectives, when stakeholders question velocity.
Key Metrics
| Metric | What It Tells You |
|---|---|
| Commitment Integrity | Percentage of original scope that remains unchanged |
| Net Scope Change | Total points added minus points removed (positive = scope creep) |
Visual Elements
- Scope Changes Chart — Horizontal bar chart showing points added vs. removed with cumulative timeline
- Changed Issues Table — Every issue added or removed, with Issue Key, Points, Assignee, Change type
Scrum Master Actions
- Net scope change is positive: Scope creep is occurring. Discuss with PO whether additions are justified.
- Issues added without points: Flag estimation gaps — unpointed work distorts velocity.
- In retrospectives: Show the scope change chart. Ask: “Were these changes planned?”
5 Team Tab
Purpose: Individual contributor breakdown — who is doing what and how much.
When to use it: Capacity planning, 1:1 preparation, identifying blocked team members.
Team Member Table
| Column | What It Shows |
|---|---|
| Team Member | Name and avatar |
| Points | Story points assigned |
| Issues | Number of issues assigned |
| Done | Fraction completed (e.g., 8/13 = 62%) |
| Progress | Visual bar: Done vs In Progress vs To Do |
| Status | Whether the member is on track |
| Scope | Whether their scope has changed |
Scrum Master Actions
- “Unassigned” with significant points: Assign work or discuss ownership in standup.
- Low Done % relative to others: Check for blockers privately before standup.
- Scope column shows changes: Cross-reference with Scope Forensics.
6 Compare Tab
Purpose: Cross-sprint trend analysis for continuous improvement.
When to use it: Retrospectives, quarterly reviews, maturity assessments, stakeholder reporting.
How to Use It
- In the Select Sprints row, click the sprint pills you want to compare (up to 6 recommended)
- Click the blue Compare X Sprints button
- The comparison dashboard loads below
Key Metrics
| Metric | What It Shows |
|---|---|
| Average Velocity | Mean pts/day across selected sprints |
| Average Completion | Mean completion rate across sprints |
| Average Team Size | Mean number of contributors |
Scrum Master Actions
- Velocity trending down: Investigate scope creep, team changes, or technical debt.
- Completion rates volatile: Team may be struggling with estimation. Run a pointing calibration exercise.
- Participation dropping: Have a private conversation — they may be blocked or overallocated.
Sprint Lifecycle Workflows
Sprint Planning
- Open the Overview tab for the previous sprint to review final metrics
- Switch to Compare and select the last 3–5 sprints to establish velocity trends
- Use Average Velocity to set a realistic commitment for the new sprint
- After populating the backlog, check Workload to validate load balance
- Review Prediction — if probability is below 70% before the sprint starts, you’ve likely over-committed
Daily Standup
- Open the Overview tab for the active sprint
- Check the Sprint Timeline — are you on pace?
- Review Completion Probability — has it changed since yesterday?
- Note any Alerts & Recommendations
- If someone seems blocked, switch to the Team tab
Mid-Sprint Health Check
- Overview: Check completion probability and workload score
- Prediction: Compare current vs. required velocity
- Scope Forensics: Has scope changed since sprint start?
- Workload: Is work still balanced?
- If problems detected, facilitate a mid-sprint re-planning session
Sprint Retrospective
- Overview: Review final sprint metrics
- Scope Forensics: Walk through every scope change with the team
- Compare: Show trends across the last 3–5 sprints
- Team: Review contribution distribution (focus on systemic issues, not blame)
- Document insights and carry action items into the next sprint
Stakeholder Reporting
- Overview: Screenshot the top metrics cards for a quick status update
- Compare: Use Velocity and Completion Trend charts to show progress over time
- Prediction: Share completion probability as a confidence indicator
Metrics Glossary
| Metric | Definition | Formula / Source |
|---|---|---|
| Completion Probability | AI-predicted likelihood of completing all committed work | Based on current velocity, remaining points, and days left |
| Workload Score | Evenness of work distribution (0–100) | Standard deviation normalised to 100 |
| Commitment Integrity | Percentage of original scope unchanged | (Original − |Changes|) / Original × 100 |
| Current Velocity | Rate of point completion | Done points / Elapsed days |
| Required Velocity | Rate needed to finish on time | Remaining points / Remaining days |
| Balance Score | Workload evenness across team | Inverse of std deviation, scaled to 100 |
| Net Scope Change | Total scope movement since sprint start | Points added − Points removed |
| Completion Rate | Final percentage done | Done points / Total committed × 100 |
Tips & Best Practices
Do
- Check SprintINSite daily — even a 30-second glance at Overview catches problems early
- Use Compare in every retro — data-driven retrospectives beat opinion-based ones
- Share Prediction data with the PO — if probability drops below 60%, descoping must happen immediately
- Monitor Commitment Integrity — use Scope Forensics for honest scope creep conversations
- Use Workload Balance proactively — check the balance score at planning time, not when burnout hits
Don’t
- Don’t use Team metrics to blame individuals — the Team tab is for systemic issues, not performance reviews
- Don’t ignore the Alerts section — every alert is data-based. Take them seriously.
- Don’t compare velocity across different teams — velocity is team-internal. Use it for trends within a team only.
- Don’t skip the baseline lock — late additions after baseline distort all commitment metrics
Troubleshooting
| Issue | Solution |
|---|---|
| Data looks stale | Click the Refresh button in the sprint header card |
| Sprint not appearing | Ensure the sprint exists on your Jira board and has at least one issue |
| Metrics show 0 | Check that issues have story point estimates assigned |
| Team members missing | Verify that issues are assigned to team members in Jira |
| Completion probability seems off | Early in a sprint with few completed items, the prediction will be pessimistic |
Quick Reference Card
| I want to… | Go to… |
|---|---|
| Check if we’ll finish the sprint on time | Prediction tab → Completion Probability |
| See if work is evenly distributed | Workload tab → Balance Score |
| Investigate scope creep | Scope Forensics tab → Scope Changes chart |
| Prepare for a retrospective | Compare tab → Select last 3–5 sprints |
| Check a specific person’s progress | Team tab → Team Member table |
| Get a quick sprint status | Overview tab → Top metrics cards |
| Show stakeholders our velocity trend | Compare tab → Velocity chart |
SprintINSite v3.0.0 — Sprint Analytics for Jira Cloud
Built by Agility Ops Business Pty Ltd