Agile-and-Scrum **Agile Coaching & Facilitating Retrospectives (Techniques) – Zero-Fluff Study Guide**

Agile Coaching & Facilitating Retrospectives (Techniques) – Zero-Fluff Study Guide

For Scrum Masters, Agile Coaches, and Teams Who Want to Run Retros That Actually Drive Change

1. What This Is & Why It Matters

A retrospective is the Scrum event where the team inspects its process and adapts for the next Sprint. It’s not a "post-mortem" (that’s for dead projects) – it’s a live, actionable feedback loop.

Why it matters in production:
- Without retrospectives, teams repeat the same mistakes (e.g., late integration, unclear acceptance criteria, unplanned work).
- Without facilitation, retrospectives turn into complaint sessions (e.g., "Management sucks" → no action → team disengages).
- Without coaching, teams stay stuck in "doing Agile" instead of "being Agile" (e.g., they follow Scrum mechanically but don’t improve).

Real-world scenario:
You’re a Scrum Master for a team that just delivered a Sprint with: - 30% unplanned work (emergency bugs, last-minute scope changes).
- 2 developers burned out from overtime.
- A stakeholder complaining that "Agile isn’t working" because the team missed a deadline.

Your job: Run a retrospective that: 1. Uncovers the root causes (not just symptoms).
2. Generates actionable improvements (not vague "we should communicate better").
3. Gets the team to own the solutions (not just nod and forget).

If you fail, the team will keep shipping late, burning out, and blaming "the process."

2. Core Concepts & Components

3. Step-by-Step: How to Run a Retrospective That Works

Prerequisites:
- A team that just finished a Sprint (or a major milestone).
- A whiteboard (physical or digital, e.g., Miro, Mural).
- 60-90 minutes blocked on the calendar.
- A facilitator (you or a neutral party).

Step 1: Set the Stage (5 min)

Goal: Create psychological safety and align on purpose.
What to do:
- Start with a check-in question (e.g., "On a scale of 1-5, how was this Sprint for you?").
- Remind the team: "This is about improving our process, not blaming people." - Share the retro structure (e.g., "We’ll brainstorm, then vote on 1-2 actions").

Why it matters:
If people don’t feel safe, they’ll hide problems → no real improvement.

Step 2: Gather Data (15-20 min)

Goal: Collect facts, feelings, and observations about the Sprint.
Technique: Mad/Sad/Glad (or Start/Stop/Continue) How to run it:
1. Draw three columns on the board:
- Mad (Frustrations, blockers, things that wasted time)
- Sad (Disappointments, missed opportunities)
- Glad (Wins, things that went well) 2. Give everyone 5 minutes to write sticky notes (1 idea per note).
3. Have each person share 1-2 notes and place them on the board.
4. Group similar notes (e.g., "Too many meetings" + "Unplanned work" → "Interruptions").

Example output:
| Mad | Sad | Glad | |---------|---------|----------| | "Last-minute scope changes" | "We didn’t finish the API integration" | "Pair programming helped debug faster" | | "Too many ad-hoc requests" | "QA was a bottleneck" | "Daily standups were useful" |

Production insight:
If "Mad" is full of "management sucks," dig deeper: "What specifically about management’s actions caused problems?"

Step 3: Generate Insights (15 min)

Goal: Find root causes, not just symptoms.
Technique: 5 Whys (for the biggest "Mad" or "Sad" item) How to run it:
1. Pick the most voted issue (e.g., "Last-minute scope changes").
2. Ask "Why?" 5 times to find the root cause.

Example:
1. Why did we have last-minute scope changes? → "Stakeholders didn’t review the backlog early." 2. Why didn’t they review early? → "They didn’t know it was ready." 3. Why didn’t they know? → "We didn’t share the backlog with them." 4. Why didn’t we share it? → "We assumed they’d ask." 5. Why did we assume that? → "No process for early feedback."

Root cause: "No process for early stakeholder feedback."

Production insight:
If you stop at "stakeholders are bad," you’ll never fix the real problem.

Step 4: Decide What to Do (15 min)

Goal: Pick 1-2 actionable improvements.
Technique: Dot Voting
How to run it:
1. List potential actions (e.g., "Add a backlog refinement session with stakeholders").
2. Give everyone 3 dots to vote on the most important action.
3. Pick the top 1-2 actions with the most votes.

Example actions:
- "Add a 30-minute backlog refinement with stakeholders every Sprint." - "Timebox ad-hoc requests to 1 hour/week per developer."

Production insight:
If the action is "be better at communication," it’s useless. Make it specific and measurable.

Step 5: Close the Retro (5-10 min)

Goal: Ensure commitment and end on a positive note.
What to do:
1. Assign owners to each action (e.g., "Sarah will schedule the backlog refinement.").
2. Add actions to the next Sprint Backlog (so they’re visible).
3. End with a check-out (e.g., "One word to describe how you feel about the retro.").

Why it matters:
If you don’t assign owners, nothing will happen.

4. ? Production-Ready Best Practices

Facilitation

• Timebox everything. If you don’t, the retro will drag on.
• Rotate facilitators. If only the Scrum Master runs retros, the team won’t own the process.
• Use a timer. (e.g., "5 minutes to write sticky notes").
• Avoid "groupthink." If one person dominates, use round-robin sharing (go around the room).

Psychological Safety

• Never blame individuals. Focus on systems (e.g., "Why did the process allow this?").
• Encourage quiet voices. Ask, "Does anyone have a different perspective?"
• Normalize mistakes. Say: "Mistakes are data – let’s learn from them."

Actionable Outcomes

• SMART actions only:
• Specific ("Add a Definition of Ready" vs. "Improve quality")
• Measurable ("Reduce unplanned work by 50%" vs. "Do less unplanned work")
• Achievable (1-2 actions max per retro)
• Relevant (Directly tied to a root cause)
• Time-bound ("By next Sprint")
• Add actions to the Sprint Backlog. If they’re not visible, they won’t get done.

Follow-Up

• Review retro actions in the next Sprint Planning. "Did we do what we said we’d do?"
• Track metrics. (e.g., "Unplanned work dropped from 30% to 10%").
• Celebrate wins. If an action worked, acknowledge it.

5. ⚠️ Common Mistakes & Traps

6. ? Exam/Certification Focus (PSM, CSM, etc.)

Typical Question Patterns

1. "What’s the purpose of a retrospective?"
2. Trap answer: "To discuss what went wrong."

3. Correct answer: "To inspect the team’s process and adapt for the next Sprint."

4. "Which technique helps uncover root causes?"

5. Trap answer: "Brainstorming."

6. Correct answer: "5 Whys" or "Fishbone Diagram."

7. "What’s the most important outcome of a retro?"

8. Trap answer: "A list of problems."

9. Correct answer: "1-2 actionable improvements."

10. "How do you ensure psychological safety in a retro?"

11. Trap answer: "Don’t let people criticize management."
12. Correct answer: "Focus on systems, not individuals, and encourage all voices."

Key Distinctions

• Retrospective vs. Sprint Review:
• Retro: Team process (how we work).
• Sprint Review: Product increment (what we built).
• Facilitator vs. Participant:
• Facilitator: Guides the discussion, doesn’t dominate.
• Participant: Contributes ideas, owns actions.

Scenario-Based Question

"Your team’s retro keeps ending with ‘we’ll try harder next Sprint.’ What’s the problem, and how do you fix it?" - Problem: Actions are too vague.
- Fix: Use SMART actions (e.g., "Add a Definition of Ready by Friday").

7. ? Hands-On Challenge

Challenge:
Run a 5-minute retro with a teammate (or yourself) using the Start/Stop/Continue technique.
1. Ask: "What’s one thing we should start doing, stop doing, and continue doing?" 2. Pick one action and commit to it for the next week.

Solution:
- Start: "Add a 5-minute buffer between meetings." - Stop: "Working through lunch without breaks." - Continue: "Daily standups at 9:30 AM."

Why it works:
- Forces specificity (no vague "be better").
- Takes <5 minutes (proves retros don’t have to be long).

8. ? Rapid-Reference Crib Sheet

9. ? Where to Go Next

1. Scrum Guide 2020 – Retrospective (Official definition)
2. Agile Retrospectives: Making Good Teams Great (Book by Esther Derby & Diana Larsen)
3. Fun Retrospectives (Free techniques & templates)
4. Miro Retrospective Templates (Digital whiteboard templates)