Driving Continuous Improvement

Continuous improvement isn't just retrospectives—it's a system.

Elements of an improvement system:

1. Sensing: How do we notice problems?

• Retrospectives
• Metrics and dashboards
• Regular 1:1s
• Team health checks

2. Deciding: How do we choose what to improve?

• Voting, dot-voting, prioritization
• Impact vs. effort analysis
• Connecting to team goals

3. Doing: How do we make improvements happen?

• Adding improvements to Sprint Backlog
• Assigning owners
• Making time for improvement work

4. Learning: How do we know if it worked?

• Tracking outcomes
• Reviewing past improvements
• Adjusting based on results

All talk, no action: Great retros, but nothing changes. Fix: Add improvements to Sprint Backlog. Track completion.

Too many improvements: 10 action items, none get done. Fix: Pick 1-2 per Sprint. Focus beats breadth.

Same problems recur: We keep having the same conversations. Fix: Root cause analysis. Address the system, not symptoms.

Only small changes: We tweak but never transform. Fix: Occasionally tackle a bigger change. Make time for it.

Improvement fatigue: Team is tired of "improving." Fix: Show results from past improvements. Celebrate wins.

Frame improvements as experiments, not permanent changes.

Why experiments work:

• Lower stakes—easier to try
• Built-in review point—we'll evaluate
• Easier to stop—it was just an experiment
• Encourage boldness—failure is learning

Good experiment structure:

• "For the next 2 Sprints, we'll try X."
• "We'll know it's working if we see Y."
• "At the end, we'll decide to keep, modify, or stop."

Example: "For the next Sprint, we'll pair on all stories. We'll track cycle time and ask the team about experience. At the retro, we'll decide if we continue."