Table of contents | page # |
---|---|
Introduction | 7 |
PREPARING FOR RETROSPECTIVES | |
Count your interruptions | 10 |
Walk the value stream | 12 |
Take data into the room | 14 |
Use numbers to gauge success | 16 |
Crowd source feedback | 18 |
Visualise waste | 20 |
Run an ideas box | 22 |
PROVIDING A CLEAR FOCUS | |
Renew your vows | 26 |
Focus on stakeholder relationships | 28 |
Hold a technical debt retrospective | 30 |
Use timelines with different dimensions | 32 |
Review projects with a larger group | 34 |
Compare against models, not teams | 36 |
Dissect a story | 38 |
Run periodic complexity retrospectives | 40 |
Consider waste in the wider system | 42 |
ADAPTING THE ENVIRONMENT | |
Get a room | 46 |
Involve business stakeholders | 48 |
Throw food into the mix | 50 |
Choose to travel | 52 |
Take it outside | 54 |
Do remote retrospectives | 56 |
Dim the lights | 58 |
FACILITATING SESSIONS | |
Don't just say ‘we can't’ | 62 |
Don't let facilitators solve problems | 64 |
Stand and deliver | 66 |
Allow silence | 68 |
Let the team dictate direction | 70 |
Be free inside fences | 72 |
Learn fast, don't fail fast | 74 |
Don't be scared of freestyling it | 76 |
Create a retrospective menu | 78 |
Don't let impediments become permanent | 80 |
RE-ENERGISING RETROSPECTIVES | |
Do a face-to-face team 360 | 84 |
Tailor your retrospectives | 86 |
Celebrate good times | 88 |
Keep switching your process | 90 |
Keep it short | 92 |
Switch your facilitators around | 94 |
Play retrospective roulette | 96 |
IMPROVING OUTCOMES | |
Create a business case | 100 |
Look after the pennies | 102 |
Isolate experiments | 104 |
Bake improvements in | 106 |
Task out improvement ideas | 108 |
Test assumptions with small experiments | 110 |
Don’t batch your retrospection | 112 |
Check out as well as in | 114 |
Design experiments with goal-question-metric | 116 |
Make improvements your number one | 118 |
Bibliography | 120 |
© 2014-2015 Neuri Consulting LLP