Project archiving means organising and keeping the deliverables, the code and the documentation of a project so that they stay findable and reusable once the project is over, whether by another team, by the supervisor, or by yourself months later.
In the project
The Git repository is the backbone of it: it carries the history, the tags placed at each milestone (see safety and quality) and the whole of the code. Around it, a few simple disciplines make the difference: a clear folder structure, a README file explaining how to pick the project back up, stable naming conventions, and the technical design file filed together with its appendices. A well-archived project can be picked up again in an hour. A badly archived one is lost in practice, even if every file still exists somewhere.
See also
- Project planning and tracking — which drives traceability
- Safety and quality — Git versioning and tags at each milestone
- Technical design file — the central deliverable to archive