Professional Documents
Culture Documents
Project Archive Checklist
Project Archive Checklist
Confidentiality Statement
This <document title> along with all attachments hereto shall be considered <company>s
Proprietary/Confidential Information
gantthead.com
Project Name
Project Manager
Date
Prepared by
Indexed?
Location
in Archive
Date
Status/Comments
Initials
2007 gantthead.com
gantthead.com
gantthead.com
Performance Measurement
Documents
Notes and Files of Key Project
Stakeholders
Other Documentation (Specify)
2007 gantthead.com
gantthead.com
Ensure that the archive of the product and the audit trail of that product's development have been
collected in pursuance with the following archive policy standards.
Store hard copy artifacts according to corporate retention and archive standards as appropriate.
Store hard copy artifacts that will be of use to future projects in an available location and make
others in your organization aware of that location.
Use a folder structure to store electronic artifacts that is a documented standard within your
organization.
Secure artifacts as necessary so they cannot be modified.
Include a description of the artifacts being stored, the software used to create the artifacts, and a
point of contact.
Make sure the maintenance and operations team has awareness of, and access to, all the project
artifacts that will be of use to them to maintain the projects deliverables going forward.
Make sure "Lessons Learned" documents are available through the Lessons Learned library, in
electronic form as well as in print.
Consider establishing a project library to hold artifacts.
Store and archive hard copy documents according to organizational standards.
Make hard copy documents useful for future projects available through the project library.
Make sure that the project archive contains a file describing everything it contains.
Archive all development source code, tools, and procedures critical to producing the executable
product and supporting products, including:
Two backups of source code, batch, and make files
Two backups of development tools (compilers, assemblers, linkers, source-control systems,
etc.) and supporting software documentation and license agreements
Instructions on how to produce all program files in final and debug versions and instructions
for producing release diskettes
All help files (both source and "compiled") and supporting tools and documentation
Release notes
Any of the above applicable to third-party components
Archive all SQA tools and procedures critical to testing the product, including:
Test procedures, macros, and files; unit test cases and harnesses; and all relevant
supporting documentation
Test results and logs (including, e.g., coverage analysis reports for unit and system tests,
test history log, etc.)
Test tools, supporting documentation, and license agreements
Bug database, supporting tools and documentation, and license agreements
Support release notes
Any of the above applicable to testing of third-party components, devices, or external testers
Archive all documentation tools and information critical to producing shipping documentation and
help files of the product, including:
All illustration (art) files
All document (text) files
All page-layout files, illustrations, and the page-layout template files
All tutorial and demo files, supporting tools and documentation, and license agreements
Supporting production tools (such as illustration or page-layout applications) with license
agreements and documentation
Any of the above applicable to documentation of third-party components or documentation
tools
2007 gantthead.com
gantthead.com
2007 gantthead.com
gantthead.com
Client Representative
[Other signature lines; specify]
Crosscheck
Ask yourself the following questions:
Are any hard copy artifacts that would be useful for future projects available through the Project
Library?
Does the archive contain a file describing the artifacts it contains?
Does the folder structure used to store electronic artifacts meet company and industry
standards?
Does the maintenance team have access to all the artifacts that could help them maintain the
project's deliverables?
Are "Lessons Learned" documents available through the Lessons Learned library, in electronic
form as well as in print?
Have all stakeholders signed off on the Archive Policy Compliance Sign-off sheet?
2007 gantthead.com