# Retrospectives

## **5 steps**

* **Set the stage** : Regardless of what we discover, we understand that everyone did the best job he or she could
* **Gather data** : What went well and what did not.
* **Generate insights** : Teams typically identify why things happened and what should be done more, done less and tried out.
* **Decide what to do** : Deciding on specific, meaningful, agreed and realistic actions that will be done in the next Sprint
* **Close the retrospective** : R.O.T.I

## Anti patterns

* What happens in retro, does not stay in retro
  * The retrospective is a safe place : communicates only the taken actions
* Change the world 
  * Small changes : do not try to change everything at once
* No time to improve
  * Improvement is part of the life of any team
  * Time needs to be taken
* No responsibility is taken (The scrum master will do it)
  * Team responsibility (Not a 1 person job)
* Wishful thinking actions
  * Concrete actions, [SMART](https://en.wikipedia.org/wiki/SMART_criteria) actions
* Managers want to attend
  * It is not good : safe place (silence law with managers)
* One man show
  * Everyone has the right/duty to speak
  * Scrum Master has to make this happen
* No review of past action items
  * Every actions must be followed

![](/files/-MAzolEur22cF_qIRcgm)

## Resources

* <https://retromat.org/>
* Retromat megaboard : <https://miro.com/app/board/uXjVP0VHhWo=/?share_link_id=115797241698>
* <https://blog.myagilepartner.fr/index.php/retrospective/>
* <https://coach-agile.com/>
  * Agile Burger Quiz : <https://coach-agile.com/2019/08/serious-game-agile-bubur-quiz/>
  * Agile Code Smells : <https://coach-agile.com/2019/06/agile-bashing-serious-game-agile-smells/>
* Event Storming Retrospective : <https://medium.com/nick-tune-tech-strategy-blog/remote-team-flow-eventstorming-for-retrospectives-a8ea33cdb277>
* Great videos about agile anti-patterns here :

{% embed url="<https://www.youtube.com/watch?v=HsB0UZR7XvE&list=PLaD4FvsFdarQytrGAmCo2qW_rAWcfBKeV&index=2&t=0s>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://yoan-thirion.gitbook.io/knowledge-base/agile-coaching/retrospectives.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.