Case Study 11.2. Guidelines for a Retrospective Session The following list presents guidelines…
Case Study 11.2. Guidelines for a Retrospective Session
The following list presents guidelines (adopted from Talby et al. 2006) formulated by a specific team for its retrospective sessions that take place at each of its Business Days.
· l Only one specific problem is discussed at each retrospective meeting.
· l The problem discussed should relate to the development process, not the developed product.
· l The subject is chosen in advance by the moderator (after informal/formal consultation with other team members), and presented at the beginning of the retrospective meeting.
· l The retrospective cannot exceed one hour.
· l The whole team is required to attend the retrospective.
· l Everyone is proactively encouraged to speak, but is not required to do so.
· l Team members are encouraged to speak their own opinions.
· l The moderator records important insights and proposes action items that surface during the meeting.
· l The moderator summarizes the meeting by reading to the team the action items that have been decided upon.
· l The moderator publishes the main insights and action items for the team soon after the retrospective. A wiki can be used for this purpose.
· l The decided action items are effective immediately. These are changes in the day-to-day team operations that should help resolve the debated problem.