Professional Documents
Culture Documents
Project Name
Last Revision Date Prepared by: Title: Create Date: Your Name Your Title xx/xx/xxxx
Revisions........................................................................................................2
Adds............................................................................................................................................................................2 Deletes.........................................................................................................................................................................2 Modifications..............................................................................................................................................................2
Requirements.................................................................................................6
Issues and concerns.....................................................................................................................................................6 Assumptions................................................................................................................................................................6 Dependencies..............................................................................................................................................................6 Unknowns...................................................................................................................................................................6 Options........................................................................................................................................................................6
Resource Allocation........................................................................................7
Available resources.....................................................................................................................................................7
Page 1 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
Revisions
Adds
Date
Section x, Diagram 2 Section x, Paragraph 4
Date
Section x, Diagram 2 Section x, Paragraph 4
Deletes
Date
Section x, Diagram 2 Section x, Paragraph 4
Date
Section x, Diagram 2 Section x, Paragraph 4
Modifications
Date
Section x, Diagram 2 Section x," Paragraph 4
Date
Section x, Diagram 2 Section x, Paragraph 4
Page 2 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
Document Overview
This document describes the project plan for the Title of Project Project. (Describe why we are undertaking this project.) (Describe benefits to the company.) (Include a brief mention of project time lines, costs, etc.) (Describe the document and how it is to be used; i.e., Italics mean xxxx, Courier font means yyyy.) (Mention any confidentiality concerns, etc.)
Project Team
The following are key contributors to this project: Joe Smith Company X Position E-mail address: jsmith@companyx.com Phone number: (xxx) xxx-xxxx Project Manager Mary Jones Company Y Position E-mail address: mjones@companyy.com Phone number: (xxx) xxx-xxxx Karen Rodriguez Consultant Position E-mail address: krod@consultant1.com Phone number: (xxx) xxx-xxxx John Doe Company X Position E-mail address: jdoe@companyx.com Phone number: (xxx) xxx-xxxx Jane Doe Company Z Some Company E-mail address: jdoe@companyz.com Phone number: (xxx) xxx-xxxx
Page 3 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
System Overview
Use this section to discuss the project scope in detail. This section can be broken into subsections based on the information included. This can be used to: o o o o Determine projected budgets and schedules. Discuss scope. (Dont forget to include this. You need to know what is NOT covered just as much as what is.) Include system information. Describe a phased approach (if one exists).
This section is usually more than one, but less that seven or eight pages long. The shorter you can keep it, the better. The larger this document is, the greater the chances of managers NOT reading it.
Page 4 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
Deliverables
This is where you should get detailed. The information here can become critical during project closure meetings. A general description of the deliverable goes here. Point number one Point number two Point number three
Description
This is a very important part of your plan. Include a detailed description with diagrams of functionality contained in this phase.
Project Environment
List hardware, software, coding languages, staffing, disk space, network capabilities.
Page 5 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
Requirements
Describe the deliverables in terms of action work processes. List tasks to be performed. Be specific.
Deliverables
Task requirement one Task requirement two Task requirement three Etc.
Assumptions
Describe all assumptions.
Dependencies
Be careful. Some dependencies can cause scope creep if not prepared for (for example, certain bandwidth speeds need to be available, etc.).
Unknowns
An unknown can be something related to unpredictable system performance issues. Another example can be an unknown number of possible users or volume of transactions, etc. They should be things that have the potential to impact the timeline or budget in some way.
Options
Plan Bs for various project milestones if things dont happen exactly as expected or costs rise too quickly in one area.
Page 6 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
Resource Allocation
This should be the actual working section of the document which offers specifics about who is responsible for what and when they need to complete it by. You can use Microsoft Project here and include exports from that program. **Note: Be sure to not make assumptions here if any of the tasks are not in your area of expertise. Talk with the person responsible to get a realistic time frame.
Available resources
o o o o o o o 1 Project manager 1 Lead developer 8 programmers 2 q/a testers 1 network engineer 1 power user from the finance dept 1 power user from the call center Description Responsible Projected duration Actual duration Status
Task ID
Page 7 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
Timeline Summary
Milestone Timeline. Use this to let management see that progress is being made and when to expect various functionality will be completed. A quick glance should let you know if something is getting off track or not. Timeline 2/1/05 to 5/8/05 5/9/05 to 5/12/05 Milestone Coding of functionality A Testing of functionality A Description Functionality A is Test functionality against.. Status In progress Not started
Page 8 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
Sign-off Sheet
Sign-off approval
This section will hold the right people accountable for each stage of the project. Stage 1 Approval from Manager/Driver Comments Date Signature (initials)
2 3
Page 9 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
Appendix
List sources of information, documentation, code libraries, company contact info, vendor contacts, etc.
Page 10 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
Downloads:
Successful IT rollout projects: motivating users and benefits realization Project revision log Project Management FAQ
Page 11 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .
TechRepublic:
The collective voice of IT professionals
TechRepublic communities engage IT professionals in the ultimate peer-to-peer experience, providing actionable information, tools, and services to help members get their jobs done. TechRepublic serves the needs of the professionals representing all segments of the IT industry, offering information and tools for IT decision support and professional advice by topic. IT Management: Get the latest news and resources for IT management, including white papers, downloads, and articles.
Page 12 Copyright 2004 CNET Networks, Inc. All rights reserved. To see more downloads and get your free TechRepublic membership, please visit http://techrepublic.com.com/2001-6240-0.html .