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 four core deliverables for phase 2:
a short informal presentation outlining the team plan for the remainder of the project
in general and for phase 3 in particular (to be given during your team lab session on Oct. 24th)
a project update document (due Friday night November 7th)
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 7th)
*The individual contribution assessments are due Monday November 10th.
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,
test plan, 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 10th
(phase3.md in your individual contributions repos).