In projects it is often necessary to log events. These logs are collected in form of journals. As time passes by teams are able to find information on decisions or dates at which interesting events happened. This information may also be valuable for external stakeholders, team members returning from vacation or new team members joining a team or project. Journals have the handy property that they contain only records. Records do not need to be updated. Therefore the maintenance costs for keeping a journal are very low. There are different types of journals to keep: | Definition List |
|---|
| | Developer Diary | A developer diary collects interesting information or decisions made by an individual developer. This is not a private diary and is typically accessible for all members of the team. |
|---|
| Team Journal | Teams may collect information that is relevant for them to complete their iteration and the committed amount of work successfully. The journal is divided into sections to store relevant information collected during the team's iteration. At the end of the iteration it is easy for the team to see what has happened. While the developer diary is only write-accessible by the developer, every team member is allowed to add information to the team journal. |
|---|
| Project Journal | A project journal keeps track of events relevant to the project. The project journal may summarize or simply reference the journals at the team level. The project journal may contain additional strategic information or events from outside the teams. |
|---|
| Spike Journal | If a team is investigating on a new topic, the information is typically also aggregated in a spike journal. The journal is typically created in a new space. At the end of the spike all information that is relevant for the project, is wrapped up and integrated into the project documentation. The space containing the spike journal can then be archived. |
|---|
|
| 
