Project Plan Template

[ Team Name ]

[Project Name]

Version X

May 19, 2003

[ Team Number ]

[ Paste Your Team’s Logo Here ]<o:p></o:p>

<o:p> </o:p>

Revisions

Version	Primary Author(s)	Description of Version	Date Completed
Draft Type and Number	Full Name	Information about the revision. This table does not need to be filled in whenever a document is touched, only when the version is being upgraded. <o:p> </o:p>	00/00/00

<o:p> </o:p>

The paragraphs written in the “Comment” style are for the benefit of the person writing the document and should be removed before the document is finalized.<o:p></o:p>

A project plan is the controlling document for managing a software project.

This project plan template is intended to scale with the size of a project. On very small projects, the project plan may be the only documentation for a project. On very large projects, a family of project plans may exist. Most projects will lie somewhere in-between, with the project plan being a combination of direct information and pointers to other project documents.

Review & Approval

If appropriate, this section contains formal sign-off for both review and approval of the project plans. Normally the projects authority and agent should formally sign off the plan to launch a project.  If you do not need all this approval, you can delete this section.

Project Plan Approval History

Approving Party	Version Approved	Signature	Date
Authority 1<o:p></o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>
Authority n<o:p></o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>
Agent<o:p></o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>

<o:p> </o:p>

Project Plan Review History

Reviewer	Version Reviewed	Signature	Date
Authority 1<o:p></o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>
Authority n<o:p></o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>
Agent<o:p></o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>
Stakeholder 1<o:p></o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>
Stakeholder n<o:p></o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>
Etc.<o:p></o:p>	<o:p> </o:p>	<o:p> </o:p>	<o:p> </o:p>

<o:p> </o:p>

Contents

Review & Approval. ii<o:p></o:p>

1 Introduction. 1<o:p></o:p>

1.1 Overview.. 1<o:p></o:p>

1.2 Deliverables. 1<o:p></o:p>

1.3 Assumptions and Constraints. 1<o:p></o:p>

1.4 Reference Materials. 1<o:p></o:p>

1.5 Definitions and Acronyms. 1<o:p></o:p>

2 Management Structure. 2<o:p></o:p>

2.1 Project Lifecycle. 2<o:p></o:p>

2.2 Project Organization. 2<o:p></o:p>

2.2.1 External Interfaces. 2<o:p></o:p>

2.2.2 Internal Structure. 2<o:p></o:p>

2.2.3 Roles and Responsibilities. 2<o:p></o:p>

2.2.4 Staffing. 2<o:p></o:p>

2.3 Communication. 3<o:p></o:p>

2.4 Risk and Asset Management. 3<o:p></o:p>

2.5 Startup. 3<o:p></o:p>

2.6 Closeout. 3<o:p></o:p>

3 Planning and Control. 4<o:p></o:p>

3.1 Estimate. 4<o:p></o:p>

3.1.1 Estimation Process. 4<o:p></o:p>

3.2 Resource Identification. 4<o:p></o:p>

3.2.1 Staff 4<o:p></o:p>

3.2.2 Time. 4<o:p></o:p>

3.2.3 Cost 4<o:p></o:p>

3.2.4 Materials. 4<o:p></o:p>

3.3 Resource Allocation. 4<o:p></o:p>

3.3.1 Work Breakdown Structure. 5