The purpose of the Project Plan is to define the tasks that need to be done for the project, identify who will be responsible for each task, and provide a date by which each task will be completed.
Project Background:
• A high-level description of the problem that the project will solve.
• Reference the Customer Requirements document for more information on the features to be implemented.
Statement of Work:
• Describe all the work products that will be produced (e.g., specifications, test plans, code, defect reports, etc.) and a list of people who will perform that work.
Resource List:
• A resource list of all resources that will be needed for the product and their availability.
Assumptions:
• List any assumptions the stakeholders, the project team, and users have made.
Project Schedule:
• Identify the list of all the tasks to be performed.
• If a phased-release schedule will be required, discuss the various phases and expected deliverables for each.
• Create a project schedule that shows the calendar time required for each task and who will be working on the task.
Risks:
• Identify any risks that might be encountered and indicate how those risks might be handled, should they occur. Include external factors.
The purpose of the Project Plan is to define the tasks that need to be done for the project, identify who will be responsible for each task, and provide a date by which each task will be completed.
Project Background:
• A high-level description of the problem that the project will solve.
• Reference the Customer Requirements document for more information on the features to be implemented.
Statement of Work:
• Describe all the work products that will be produced (e.g., specifications, test plans, code, defect reports, etc.) and a list of people who will perform that work.
Resource List:
• A resource list of all resources that will be needed for the product and their availability.
Assumptions:
• List any assumptions the stakeholders, the project team, and users have made.
Project Schedule:
• Identify the list of all the tasks to be performed. • If a phased-release schedule will be required, discuss the various phases and expected deliverables for each. • Create a project schedule that shows the calendar time required for each task and who will be working on the task.
Risks:
• Identify any risks that might be encountered and indicate how those risks might be handled, should they occur. Include external factors.