How to make your retrospectives the heart of your agile process
The best meeting I had last year was 2 people in my team that written one post-it about everyone in our team with what they liked about them. It’s an example of team members taking over a retrospective to put attention to what is needed.
When you implement only one aspect of agile: let it be a retrospective. If you would use retrospectives every 2 weeks with your team, I’m convinced you will try everything in XP, Scrum, Lean, TheCoreProtocols, etc.
Objective(s) of the session: Have a sessions with the basics of a retrospective.
In this session I talk about the basics of a retrospective.
- What is a retrospective?
- Design the Stage
- Set the stage
- Gathering data
- Generating insights
- Decide what to do
- Closing and debriefing
- Instruments
- Format and length. 60 Minutes presentation - (90 minutes with questions)
- Organizer(s) and contact information: Yves Hanoulle, TBD
- Process and timetable
Intro 5 minutes
Design the Stage 5 minutes
Set the stage 5 minutes
Gathering data 10 Minutes
Generating insights 10 minutes
Decide what to do 10 minutes
Closing and debriefing 5 minutes
Instruments 5 minutes
(10 minute buffer)
(30 minutes questions for 90 minute session)
- Intended audience and prerequisites: anyone interested in learning more about having good restrospectives
- What do the presenters expect to learn from the session?
By talking about this, rememebering again good idea's for retrospectives
- Materials needed, room layout, limitations...: Projector, Whiteboard,
|
