Day 16 / 100 · Scrum done right · Retrospectives

Retros that change something.

A retrospective is only as good as the change it produces. Keep the structure simple and the follow-through relentless.

Gather data

What happened this sprint? Facts before opinions.

Find the why

Look for patterns and causes, not culprits.

Pick one change

One experiment, one owner, one way to tell if it worked.

Check it next time

Open the next retro by reviewing the experiment.

One change. Owned. Checked next time.