How do you actually know your Scrum Master is doing a good job? It's a fair question, and one that trips up a lot of teams. A Scrum Master holds no formal authority over the people they serve, so the wins (and the failures) show up everywhere except on a tidy performance review.
The challenge is that the most valuable Scrum Master work—fostering psychological safety, building trust, teaching the team to manage itself—happens invisibly. Meanwhile, the visible stuff (facilitating ceremonies, maintaining Jira boards) is often the least important. Here's how to read the signals that matter.
The Nine Signals, Simplified
The original list from age-of-product.com covers nine indicators. Here's what they boil down to in practice:
1. The team ships every Sprint.** Not sometimes. Not when the stars align. Every iteration ends with a usable Increment stakeholders actually value. Everything else is secondary.
2. People want to join.** Track whether your team members would recommend an open role to a capable friend with an agile mindset. It's an "employer NPS" for your squad—and a brutally honest metric.
3–5. Values and safety are lived, not laminated.** Commitment, focus, openness, respect, courage show up in how the team handles bad news, disagreement, and Sprint failures. Psychological safety means people raise risks and admit mistakes without performing bravery.
6–7. Self-management is taking hold.** The Scrum Master can take a two-week holiday without the team stalling. The team seeks improvement because they see the point, not because someone mandated a retrospective.
8–9. Scrum is pulled, not pushed.** The team chooses Scrum deliberately—and switches to Kanban or another approach when it fits better. They understand the big picture: the problem space, the customer, the why behind the backlog.
Who Should Care About Which Signal
| Signal | Scrum Master | Team Lead / Engineering Manager | Aspiring Agile Practitioner |
|---|---|---|---|
| Consistent Increments | Prove value to skeptics | Validate investment | Anchor your pitch to business outcomes |
| Employer NPS | Early warning for team health | Hiring and retention signal | Show ROI of process investment |
| Living Scrum Values | Daily practice, not wall art | Cultural benchmark | Demonstration of competence |
| Psychological Safety | Hardest to build, easiest to erode | Retention and innovation indicator | Proof that "agile transformation" is real |
| Self-Management | Aim for invisibility | Resist the urge to micromanage | Evidence that teams can govern themselves |
| Kaizen Mentality | Facilitate, don't mandate | Reward improvement, not just delivery | Prove continuous improvement isn't theater |
| No Enforcement | Coach the organization too | Trust the framework | Show maturity beyond textbook Scrum |
| Big Picture Understanding | Remove knowledge bottlenecks | Connect work to strategy | Make the case for cross-functional teams |
Where the Optimism Meets Reality
The list is compelling but leans optimistic. In practice, you'll usually see some signals and not others—and the gaps are more instructive than the checkmarks.
A team might deliver valuable Increments and run sharp retros while the Scrum Master still bottlenecks every decision. That's dependency wearing a Scrum costume. Or Values look fine on the surface until an executive walks into Sprint Review and candor evaporates.
Treat the nine as a diagnostic, not a scorecard. Where are you strong? Where's the gap? That's your Sprint goal.
There's also a career tension here: the most successful Scrum Masters build teams that need them less. In organizations that reward visibility, this makes the role thankless. The best practitioners either find employers who understand this paradox, or they learn to communicate their value through leading indicators (trust built, decisions unblocked, knowledge spread) rather than lagging ones (Incidents not escalated).
What to Do With This
If you're a Scrum Master:** Pick the signal you're weakest on and make it your explicit focus for two Sprints. Don't try to fix everything—overcorrection looks like enforcement.
If you're a team lead or engineering manager:** Use these signals to coach, not grade. Good Scrum knowledge is table stakes. What you're hiring for is judgment about when Scrum fits and when it doesn't.
If you're building credibility for a process change:** Pick two or three signals that resonate with your leadership—reduced reporting overhead, higher team retention—and show the behavioral chain that connects to them.
Start this week: run an anonymous one-question survey. "Would you recommend joining us to a capable friend?" Share results at your next retrospective and ask what would need to change for the score to climb. That's kaizen in action, and it's how you begin earning the invisibility that marks real success.
Key takeaways
- Regular, stakeholder-valued Increments are the foundation—without delivery, nothing else on this list matters.
- Track an internal "employer NPS" to catch culture drift before it shows in turnover or velocity charts.
- Aim for invisibility: the best Scrum Masters build teams that thrive without constant hand-holding.
- Use the nine signals as a diagnostic tool, not a pass/fail checklist.
Frequently asked questions
What's the strongest signal of Scrum Master success?
Consistent delivery of valuable Increments every Sprint. If the team ships useful work stakeholders value, the Scrum Master is probably doing the other things right too.
Can a team succeed without a great Scrum Master?
Yes. The original analysis acknowledges that some teams perform well despite their Scrum Master. The role removes impediments and coaches—it's not the primary driver of outcomes.
How do I measure psychological safety on my Scrum team?
Run short, anonymous surveys each Sprint asking whether team members feel safe raising bad news, challenging decisions, and speaking up in stand-ups. Track the trend over quarters, not a single snapshot.
Should a Scrum Master enforce the Scrum framework?
No. Scrum cannot be pushed onto people—it has to be pulled. A good Scrum Master helps the team choose Scrum deliberately and switches to Kanban or another approach when circumstances warrant.
How long does it take to build a self-managing team?
It depends on the starting point, but expect several Sprints of deliberate work. A practical benchmark: if your Scrum Master can take a two-week holiday and the team still ships, you're close.