Discuss, share, and learn from fellow Scrum Masters
Hey everyone! Welcome to Scrum Island, the community built by and for Scrum Masters. Whether you're a seasoned CSM or just starting your agile journey, this is your space. Drop a comment below and tell us: - Your name and where you're based - How long you've been a Scrum Master - One thing you're hoping to learn or share here Let's build something great together! 🏝️
I compiled salary data from 200+ community members. Here are the highlights: **By Experience:** - 0-2 years: $75K-$95K - 3-5 years: $95K-$125K - 5-10 years: $120K-$155K - 10+ years: $140K-$180K **By Industry:** - Tech: $110K-$165K - Finance: $105K-$150K - Healthcare: $90K-$130K - Government: $80K-$115K **Key findings:** - Remote roles pay ~5% less on average but closing the gap - SAFe certification adds ~$10K on average - Agile Coach title pays 15-25% more than Scrum Master - Contract/freelance rates: $85-$150/hour Full spreadsheet linked in the first comment. What matches your experience?
Hot take: synchronous daily standups are a waste of time for distributed teams across 3+ time zones. We switched to async standups via Slack (using Geekbot) a year ago. Results: ✅ **What improved:** - People actually think about their updates (no more "I did stuff") - Written record we can search later - No more 6am or 10pm meetings for anyone - More honest blockers reported (less social pressure) ❌ **What we miss:** - Spontaneous problem-solving - Team bonding moments - Reading body language for stress/burnout **Our compromise:** Async daily + one 15-min sync call on Wednesdays for face time. Would love to hear from other distributed teams!
Starting a new engagement next week with a team that has explicitly said they don't need a Scrum Master. They've been self-managing for 6 months and leadership brought me in because delivery has slowed. My approach: 1. Don't come in trying to change everything 2. Observe for the first sprint — attend ceremonies, look at metrics 3. Build trust through individual conversations 4. Find ONE area where I can add clear value 5. Let results speak But I'm nervous. Anyone been in this situation? What worked?
After 3 months of preparation, I passed the PSM II exam with 90%! Here's my study plan: **Resources I used:** 1. The Scrum Guide (read it 5 times, no joke) 2. "Mastering Professional Scrum" by Stephanie Ockerman 3. Scrum.org's open assessments (until I scored 100% consistently) 4. Practice exams on Mikhail Lapshin's site 5. This community's study group threads! **Key insights:** - PSM II is about understanding WHY, not just WHAT - Real-world scenarios make up most of the questions - Focus on the Scrum Master's stance as a coach and facilitator - Time management: I had 15 minutes left Happy to answer questions in the comments!
I'm at my wit's end. Our daily standup has ballooned to 45 minutes with a 7-person team. People are going deep into problem-solving mode and I can't seem to rein it in. Things I've tried: - The classic 3 questions format - Walking the board - A physical timer - Standing up (we're remote now so this doesn't work) The devs say the long standups are 'valuable' but I can see half the team zoning out. What am I doing wrong?
Just finished re-reading this classic and it holds up incredibly well. Here's my review: ⭐⭐⭐⭐⭐ **Best for:** Intermediate practitioners who want to go deeper **Key takeaways:** - The chapter on "energized work" should be required reading for every manager - The testing pyramid explanation is the clearest I've ever read - Great section on when NOT to use Agile **What I'd change:** - Could use more on distributed teams (written pre-pandemic) - The tooling recommendations are slightly dated **Bottom line:** If you read one agile book this year, make it this one. It respects practitioners' intelligence without being academic. What's the best agile book you've read recently?
I know this has been discussed a million times, but I'm seeing a new trend at my org. Leadership is pushing us back to hourly estimates because "story points aren't predictable enough." Here's my argument for keeping story points: 1. They measure complexity, not time — which is what actually matters for capacity planning 2. They reduce sandbagging (people pad hourly estimates) 3. Velocity stabilizes over time and becomes MORE predictable than hours 4. They force conversations about scope and complexity What's your go-to response when leadership pushes back on story points?
Our sprint planning used to be a marathon. Here's what changed: **Before:** PO presents every story cold, team asks questions for the first time, estimates take forever. **After:** 1. **Continuous refinement** — 2x 30-min sessions per week 2. **Pre-read** — PO shares stories 48 hours before planning 3. **Definition of Ready** — stories must meet DoR or they don't enter planning 4. **Confidence voting** — instead of debating each story, we do a quick confidence vote. Only discuss if there's disagreement. 5. **Sprint goal first** — we align on the goal before picking stories Result: 90-minute planning sessions, higher team satisfaction, better sprint goals.
I've been running retros for years, but last month I tried the Sailboat format and the results were incredible. For those unfamiliar: - ⚓ Anchors = What's holding us back - 🌬️ Wind = What's pushing us forward - 🪨 Rocks = Risks ahead - 🏝️ Island = Our goals My team opened up about issues they'd been sitting on for months. The visual metaphor made it feel less confrontational. We identified 3 concrete action items and actually followed through on all of them. Has anyone else had success with visual/metaphor-based retros?
I'll probably get heat for this, but hear me out. I've worked with dozens of Scrum Masters across multiple organizations, and the pattern I see is: - They manage the Jira board instead of coaching the team - They report status to management instead of protecting the team - They assign work instead of letting the team self-organize - They run ceremonies as checkbox exercises True Scrum Mastery is about servant leadership, coaching, and organizational change. How many of us are actually doing that vs. being glorified project managers? I'm not trying to gatekeep — I'm trying to start a conversation about how we elevate the role.
Story time. Two years ago, I facilitated a retro that went completely sideways. Context: The team had just had a terrible sprint. Missed the goal, two devs had a public argument, and the PO was frustrated. My mistake: I used a standard "What went well / What didn't" format. Within 5 minutes, it became a blame session. One person called out another directly. The PO piled on. I froze. What I should have done: 1. **Set stronger working agreements** at the start 2. **Used a format that separates people from problems** (like the 4Ls or Starfish) 3. **Had a 1:1 with the feuding devs beforehand** 4. **Called a break** when things got heated instead of freezing The silver lining: This experience made me a much better facilitator. Now I always assess team mood before choosing a retro format. What's your retro horror story?
Updated my tools list for 2026. Here's what I'm using: **Sprint Planning & Tracking:** - Linear (free for small teams, amazing UX) - Plane.so (open source alternative) **Retrospectives:** - EasyRetro (still the best IMO) - Metroretro (great templates) **Daily Standups:** - Geekbot (async standups in Slack) - Standuply (for Teams users) **Collaboration:** - Miro (whiteboarding) - FigJam (lighter alternative) **Estimation:** - PlanningPoker.live - Scrumpy What tools are you using that I'm missing?