Notice: file_put_contents(): Write of 99512 bytes failed with errno=28 No space left on device in /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php on line 36

Warning: http_response_code(): Cannot set response code - headers already sent (output started at /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php:36) in /opt/frankenphp/design.onmedianet.com/app/src/Models/Response.php on line 17

Warning: Cannot modify header information - headers already sent by (output started at /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php:36) in /opt/frankenphp/design.onmedianet.com/app/src/Models/Response.php on line 20
Project diary - Wikipedia Jump to content

Project diary

From Wikipedia, the free encyclopedia
Project logs being inspected at a US Navy station

A project diary (also history, journal or log) is a record of a project which is compiled while it is being done.[1][2]

This record might be used as legal evidence if there is a dispute about the outcome of the project such as a cost overrun. To facilitate this, entries should be indelible, time-stamped and signed so that they may not be easily altered in retrospect. The details kept would typically include a record of the time and content of communications such as orders and instructions; events, incidents and their remediation; and the names of the people and parties responsible.[3]

References

[edit]
  1. ^ Triant G. Flouris; Dennis Lock (2016), "Case History or Project Diary", Managing Aviation Projects from Concept to Completion, Routledge, p. 484, ISBN 9781317101956
  2. ^ Nick Graham (2014), "Project Log Checklist", Project Management Checklists For Dummies, John Wiley & Sons, p. 126, ISBN 9781118931431
  3. ^ Randy R. Rapp (2011), "Recovery Project Diary", Disaster Recovery Project Management: Bringing Order from Chaos, Purdue University Press, pp. 144–5, ISBN 9781557535887