Sprint Retrospectives
❓What is it
- Regular Retrospectives are dedicated sessions where teams reflect on their processes and performance, aiming to identify areas for improvement and celebrate successes.
- The event is a safe place with no observers or participants outside of the core team, encouraging an open and transparent dialogue within the team
👥Who
- Facilitated by the delivery manager, this technique involves the whole core team
🛠 Running the technique
- Retrospectives should be scheduled on a regular basis at the end of a sprint or iteration for around a one hour timeframe
- The team should jointly agree the ground rules of running this event
- Discussion is typically facilitated by the delivery manager, although volunteering to run the session offers learning opportunities in more established teams.
- Discussion should focus on how work is done and the dynamics and working relationships within team members. Discussion on the content of the work completed should be excluded- this is covered in a sprint review event
- All voices and viewpoints should be treated as equal and valid in this session, irrespective of the role
- It is recommended to use a template to help frame the conversation. There are numerous freely available templates that can be used in a physical or virtual meeting.
- Good sessions should surface at least one proposed improvement to take forward and implement in the next iteration
📖Additional Material
(Agile bootcamp handbook)
No Comments