Scrum · 6–12 people · SaaS / Software · Assessed by: Scrum Master
This is a sample report. Yours will reflect your team's actual answers.
Basic Scrum events are in place, but event quality is inconsistent. The team's primary bottlenecks are WIP overload and retrospective follow-through.
5 dimensions in Team Playbook ($49)
Team members average 3–4 active items simultaneously. Per Little's Law, this is the primary driver of the team's 14-day average cycle time — 2× the Scrum benchmark for a 6-person team.
⚡ Add WIP limit of 6 to the In Progress column this sprint and swarm on blocked items before starting new ones.
Retrospective analysis shows the team uses Start/Stop/Continue every sprint. The same 3 themes (testing bottlenecks, unclear requirements, code review delays) have appeared in retros for 6 consecutive months — indicating action items aren't being tracked or completed.
⚡ Add 1 retro action item to the Sprint Backlog as an actual Sprint task with an owner this sprint. One item, executed, beats five items discussed.
30% of sprint stories enter planning without acceptance criteria. The team spend…
Engineering manager distributes task assignments at the start of each sprint, by…
Only 1–2 stakeholders attend Sprint Reviews, and feedback is non-specific ('look…
Coach's Toolkit — $99
Full roadmap with milestone owners
Team Playbook — $49: All 8 dimensions scored, event-by-event health analysis, WIP implementation guide, Definition of Done template, and 30-day coaching plan.
Team members average 3–4 active items simultaneously. Per Little's Law, this is the primary driver of the team's 14-day average cycle time — 2× the Scrum benchmark for a 6-person team.
⚡ Add WIP limit of 6 to the In Progress column this sprint and swarm on blocked items before starting new ones.
Retrospective analysis shows the team uses Start/Stop/Continue every sprint. The same 3 themes (testing bottlenecks, unclear requirements, code review delays) have appeared in retros for 6 consecutive months — indicating action items aren't being tracked or completed.
⚡ Add 1 retro action item to the Sprint Backlog as an actual Sprint task with an owner this sprint. One item, executed, beats five items discussed.
30% of sprint stories enter planning without acceptance criteria. The team spends the first 3 days of each sprint in discovery, effectively running a 7-day sprint. This compresses delivery into the final days and creates quality risk.
⚡ Introduce a 45-minute weekly Backlog Refinement session. Only stories with acceptance criteria and estimates enter planning.
Engineering manager distributes task assignments at the start of each sprint, bypassing the Scrum team's self-organization principle. This creates dependency and reduces team ownership of outcomes.
⚡ In next Sprint Planning, have the team self-assign all tasks after the Sprint Goal is agreed — manager only facilitates the goal, not the assignments.
Only 1–2 stakeholders attend Sprint Reviews, and feedback is non-specific ('looks good'). The team has shipped 4 features in the last quarter that were deprioritized immediately after delivery due to misaligned stakeholder expectations.
⚡ Send a 3-sentence sprint summary email to all stakeholders 24 hours before the Review with 2 specific questions you want answered.
⚠ Stories enter the event without acceptance criteria
✓ Introduce Definition of Ready — 3 criteria before a story enters Planning
⚠ Status reporting to SM rather than peer coordination
✓ Each dev speaks to each other, not the SM. Ask: 'Who needs my help today?'
⚠ Stakeholders attend passively, provide no actionable feedback
✓ Pre-brief stakeholders with 2 explicit feedback questions 24h before
⚠ Same themes repeat; action items not tracked to completion
✓ 1 action item on the Sprint Board per retro. One done > five discussed.
Set In Progress WIP = team size (6). Test for 2 sprints.
Add a 'Blocked' swimlane — blocked items count against WIP limit.
Track cycle time per story. Target: ≤ 4 days for a 2-week sprint.
In retrospective, review WIP violations — treat them as team learning moments.
After 4 sprints, tighten WIP to team size × 0.8 if flow is stable.
Coach's Toolkit — $99: Everything in Playbook plus facilitation scripts for all 4 Agile events, stakeholder communication templates, impediment escalation framework, and a 90-day roadmap with owner assignments.
Condensed excerpt — full script in your paid report
"We're here to craft our Sprint Goal and select the work. Before we start — does everyone feel the backlog is ready? Let's check: does the top story have acceptance criteria?"
"Our Sprint Goal is [goal]. This supports our Q3 OKR: [OKR]. The top 3 stories I want to discuss are..."
"Let's do a quick planning poker on story 1. Remember — we're estimating relative complexity, not hours. I'll call 1, 2, 3 — hold your cards."
"Before we close — does everyone agree we can meet the Sprint Goal? What's the biggest risk? How do we mitigate it before sprint day 3?"
+ Daily Scrum, Sprint Review, and Retrospective scripts in the full report
To: [Stakeholders]
Subject: Sprint {N} Review — 30 min, {Date} at {Time}
Hi team,
Quick preview before Thursday's Sprint Review:
What we shipped: [3 bullet points — user-visible changes only]
Sprint Goal achievement: [✅ Met / ⚠️ Partially / ❌ Missed + why]
2 questions for you:
1. Does the onboarding flow feel intuitive? (We'll demo live.)
2. Are we solving the right problem for next quarter?
See you Thursday. No prep needed — just show up ready to react.
Implement WIP limits (In Progress ≤ 6)
📏 Success metric: Avg items in progress drops below 7
Introduce Backlog Refinement (45 min/week)
📏 Success metric: Sprint Planning time drops by 30%
Implement Definition of Ready
📏 Success metric: Stories without AC blocked from planning
Rotate retro format + track actions on board
📏 Success metric: 100% action item completion rate
Manager coaching: shift from task assignment to Sprint Goal setting
📏 Success metric: Team self-assigns 100% of Sprint tasks
Stakeholder Sprint Review workshop
📏 Success metric: ≥ 3 engaged stakeholders providing actionable feedback
Transformation Roadmap — $199: Everything in Toolkit plus framework selection guide (SAFe vs LeSS vs Scrum), OKR–Sprint alignment templates, DORA metrics dashboard, leadership coaching guide, and exec presentation deck.
Scrum fit score based on team size, industry, and current maturity
Deployment Frequency
Current: ~2/sprint
Target: Daily
Lead Time for Changes
Current: ~8 days
Target: < 1 day
Change Failure Rate
Current: ~18%
Target: < 5%
Time to Restore
Current: ~4 hours
Target: < 1 hour
Estimated current state based on assessment answers. Actual DORA metrics require CI/CD pipeline instrumentation.
Company OKR
"Achieve 95% customer retention by reducing onboarding time to under 5 minutes"
Product Goal (Quarter)
"Reduce onboarding step count from 12 to 6 while maintaining 90%+ completion rate"
Sprint Goal (This Sprint)
"Users can complete steps 1–4 of onboarding without contacting support"
Excerpt for Scrum Master role
Ready to assess your actual team? The assessment takes 12 minutes.
Start Free Assessment