(And How to Steer Around Them)
Learning to spot the potholes is half the battle. The other half? Riding together without blaming the bumps.
Scrum is like learning to ride a bike.
You start wobbly. You hit a few curbs.
Maybe fly over the handlebars once or twice.
And that’s okay.
Because it’s not about being perfect — it’s about learning to spot the potholes before they throw you off balance.
In this blog post, we’ll walk through 10 common Scrum “antipatterns” — habits that sneak in looking helpful but can quietly slow you down, confuse your team, or make Agile feel a little… broken.
No shame. No finger-pointing. Just a friendly map of what to watch for and how to steer better.
🕳️ 1. The Standup That Feels Like a Pop Quiz
What it looks like:
Everyone’s reporting progress to the Scrum Master like it’s their manager. “Yesterday I did X, today I’ll do Y…”
Why it’s tricky:
Standups aren’t for reporting up. They’re for syncing with each other. If it feels like a quiz, no one’s going to be honest about blockers.
Try this instead:
Picture it like a pit stop. What does the team need to keep moving smoothly? Talk to each other, not just “at” someone.
🕳️ 2. The Retrospective Where Nothing Changes
What it looks like:
Everyone shares feedback… but next sprint, it’s déjà vu. Same issues. Same stuck points.
Why it’s tricky:
If nothing changes, people stop speaking up.
Try this instead:
Make retros actionable. Pick one small thing to try — like sprint experiments. Think “tiny upgrade,” not total overhaul.
🕳️ 3. The Missing Product Owner
What it looks like:
The team needs quick decisions or clarification — and the PO is either busy, unclear, or unresponsive.
Why it’s tricky:
Without a clear voice on what to build and why, the team ends up guessing.
Try this instead:
Agree on regular PO check-ins. If you’re the PO, think of yourself as the team’s navigator — they can drive, but they need directions.
🕳️ 4. The Backlog That’s a Junk Drawer
What it looks like:
The backlog has 200+ tickets. Some are old. Some are vague. Some are written like cryptic prophecies.
Why it’s tricky:
Teams can’t focus if they’re digging through clutter.
Try this instead:
Keep the backlog lean. Prioritize ruthlessly. If an item’s unclear, refine it or park it elsewhere. Clean drawers = clear thinking.
🕳️ 5. The Obsession with Story Points
What it looks like:
Every conversation ends with, “But how many points is it?” Like Agile turned into a math competition.
Why it’s tricky:
Points are a tool, not a goal. Chasing velocity can lead to weird behaviors (like inflating estimates).
Try this instead:
Use velocity as a guide, not a scoreboard. What matters most? The value you deliver — not the number you assign to it.
🕳️ 6. The Scope-Swapping Sprints
What it looks like:
Mid-sprint, someone says, “Can we just add this one quick thing?” Suddenly, everything’s changing.
Why it’s tricky:
Interruptions break flow and make the sprint goal blurry.
Try this instead:
Set a clear sprint goal. If something urgent comes up, discuss as a team: pause, replan, or push it to the next sprint?
🕳️ 7. The Scrum Master Who’s Just an Admin
What it looks like:
They run the meetings, move tickets, and book rooms… and that’s it.
Why it’s tricky:
Scrum Masters aren’t secretaries. They’re coaches.
Try this instead:
Focus on building trust, unblocking the team, and nudging improvement. Think facilitator > note-taker.
🕳️ 8. The Sprint Plan That’s… Ambitious
What it looks like:
Every sprint starts with more work than the team has time for. There’s pressure to commit to everything.
Why it’s tricky:
Overloading breaks confidence. Missed goals feel like failure — even when it’s just unrealistic planning.
Try this instead:
Start small. Let the team pull what they believe they can actually finish. Celebrate success, then build up.
🕳️ 9. The Loosey-Goosey “Done” Definition
What it looks like:
Developers say, “It’s done!” — but QA hasn’t tested, and nothing’s deployed. Surprise!
Why it’s tricky:
Confusion around “done” leads to missed quality, bugs, and awkward demos.
Try this instead:
Agree on a Definition of Done as a team. It’s your “ready to deliver” checklist. Use it every time.
🕳️ 10. The Agile Costume Party
What it looks like:
You’ve got the standups. The boards. The labels. But the mindset? Not quite there.
Why it’s tricky:
Without continuous improvement, Agile becomes performance art. People go through motions but don’t feel empowered.
Try this instead:
Ask real questions. “Is this working for us?” “What would make it easier to build great stuff?” Drop what doesn’t serve.
🧠 Final Thoughts: You’re Not Failing — You’re Learning
Every bump you hit is proof you’re moving -not failing. Keep going. The rhythm comes with the ride.
If you’ve spotted one (or three) of these on your team, take a deep breath. You’re not doing it wrong — you’re just finding your rhythm.
Scrum isn’t about perfect process. It’s about continuous improvement, honest reflection, and making your team’s life a little saner with each sprint.
So keep riding.
Keep adjusting your balance.
And if you hit a bump? That just means you’re moving forward.
🔥If you liked this article, check out the next one where we walk through how to write clear, concise, and complete user stories.
Written by
Simina F.
| howtobecomeapm.com – Author
|