CSCI 265 Project Phase 6: final demo, closeout, and submission

This is it! In this final phase each team gives the final demonstration of their product, turns in the final completed versions of all the documents, code, and related content, and reviews how the various project processes and approaches worked out.

Deliverables for phase 6 are divided into the following key areas*:

a closeout document summarizing the final status of the project and reviewing the roles and processes the team followed and the design and technical choices the team made (due by 8pm Friday Dec. 6th)
all the finished documents, code, and content (including any required supporting server code/content), placed in the appropriate team repo branch/directories (due by 8pm Friday Dec. 6th)
a live demo showing off your product (this might be conducted in the final lecture or in your team's final schedule lab: details to be discussed in class Monday Nov. 18th)

*The individual contribution assessments are due 48 hours after the other documentation.

Along with the final assessments I'd appreciate any overall feedback you have individually about your team, your project, and about the overall course handling of the project, and any suggestions on how the 265 projects could be run better/differently in the future.

Marks breakdown [60 marks total]

Product demo [12 marks]
Project closeout/review document [12 marks]
Final code base and readme(s) [18 marks]
Final document collection [18 marks]

Product demo

Ideally these will be 15-20 minute live demonstrations to show off your team's final product, held either in the labs or lectures in the final week of classes (see the note below).

Show the class what your product can do, and give a brief rundown of the core features you didn't get working but would want to add if there was more time to finish things up.

Project closeout/review

This last team document (closeout.md) belongs in your usual team repo documentation directory, and is intended to both summarize the final state of the product and to provide a review of what worked and what didn't work this term.

The key components I'll be looking for in the document are the following:

Final updates:
- This section should detail any phase 6 changes to the requirements, design, standards, charter, and test plans.
End state of the product:
- This section should detail the features and functionality that was successfully incorporated into the final product.
- It should also detail any core features and functionality that wasn't successfully incorporated into the final product, estimate how much work remains before these features could be completed, and make recommendations on what order they should be completed in (if the team had the time to complete them).
Review the organizational aspects of the project:
- This section should summarize the key organizational choices the team made (i.e. from the charter and standards documents) from the perspective of which ones worked well and how the team would do things differently given a 'do-over'.
Review the technical aspects of the project:
- This section is much like the previous one, but this time focused on the design and implementation choices made by the team: which ones worked well and how would the team do things differently given the opportunity.

Final code base and readme(s)

All the final code for the product, along with all the needed supporting content/assets, should be in its final form in the appropriate branch/directory in the team repo. This includes the code/content for any team-run servers needed for the product to operate.

A clear and detailed README should be provided, giving explicit instructions on how to build the final product from the code in the repository and how to run the product.

If the product requires team-run servers then there should be a README for each server giving the instructions on how to build/configure/run the server appropriately.

(It is acceptable for the readme to direct the reader to other sources for general/background instructions on installing/running needed tools, along with sufficient specifics for the reader to build the team's product.)

Final document collection

All the core documentation produced for the project should be fixed and finalized, and available in the appropriate branch/directory in the team repo. This includes:

the team charter
the team standards/processes document
the product requirements document
the product design document
the user acceptance testing document
the project closeout document

Assessment and marks

Be sure all team members have read the contributions assessment page, and complete and submit their assessments by 8pm Sunday Dec. 8th (phase6.md in your individual contribution repos).