CSCI 375 Team project: preliminary project plan

Deadline

These deliverables are due by the start of the registered lab session on January 30th.

Document name

The document must be named ProjectPlan.odt and must be located in the Documents directory of your team git repository.

In this document the team is describing their plan for completing the team project.

Document overview

Provide a short (2-3 paragraph) outline of the content of this document.

Proposal update

Provide an update on the state of the project, clearly identifying any changes to the planned product/features/interface since the proposal/feasibility analysis and the reasons for those changes.

Management plan

Provide a description of your plan for managing/running the project, complete with at least the following:

• A description of the final team structure (roles and responsibilities).

• A description of the team charter.

• A list of the milestones, deliverables, and deadlines for the project.

• A description of the key technical processes your team will follow, including
  • the version control process the team plans to use to manage their team repository,
  • the development environment(s) and tools the team plans to use,
  • the code and document standards the team plans to use.

• The project metrics the team plans to track, the intended use of those metrics, the processes to be followed to gather the metrics, and the responsibilities of the team members with respect to those processes.

• The initial software development plan: a table or chart identifying all the planned project tasks, and specifying for each:
  • the task name,
  • the nature of the task (e.g. administration, design, coding, documentation, testing, etc)
  • the associated deliverable(s), if any,
  • the planned start date,
  • the planned completion date,
  • the estimated total time for the task,
  • the percent of the task that is complete to date,
  • the team member(s) assigned to the task.
  Note that the tasks planned for the near future should be fairly detailed, while those for much later stages of the project may be given at a fairly high level at this point.

Team presentation

In the lab session of January 30th, each team will provide a short (10-15 minute) presentation summarizing the information in the document described above.