- Created by Robert Reiner, last modified on 10. Sep 2018
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 4 Next »
projectdoc Toolbox
Track what you have achieved and the reasons why. Check what you have learned and find areas where you can improve.
- ID
okr-retrospective- Suite
Take some time to evaluate the result of your work. Log what was good and where is room to improve.
Properties
The document type okr-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.
Type
Specify the type of the retrospective to organize them.
Use the objective retrospective type to define types of retrospectives.
Location
State the location where the meeting takes place.
Since this is also the meeting minutes for this retrospective it contains metadata for minutes. In case you are evaluating your progress in your retrospective alone, skip this information.
Date
State the date when this retrospective takes place. This is per default the current day.
Time
Log the start and end time of the meeting. Expected format is 09:30-10:15.
Since this is also the meeting minutes for this retrospective it contains metadata for minutes. In case you are evaluating your progress in your retrospective alone, skip this information.
Attendees
List the stakeholders that are invited to attend this retrospective.
In case you are evaluating your progress in your retrospective alone, skip this information.
Score
Log the scored value by the end of the period. The format of the value is a decimal value between .01 (or .05) and 1.
Sections
Description
Describe the reason for the scored value in a self-assessment. Also describe what you have learned.
Recap briefly what has happened during the last cycle. Document the essence that may be interesting in the future.
Note that you may specify aspects that haven been conducted well and those that may have room to improve in detail below.
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 period.
Subordinate OKR Retrospectives
In case you need to organize retrospectives in a hierarchy then add additional retrospectives as children to this retrospective. Subordinate retrospectives will then be automatically listed.
Since there is typically only one retrospective for each item there is probably no need to organize retrospectives in this way.
Preparation Items
To prepare the retrospective list what needs to be done to have all required and optional resources available.
Since this information is only relevant before the meeting and probably not useful for most readers after the event took place, the section is typically hidden and only accessible to editors of this document. It is also at the end of the document so that it does not bother editors too much either.
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.
The text of notes sections is also indexed.
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.
For further information please refer to References and Resources.
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.
For further information please refer to References and Resources.
Related Doctypes
- Wrap-up Type
Type-specific category for OKR wrap-ups.
- Check-in
Document the result of a OKR check-in.
- Key Result
Publish key results to achieve in order to pursue an objective to share with your colleagues.
- Objective
- Publish an objective to share with your colleagues.
- Strategic Theme
Publish a strategic theme to group objectives and to share them with your colleagues.
- Wrap-up
Track what you have achieved and the reasons why. Check what you have learned and find areas where you can improve.
- No labels
