Notes
Notes
- Definition: At the end of an Agile sprint you have a meeting to asses what went well and what could be improved
- Framework
-
- What worked well
- What needs to change
- 4Ls
-
- Liked
- Learned
- Lacked - Things we could change
- Longed For - Things that have external factors
- Having structure for the retrospective is more important than which framework you choose
- Trust is important
- Daily stand-ups are a good place to identify trust issues
- Stakeholders are not in sprint retrospectives, but they are in end of project retrospectives.
Managers can not be allowed in the meeting. Some people may not be comfortable giving feedback regarding managers.
Having a “safe space” is critical.
When topics get hot discussion stops and a separate meeting occurs with the individuals.
Have multiple notetakers to get multiple perspectives.
Types of retrospectives
- Team (Quarterly)
- Project (End of project with stakeholders) 90 mins
- Sprint (scrum team only) 45 mins
- Post-incident (when something bad happens) - 30 mins
Separate retrospectives can be had to discuss the affect of non-project related work in order to surface trends.
No one system works for everyone. Adjust as you go.
Pick a few of the “could be better” items and work on those to be able to show progress next time.
