Slide 1

Slide 1 text

R E T R O S P E C T I V E S I N S P E C T. R E F L E C T. C O R R E C T.

Slide 2

Slide 2 text

@mad_typist bit.ly/JLslides H E L L O I ’ M J E S S I E L I N K ! Director of Engineering, Twitter Former LivingSocial’er Former US Air Force Officer Certified Scrum Master

Slide 3

Slide 3 text

@mad_typist bit.ly/JLslides W H AT I H O P E Y O U TA K E A WAY T O D AY • 5 different types of retros you can immediately start using with your team • When to use each type of retrospective • Why to use each type of retrospective

Slide 4

Slide 4 text

T H E P R O B L E M T O D AY

Slide 5

Slide 5 text

@mad_typist bit.ly/JLslides • They get stale • People do them but don’t understand how to get the most of out of them • They are poorly facilitated • Things don’t change/improve T R O U B L E W I T H R E T R O S

Slide 6

Slide 6 text

@mad_typist bit.ly/JLslides C O M M O N M I S TA K E S • Facilitator goes in with an agenda or a pre-determined answer they want to hear • We collect feedback, but don’t identify action items • We introduce bias into the sticky note process • People read the stickies one by one • People stop doing retros, or only do them when it’s all going wrong

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

W H Y S H O U L D I D O R E T R O S ?

Slide 9

Slide 9 text

@mad_typist bit.ly/JLslides B E C A U S E F E E L I N G S A R E … . • Icky! • Hard to talk about! • Difficult to understand • Scary

Slide 10

Slide 10 text

@mad_typist bit.ly/JLslides R E T R O S C A N D O A L O T O F T H I N G S • Diagnose hidden problems and blockers • Determine root causes of a problem • Build team morale • Improve processes • Get employee buy in • Set goals

Slide 11

Slide 11 text

H O W T O R E T R O L I K E A P R O

Slide 12

Slide 12 text

@mad_typist bit.ly/JLslides I T ’ S A L L A B O U T T H E C L U S T E R S • Have your team take turns creating and summarizing the clusters for each category • Why are clusters are powerful? • What about the outliers? What if there are no clusters?

Slide 13

Slide 13 text

R E T R O # 1 The 4 Ls

Slide 14

Slide 14 text

@mad_typist bit.ly/JLslides I N S T R U C T I O N S Team fills out cards for the following categories: Lacked Longed For Learned Liked

Slide 15

Slide 15 text

@mad_typist bit.ly/JLslides W H Y I L I K E T H E 4 L S • Removes the word “wrong” from the conversation • These are evocative words • First person perspective on events during the sprint • Helps focus on outcomes (actual and desired) Lacked Longed For Learned Liked

Slide 16

Slide 16 text

@mad_typist bit.ly/JLslides H O W / W H E N T O U S E T H E 4 L S • Use the 4 Ls for a normal sprint (2 weeks), or release • Use this to diagnose root cause • “Lacked” is a particularly ripe category to find process improvements • Also useful for conferences, training, events

Slide 17

Slide 17 text

R E T R O # 2 Draw how the sprint went

Slide 18

Slide 18 text

@mad_typist bit.ly/JLslides I N S T R U C T I O N S • Hand out blank sheets of paper and pens • “Draw the sprint” • That’s it! • Intentionally broad direction - I usually tell the team “Whatever that means to you, go ahead and start drawing” • What happened, how did you feel about it? • Afterwards, take turns describing what’s happening in your picture

Slide 19

Slide 19 text

@mad_typist bit.ly/JLslides W H Y I L I K E D R A W T H E S P R I N T • Picture really is worth a thousand words. And these are words you won’t get folks to say out loud normally. • It’s fun! • Learn a lot about your team and how they think

Slide 20

Slide 20 text

@mad_typist bit.ly/JLslides

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

@mad_typist bit.ly/JLslides H O W / W H E N T O U S E D R A W T H E S P R I N T • Use this to break up the monotony, when things feel “boring” • Useful when people have been disengaged and/or not writing down much at retro • This is a retro that should be used sparingly • I recommend once a quarter

Slide 25

Slide 25 text

R E T R O # 3 Timeline retro

Slide 26

Slide 26 text

@mad_typist bit.ly/JLslides I N S T R U C T I O N S • Draw a timeline, with an arrow at the right end • Stickies represent events: • Good events • Problematic/bad events • Significant event • Once all the stickies are written, place them along the timeline approximately where they happened

Slide 27

Slide 27 text

@mad_typist bit.ly/JLslides I N S T R U C T I O N S • Use colored stickies to represent the good (green), bad (red), and significant (yellow) events • If you don’t have enough colors, as an alternative, use the above the line for good events, below the line for bad, and then on the line for significant events

Slide 28

Slide 28 text

@mad_typist bit.ly/JLslides W H Y I L I K E T H E T I M E L I N E • Easy to respond to - nice structure • Because it’s time based, it may catch things other retros won’t • Clusters happen by default • Tells a really crisp story about what happened

Slide 29

Slide 29 text

@mad_typist bit.ly/JLslides H O W / W H E N T O U S E T H E T I M E L I N E • Great for sprint retrospectives • Can be used fairly frequently • Works really well for root cause analysis of issues • Helps draw out disconnects on your team - did we perceive the same event differently? Why?

Slide 30

Slide 30 text

R E T R O # 4 Gratitude Retro

Slide 31

Slide 31 text

@mad_typist bit.ly/JLslides I N S T R U C T I O N S • Each person writes down 2-3 thank you notes for other people on the team • No clustering required! Just go around the room and read out the notes

Slide 32

Slide 32 text

@mad_typist bit.ly/JLslides W H Y I L I K E T H E G R AT I T U D E R E T R O • Helps build team chemistry • It feels nice to be nice to someone else • It’s okay to take a break from being critical and trying to fix things all the time! • Sometimes we take for granted that our teammates know we appreciate them

Slide 33

Slide 33 text

@mad_typist bit.ly/JLslides H O W / W H E N T O U S E T H E G R AT I T U D E R E T R O • Great for sprint retrospectives • Should be used as a change of pace retro. • You want the sentiments to be sincere, so beware of overuse • Use this if the team has been low energy, non-communicative • Be careful using this if the team has open conflict

Slide 34

Slide 34 text

R E T R O # 5 The Sailboat exercise

Slide 35

Slide 35 text

@mad_typist bit.ly/JLslides I N S T R U C T I O N S • Draw a sailboat - this represents our team • 4 key metaphors here: • Wind in your sails - what drives us • Anchors - what’s holding us back • Hidden dangers - what’s lurking that will crash us • Promised land - where are we trying to go

Slide 36

Slide 36 text

@mad_typist bit.ly/JLslides I N S T R U C T I O N S ( C O N T. ) • You’ll want a large piece of paper to draw your sailboat on (or a large whiteboard space) • Practice drawing these ahead of time, if you want your picture to be less ugly than mine

Slide 37

Slide 37 text

@mad_typist bit.ly/JLslides W H Y I L I K E T H E S A I L B O AT E X E R C I S E • Identifies “big” things that are impacting your team • Helps re-center the team on the things that really matter • Can be used to root out long-running issues that have plagued your team • Powerful way to surface fears

Slide 38

Slide 38 text

@mad_typist bit.ly/JLslides H O W / W H E N T O U S E T H E S A I L B O AT E X E R C I S E • It can be used for sprint retrospectives, but it is more useful when deployed strategically • Roadmap planning • When you want to “reset” a team • When you feel like there are large issues affecting your team that aren’t getting addressed in the more tactical sprint retros

Slide 39

Slide 39 text

F I N A L T H O U G H T S

Slide 40

Slide 40 text

@mad_typist bit.ly/JLslides R E M E M B E R : • Retros only work if you do them, and do them regularly • Insights drawn out of retros have a cumulative effect • Don’t wait until things are going badly! • Identify 2-3 things max to address each week • Follow up on your action items - commit but don’t be afraid to change/ rollback if the action item doesn’t work

Slide 41

Slide 41 text

@mad_typist bit.ly/JLslides T H E S E W E R E J U S T A F E W E X A M P L E S • There are dozens of variants on these, plus other formats for you to use. • http://retrospectivewiki.org/index.php?title=Retrospective_Plans • Think carefully about what you’re trying to draw out, and then choose a retro geared towards surfacing those particular bits of feedback/reaction

Slide 42

Slide 42 text

@mad_typist bit.ly/JLslides B U T W H AT A B O U T… . • Remote teams? • Teams that are extra large? • Cross-functional teams? • Etc etc etc?

Slide 43

Slide 43 text

A N D N O W, A R I N G I N G E N D O R S E M E N T F R O M M Y O L D T E A M M E M B E R … …

Slide 44

Slide 44 text

Kenny H. “You know, I came in thinking this was going to be lame, but it was actually pretty good!”

Slide 45

Slide 45 text

T H A N K Y O U !