Project plan

Each project group is required to hand in a project plan. A template and example of the plan can be found in your group git repo under path-to-repo/report/plan/example/.

The plan should contain:

• Projet title; year; group member names and e-mail addresses.
• An overview of the project.
• Descriptions of the key parts of the project, including
  • equipment and materials.
  • modeling.
  • design (hardware, software, control principles).
  • implementation.
• A decomposition of the project into subtasks and suggested allocation of the project resources to key tasks.
• A time plan (using a Gannt chart (Links to an external site.) provides good overview). 
• A risk assessment, where major risks (e.g. delay of ordered component, a method not working as intended, etc.) are identified and brief contingency plans for those risks are presented.

Some useful hints for the project planning and execution

• Break the project into manageable subtasks.
• Establish dependencies between subtasks.
• Estimate time required each subtask (man hours/days).
• For each week estimate how many hours every member of the team will work.
• Plan deadlines for each subtask using the estimates above.
• Put any spare time you might have at the end of the schedule, not the beginning!
• Follow up on your progress weekly, and schedule more time if you are falling behind.

The plan should be detailed enough to track weekly progress. If you need to order some equipment for your project, first confirm it with your project advisor, and it is important to schedule time for component ordering and delivery in your plan.