Project Plan

<Project Name>

<Author Name>

---

<Note: everything surrounded by <> is either a placeholder to be filled in or a comment to be deleted when submitting the project plan.>

Table of Contents

<Bulleted list of linked major sections (first-level linked subsections may be included as well if the artifact is long).>

---

Personnel

<Organized by subteams.  The Email address should be a mailto: link.>

Name

Roles

Email Address

---

Work Packages

<All team members are responsible for performing work packages.  A work package basically defines the information involved with a task that one or more members of the team are to perform.  Such tasks could include work on a particular artifact, team or subteam meetings, or other tasks as needed.  Overall work packages are to be defined by the project manager.  Team members are to keep detailed records of what they do, for the weekly reports, and are responsible for ensuring the work packages reflect what they actually did.

Every effort should be made to ensure that work packages are up to date and that dates reflect when work is to occur.

The table entries should be filled in as below.  You may want to organize the table by team member, similar tasks, or time.  If more than one member of a team is involved with a task, you may find it easier to have a different work package for each member of the team performing that task.

• Work Package ID - unique number identifying the work package; the table cell should be green for on schedule, yellow for possibly going off schedule, red for off schedule, blue for completed, pink for waiting to begin
• Resource Names - name of the team member(s) fulfilling the task and then resources required, e.g. hardware and software
• Role - the role the team member(s) have for the task
• Tasks - bulleted list of the tasks the team member(s) is to accomplish for the work package
• Start - the date the task starts
• Finish - the date the task finishes
• % Work Completed - the amount of work completed thus far

Work package tables must be updated weekly, and the updated tables should be part of the project manager's weekly report.>

Work Package ID	Resource Names	Role	Task	Start	Finish	% Work Completed
<Package ID>	<Resources>	<Role>	<Task>	< Use MM/DD/YYYY format>	< Use MM/DD/YYYY format>	<Use ##% format>
<Package ID>	<Resources>	<Role>	<Task>	< Use MM/DD/YYYY format>	< Use MM/DD/YYYY format>	<Use ##% format>
<Package ID>	<Resources>	<Role>	<Task>	< Use MM/DD/YYYY format>	< Use MM/DD/YYYY format>	<Use ##% format>

Project Schedule Update

<The table below must be updated weekly and filled in as follows:

• Week Starting - Monday's date for the week
• On/Off Schedule - Put in On if on schedule and Off if not on schedule
• Reason Off Schedule - brief, but specific description of why the project is off schedule
• Corrective Actions To Take - brief, but specific description of what will be done to get the project back on schedule>

Week Starting	On/Off Schedule	Reason Off Schedule	Corrective Actions To Take
< Use MM/DD/YYYY format>	<Status>	<Reason>	<Actions>
< Use MM/DD/YYYY format>	<Status>	<Reason>	<Actions>
< Use MM/DD/YYYY format>	<Status>	<Reason>	<Actions>

---

To Do List

<List of items to be completed in THIS artifact.>

Items

<Item Description> 

<Item Description> 

<Item Description>

---

Revision History

Date	Name	Revision
< Use MM/DD/YYYY format>	<Name>	<Description of Revision>
< Use MM/DD/YYYY format>	<Name>	<Description of Revision>
< Use MM/DD/YYYY format>	<Name>	<Description of Revision>