The document outlines a structured approach to agile retrospectives, detailing a 60-minute session that includes data gathering, insight generation, and decision-making. It emphasizes Kerth's prime directive, promoting a non-judgmental atmosphere where team members are acknowledged for their efforts and contributions. Additionally, it categorizes participant engagement levels and experiments aimed at improving team integration.

1. structured agile retrospectives
Enrico Teotti - @agenteo - http://teotti.com

2. structured agile retrospectives
Enrico Teotti - @agenteo - http://teotti.com

3. gather data + decide what to do + drink beer (60 minutes)
;)
happy
;(
sad
;
meh

4. semantic satiation
Semantic satiation (also semantic saturation) is a psychological phenomenon in
which repetition causes a word or phrase to temporarily lose meaning for the listener,
who then perceives the speech as repeated meaningless sounds.
https://en.wikipedia.org/wiki/Semantic_satiation

7. do what works

8. structured agile retrospectives
someone’s agenda

10. CENSORED

12. ;) ;(;

13. Action items
Julio
Anna
Luigi
?

14. structured agile retrospectives

15. set the stage (5 minutes)
gather data (20 minutes)
generate insight (15 minutes)
decide what to do (10 minutes)
team appreciation (10 minutes)

16. setting the stage
(5 minutes)

17. Kerth’s Prime directive
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.

18. Kerth’s Prime directive
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.

19. Kerth’s Prime directive
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.

20. Kerth’s Prime directive
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.

21. Kerth’s Prime directive
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.

22. Explorers are eager to discover new ideas and
insights. They want to learn everything they can about
the iteration/release/project.
Shoppers will look over all the available information,
and will be happy to go home with one useful new
idea.
Vacationers aren’t interested in the work of the
retrospective, but are happy to be away from the daily
grind. They may pay attention some of the time, but
they are mostly glad to be out of the office.
Prisoners feel that they’ve been forced to attend and
would rather be doing something else.

23. gather data
set the stage (5 minutes)
(20 minutes)

25. https://www.thekua.com/rant/2006/03/a-retrospective-timeline/

26. generate insight
set the stage (5 minutes)
gather data (20 minutes)
(15 minutes)

28. decide what to do
set the stage (5 minutes)
gather data (20 minutes)
generate insight (15 minutes)
(10 minutes)

29. Hypothesis: starting development exchange 2 days a week with a developer on the
remote team will make us feel as one team allow us to share Pivotal values and
reduce merge conflicts.
Team integration experiment
Experiment:
* client developers participate Pivotal standup
* comunicate with client devs on flowdoc when introducing new patterns
Measurement:
* times Pivots pair with client developers
* times client developers participate Pivotal standup
* number of merge conflicts requiring merge party

32. team appreciation
set the stage (5 minutes)
gather data (20 minutes)
generate insight (15 minutes)
decide what to do (10 minutes)
(10 minutes)

33. Enrico Teotti - @agenteo
http://teotti.com
set the stage (5 minutes)
gather data (20 minutes)
generate insight (15 minutes)
decide what to do (10 minutes)
team appreciation (10 minutes)