Record the discussion of the team about their last iteration.

ID
retrospective
Suite
Agile Team
Parent
Doctypes for Agile Planning
Documentation Type
Q2 - Project
Categories
/ Work / Check
Tags
Agile Planning

Description

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.

Properties

The document type ${doctype-name} provides the following properties:

Location

Specify where the retrospective takes place.

Date

Log the date of the meeting.

Time

Log the start and end time of the meeting.

Attendees

List the names of the attendees of the meeting. This is usually the team, but other stakeholders may be invited.

Sections

Preparation Items

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.

Timeline

The team tells within 5 minutes what has happened during the last iteration. Document the essence that may be interesting in the future.

Discussion

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.

Notes

These are internal notes that are usually not exported and only visible to team members with write access.

But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.

References

For a document the references section contains pointers to resources that prove the statements of the document.

Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.

Resources

The resources section provides references to further information to the topic of the document.

This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.