Whether your org says Scrum Master or Scrum manager, I hire for people who improve team outcomes—not people who worship ceremonies. Here's what I'd look for.
Skills that matter
- Facilitation — meetings that produce decisions and clarity
- Coaching — help the team inspect and adapt without becoming the boss of the backlog
- Flow awareness — WIP, blockers, and cycle time over vanity velocity
- Conflict navigation — surface disagreement early and constructively
- Stakeholder shielding done right — protect focus without hiding reality
- Scrum literacy — values and empiricism, not cargo-cult rituals
- Communication — crisp updates upward; actionable prompts inside the team
- Continuous improvement — retros that change next sprint, not just feelings
What I treat as yellow flags
| Pattern | Why it worries me |
|---|---|
| Ceremony cop | Enforces form without improving delivery |
| Proxy PO | Quietly owns backlog decisions the PO should own |
| Metric theater | Velocity worship with no outcome conversation |
How I'd grow into the role
- Facilitate one planning/retro end-to-end and gather blunt feedback
- Pick one systemic blocker (handoffs, flaky tests, unclear DoD) and drive a fix
- Practice saying: "What decision do we need today?"
Day-to-day application
- Turning retro themes into one systemic fix per sprint
- Coaching the PO relationship without becoming a shadow PO
- Making blockers visible early—and socially safe to raise
- Protecting focus while still surfacing hard delivery truths
My take
Great Scrum leaders make agility visible in the work, not in the wallpaper. Pair process craft with product literacy via the PM Certification and the newsletter.