Record the discussion of the team about their last iteration.
Record the discussion of your team about their last iteration. Take notes on what worked in the last iteration and what needs to be improved. This may be made public or kept internally to the team.
Retrospective documents are closely related to Iterations. Therefore they are attached as subdocuments.
The document type retrospective provides the following properties:
Please note that only information about specific properties is provided here. Common document property used by all document types are documented by Document Properties.
Specify where the retrospective takes place.
Log the date of the meeting.
Log the start and end time of the meeting.
List the names of the attendees of the meeting. This is usually the team, but other stakeholders may be invited.
List all items that have to be prepared to run the retrospective successfully.
This includes reserving the room, provide a whiteboard, snacks and drinks, etc.
TimelineThe team tells within 5 minutes what has happened during the last iteration. Document the essence that may be interesting in the future.
List what went well and where the team may still need to improve.
This is usually done on a whiteboard so you may want to add a picture of the whiteboard here and add only those items you want to have for text search.
What did we do well?
List what went well for later reference.
Where can we still improve?
List what can be improved for later reference.
Actions to Improve!
Make a prioritized list of actions for the next iteration.