title: A short introduction to retrospectives author: name: Henry url: https://github.com/henryaddison/retrospectives-intro-presentation output: slides.html style: slides.css theme: jdan/cleaver-retro controls: true
--
- Why?
- Who?
- When?
- How?
- What next?
- Resources
--
This talk is focussed on agile retrospectives for a tech team on a project.
But they don't have to.
--
Make the team happier: Simpleweb measure of success.
Continuous improvement of the team.
Lots of cleverer people than me recommend them.
--
The devs working on a project.
If you're a one man team then maybe just a one-on-one catch up with another dev.
If there's only two of you then you might get away being less formal.
--
Often enough that events are still fresh.
Not so often you don't have time to work and change things.
I recommend regular schedule or else it doesn't happen.
--
- Start
- Gather Data
- Generate Insight
- Decide Actions
- End
--
Before the retrospective, the team is asked to prepare up to 6 items which answer one of:
- what to start doing?
- what to continue doing?
- what to stop doing?
At the retrospective, in turn everyone shares an item.
--
Discuss the presented items as a group:
- Give everyone a fixed amount of time to lead the discussion so they can focus on what they want.
- Try and discuss items rather than solutions at this stage.
Afterwards, group together similar items.
--
Better to fix a few things than mull over many things.
Decide what to focus on by voting on the items (e.g. everyone gets two votes to decide the top 3 most important items).
Then assign actions or items to people.
--
Ultimately up to the team.
--
--
--
--
--
--
--
--
Ask me to help you get started. It's my job.
Just do it! (and let me know if you do). This is your team.
--
-
Agile Retrospective Resource Wiki has ideas for formats: https://retrospectivewiki.org/index.php
-
Atlassian have a plan for a retrospective: https://www.atlassian.com/team-playbook/plays/retrospective