Phase 3 is focused on the team making (and reporting on) their progress in all areas
of the project deliverables. The nature of the progress will depend on the team's
chosen life cycle and plan for the current phase.
There are three core deliverables for phase 2:
the current version of any updated project documents
(charter, standards/procedures, requirements, design)
a project update document (due Friday night November 20th)
giving a ~15-minute formal team presentation on the
current state of your project deliverables,
to be done in your team's lab section (November 20th)
*The individual contribution assessments are due Monday November 23rd.In-lab team meetings/updates The entire team is expected to be present in the lab sessions on October 30th
and November 6th
to update the instructor on the current state of the project and their own work on it.
Sample versions of most project documents can be found
here, based on a fictional team and project.
The project update document
Much like the team presentations at the end of this phase, the document is meant
to give a clear summary of the progress made in the current phase and the current
state of all project deliverables.
The document should highlight:
The progress made in the current phase, and how that compared to the team's original
plan for the phase,
any changes to the assessed risks for the project,
any changes to the planned product features or functionality, or long term goals
for the project,
the current state of each deliverable (charter, standards, requirements, design,
repo/infrastructure, code base, art assets, etc).
Assessment and marks
Be sure all team members have read the contributions assessment
page, and complete and submit their assessments by the evening of November 23rd
(phase3.md in your individual contributions repos).