- Weekly reports written with the Metrics Management Tool. Project managers write the weekly reports on Sunday or on Monday for the previous week.
- Project plan (updated 28.8.2020).
- Test plan
- Test report (v7, updated 15.12.2020)
- Final report (v8c, updated 16.12.2020)
- Project poster (A4-size pdf-document, name of the project in top, include at least one screenshot and description of the project. Check the link to get more guidelines.)
- Delivery package / project CD
Teams decide how they design software architecture, user interface and testing, and how they manage and document requirements.
Update: Instead of a project CD, it is ok to deliver a zip-file (or give a link to version control repository) that contains all project material. It is not anymore necessary to deliver a physical media. Details can be agreed in the project plan.
The project CD / DVD / Blu-ray / Memory stick should contain a README.txt file that lists the content of the CD and the locations of the files. Your project CD should contain all your documents and code.
If the project’s documentation is in a wiki or in a version control repository, it is ok to burn the whole wiki to the CD. You should make sure that the links in the wiki are self-explanatory, easy to follow and understand.
There should be at least the following documents:
- Project plan
- Requirements specification (or the corresponding product backlog, use cases and other documents related to requirements management)
- Test plan
- Design documentation, database diagrams
- Test report
- Final report
- Project poster
- Inspection / Review reports
- Project’s usability plan
- UI specification
- Heuristic evaluation reports
- Usability test reports
- User guide
- Online help
- Installation guidelines
- Configuration files, makefile
- Maintenance document