Advanced Scrum: Beyond the Basics

Most teams do "Zombie Scrum." They do the rituals (Standup, Planning, Retro) but they lack the soul of Agile. They treat Scrum as a way to "Track Status" rather than a way to "Deliver Value."

If your Sprints feel like a death march, and your Standups feel like a status report, you need Advanced Scrum Events. These are the unofficial rituals that high-performing teams use to crush uncertainty.

Here is what we'll cover:

1. Backlog Refinement (The Grooming): Why Planning fails without it.
2. The "Three Amigos" Session: Removing ambiguity before code is written.
3. Swarming: Identifying the bottleneck and attacking it together.
4. Design Slotting: Estimating the unknown.

1. Backlog Refinement (The Pre-Game)

Sprint Planning should take 30 minutes. If your Sprint Planning takes 4 hours, it's because you are doing Refinement during Planning.

The Rule: You cannot plan what you do not understand. Refinement is a mid-sprint meeting where you look at next sprint's tickets.

The Checklist:

• Does this ticket have a clear "Definition of Done"?
• Do we have the designs?
• Do we know the API contract?
• Estimate it now. If it's an "8" or "13", break it down before Planning starts.

Mentor Tip: If a ticket is not "Ready" by Planning, Reject it. Do not pull unclear work into the sprint "just to be nice."

2. The "Three Amigos" Session

Before a developer starts coding a complex story, hold a 15-minute sync with:

1. The Developer (You)
2. The Product Manager (PM)
3. The QA / Designer

The Agenda:

• "I plan to implement it like this."
• PM: "Wait, did you consider the edge case where the user is offline?"
• QA: "How will we test this?"

Result: You catch bugs before you write a single line of code. This is the cheapest way to fix bugs.

3. Swarming (The Anti-WIP)

"Every developer on their own island" is bad for flow. When a critical ticket is blocked (e.g., a P0 bug, or the main sprint goal is at risk), declare a Swarm.

How to Swarm:

• Stop Starting: Nobody picks up new tickets.
• Context: Everyone gathers around the one problem.
• Roles:
  • Dev A drives the keyboard.
  • Dev B researches the docs.
  • Dev C checks the database logs.

You will solve in 1 hour what would take 1 person 2 days.

4. Design Slotting (Spikes)

"How long will it take to migrate to GraphQL?" Junior Answer: "Uhh... maybe 3 weeks?" (Guessing). Senior Answer: "I don't know. Let's schedule a Spike."

A Spike is a time-boxed investigation.

• Goal: Learn, not ship.
• Output: A document or a prototype.
• Ticket: "Spike: Investigate GraphQL Migration (Max 1 Day)."

Once the Spike is done, you can estimate the real work with confidence.

Summary

Scrum is not just the events in the book. It's about reducing risk.

1. Refine early to save Planning time.
2. Three Amigos to align on requirements.
3. Swarm on blockers.
4. Spike on uncertainty.