| Iteration Retrospective |
---|
Foundation | - Timebox: (1-2) hours at the end of the iteration
- Purpose: Provides Agile team the opportunity to reflect on the committed sprint and look for opportunities for continuous improvement, and cross-functionality. What is working well, any obstacles, and action items in user stories for the next sprint.
- Attendees – SM and Team. PO is optional
- Facilitator: SM
- Preparation: Cadence has been scheduled and Retro Board shared with the team in advance.
|
Meeting Flow | Each Agile team member is transparent about the below questions: - What went well during this iteration that the team should continue doing
- What can be improved?
- What are any obstacles?
- Scrum Master helps the team in discovery – not provide answers
|
Recommended Practices | - Did the meeting start on time
- Did all the Agile Team attend the Retrospective
- Did team members feel safe?
- Retro board created and visible for the team
- Action items created as user stories for the next sprint
- Were the team members actively engage
- Did the meeting end on time
- The team is proud of their accomplishments and can celebrate
- The team event facilitated by the Scrum Master
- Did the team has webcam cameras on at all times
|
Notes from Retrospective Observations | 2022-09-02 HCD PI20 S2 Retro • Tantus Tech (mural.co)
|