Swinburne University of Technology
Faculty of Information and Communication Technologies
INF30019 Information Systems Project Management
Guideline: Look at http://www.projectmanagementdocs.com/ for some other templates and some explanations of different parts of the project plan.
FINAL PROJECT PLAN
Provide some information about <organization name>. Describe the strategic goals of the <organization name> and how top management plans to achieve these goals. Next, explain specifically how <project name> relates to these organizational goals.
The aim of this section is to clearly outline how the proposed project will benefit the organization. The current situation in <organization name> is first explained. This includes a detailed description of the relevant environmental conditions. Second, a description of the business problem or opportunity is provided. This includes a detailed assessment of the business needs that are currently being met or not met. Finally, the gap that exists between the current situation and the stated objectives of the project is analyzed.
Project Start Date:
<Enter <project name>’s expected start date here>
Project End Date:
<Enter <project name>’s expected finish date here>
<Enter the name of the project manager here>
<Enter the name of the project sponsor here>
Provide a list of what <project name> will accomplish in terms of the products/service that will be produced. Also, indicate the target benefits of <project name.>
List the approach that the project will take.
List the different people who will be working on <project name>. This list would include the project manager and all the key stakeholders who will be involved with <project name>. Also, record their role, their positions, and their contact information.
List and describe any project constraints that have been identified during the planning phase of <project name>. These constraints will affect the scope, schedule, budget, and quality of <project name>.
Any assumptions that have been made during the planning process for <project name> must be specified.
Provide a rough estimate of how long it will take to complete <project name> and how much it will cost.
Describe the rules for modifying the Project Charter. For example, only the project manager has the authority to change this document.
The signatures above represent stakeholders’ agreement and acknowledgement of the information contained in this document.
Provide a summary of the deliverables of <project name>. Only a list of the high-level deliverables is provided here. More information can be found in the Work Breakdown Structure.
Provide a list of what is in and out of scope of <project name>:
Describe how the work breakdown structure (WBS) will be developed. This describes which approach (such as top-down or bottom-up approach) will be used to develop the WBS, as well as who will be involved in the development. Produce a WBS in diagram form.
Explain how changes in <project name>’s scope will be addressed. This involves a description of how any changes in scope will be identified, addressed, communicated, and documented. Provide a list of the members of the Change Control Board who will be approving/rejecting any changes, as well as the procedures in place to request a change.
Describe the rules for modifying the Scope Management Plan. For example, only the project manager has the authority to change this plan.
Provide a description of how quality will be ensured in <project name>. This is a high-level description as more detailed information will be provided in the Quality Assurance and Quality Control sections. Provide a list of the tools that will be used in managing project quality, a description of how the tools will be used, and a list of who will be responsible for managing these tools.
Quality assurance processes are used to evaluate overall project performance and to determine that quality reviews were held, deliverables tested, and customer acceptance acquired. This section includes a description of testing and acceptance processes, verification processes, communication and documentation processes, and continuous improvement processes.
Quality control processes are used to monitor the project deliverables to ensure that these deliverables comply with quality standards. This section includes of how control information will be collected and how this information will be analyzed and used to determine whether quality standards have been met. Also describe how any deviations from acceptable quality metrics will be reported and resolved.
Holding a PhD degree in Finance, Dr. John Adams is experienced in assisting students who are in dire need...
55 - Completed Orders
Canada, Toronto I have acquired my degree from Campion College at the University of Regina Occuption/Desi...
52 - Completed Orders
Even since I was a student in Italy I had a passion for languages, in fact I love teaching Italian, and I...
102 - Completed Orders
To work with an organization where I can optimally utilize my knowledge and skills for meeting challenges...
109 - Completed Orders
JOB OBJECTIVE Seeking entry level assignments in Marketing & Business Development with an organization...
202 - Completed Orders
Current work profile Project manager- The Researchers Hub (2nd Jan 2016 to presently working) Researc...
20 - Completed Orders
Sales Assistant, Mito Marina Assigned to the Stationery dept – assisted in merchandising, stock taking...
100 - Completed Orders
Personal Profile Dedicated and highly experienced private chauffeur. High energy, hardworking, punctua...
200 - Completed Orders
I'm Lizzy, full time education specialist in English, Essay Writing, Economics and Maths. Having Assi...
109 - Completed Orders