YOU ARE DOWNLOADING DOCUMENT

Please tick the box to continue:

Transcript
Page 1: Agile retrospectives explained

agile retrospectivesMagdalena Sitarek

Page 2: Agile retrospectives explained

why retrospect?

the team sets aside a brief, dedicated period at the end of each sprint to deliberately reflect on how they are doing and to find ways to improve.

Page 3: Agile retrospectives explained

to-do

● step back● reflect● emphasize● examine● analyse● identify wins● identify issues

Page 4: Agile retrospectives explained

remember !

you want to create an atmosphere where people can focus, open up, get to the root cause of their issues, give

feedback

Page 5: Agile retrospectives explained

a retrospective is not...

● a time to blame people

Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities,

the resources available, and the situation at hand

● a forum for fixing everything○ retro often, and make small, incremental changes each time

Page 6: Agile retrospectives explained

preparation

time for conductingteam focus

time for review and implementation

Page 7: Agile retrospectives explained

Outcome

start - stop - continue

Page 8: Agile retrospectives explained

Issues ?

● too many retrospectives fail to deliver value● too often are boring, painful, senseless● lack of focus and real participation

Page 9: Agile retrospectives explained

how to make it better ?

○ What is the safety level?○ How experienced are they in giving feedback?○ What sort of issues do you expect to hear about?○ Do they need to dig deep into an 1 obvious issue, or do they

need to brainstorm and mix things up?○ Is an outside facilitator more appropriate?

Page 10: Agile retrospectives explained

set the focus

of a retrospective(s)

make sure we focus only on 1 thing covered and everybody understand it

gather data

give voice

brainstorm

set other concerns aside

document

follow up

discussion → action

Page 11: Agile retrospectives explained

technicalities

● Generate insights○ Team members write down on post-its and put them up on the board○ Moderator takes a few min to "aggregate" the issues and mentally sort through

them● Plan of action

○ Team discusses the post-its○ Comes up with action items, if needed○ (don't have to have an action item for every point--sometimes the discussion is

enough)● Close

○ Moderator reviews action items

Page 12: Agile retrospectives explained
Page 13: Agile retrospectives explained

Quadrant 1: Frown face for aspects you disliked, should be changed

Quadrant 2: Smiley face for aspects you liked, should be repeated

Quadrant 3: Light bulb for new ideas to try

Quadrant 4: Bouquet for people you appreciated

Page 14: Agile retrospectives explained

more: https://www.thekua.com/rant/2006/03/the-retrospective-starfish/

Page 16: Agile retrospectives explained
Page 17: Agile retrospectives explained

big picture - sailboat

things that slow it down (anchors)

things that propel it forward (wind)

things to look out for (iceberg)

Page 18: Agile retrospectives explained

Questions?Comments?

Ideas?

Thanks


Related Documents