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
⦁ Introduction and Objectives of the Project Plan
⦁ Overview of the Organization
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.
⦁ Current Situation and Problem/Opportunity Statement
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 Charter [5 Marks] (Note this section should not be revised after it has been written)
⦁ Project Information
⦁ Project objectives
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.>
⦁ Project approach
List the approach that the project will take.
⦁ Roles and Responsibilities
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.
⦁ Project Constraints
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.
⦁ Preliminary Schedule and Budget Estimates
Provide a rough estimate of how long it will take to complete <project name> and how much it will cost.
⦁ Plan Modification Rules
Describe the rules for modifying the Project Charter. For example, only the project manager has the authority to change this document.
⦁ Approval Signatures
⦁ Project Scope Management plan
⦁ Product description
Describe the solution that will be provided to address the problems/ opportunity.
⦁ Project Deliverables
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.
⦁ Scope Statement
Provide a list of what is in and out of scope of <project name>:
⦁ Work Breakdown Structure Development
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.
⦁ Scope Change Management Process
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.
⦁ Plan Modification Rules
Describe the rules for modifying the Scope Management Plan. For example, only the project manager has the authority to change this plan.
⦁ Schedule management plan
⦁ Project Schedule
This section contains information about <project name>’s schedule. A list of the milestones and their expected completion date are included in this section, while the detailed Gantt chart is included in the appendix.
State assumptions made during schedule development.
⦁ Cost management plan
⦁ Project Budget
This section contains information about <project name>’s budget. The final estimate for the project budget is provided here, while the detailed cost baseline is included in the appendix.
⦁ Budget Constraints
Describe any constraints regarding the project budget. For example, indicate which type of cost estimate was used (such as rough order of magnitude estimate, budgetary estimate, or definitive estimate). The type of estimate used determines the accuracy of the estimate.
⦁ Quality management plan
⦁ Quality Standards
Describe the different quality standards that apply to <project name>. Quality standards that apply to different areas of the project are specified.
⦁ Quality Metrics
Provide the quality criteria that are based on the quality standards and will be used to measure quality performance. For every project area identified in the Quality Standards section above, quality criteria should be specified. Similarly, provide quality metrics for the project deliverables.
⦁ Quality Management Approach
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
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
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.
⦁ Risk management plan
⦁ Risk Management Strategies
Describe how risk management will be conducted for <project name>. This can be done using a table as shown below or can be a discussion outlining how risk management will be conducted.
⦁ Risk Management Tools
⦁ Data Sources
⦁ Risk Categories
⦁ Risk Probability and Impact
(Note: Remember to address the mitigation of the risks either in the table or as an additional section)
⦁ HR management plan
⦁ Project Organization
⦁ Project Team
List the different people who will be working on <project name>. This list would include the project manager and all the team members who will be involved with the planning and execution of the project. Also, record the telephone numbers, fax numbers, and email addresses of all these individuals so that they can be reached easily whenever needed.
Also provide a graphic representation of how the project team is organized in terms of authority and responsibility for <project name>.
⦁ Key Stakeholders
Conduct a stakeholder analysis to identify key stakeholders, such as the project sponsor, project champion, as well as any external stakeholders, such as suppliers. Also include all pertinent information necessary to communicate with them.
⦁ Resource Requirements
Determine the number and type of personnel who will be needed over the duration of <project name>. This information can be represented in the form of a resource histogram, where the columns represent the number of people needed in a time period (such as a week or month).
⦁ Resource Assignment
Describe the assignment of the project team members to the different tasks required to complete <project name>. A Resource Assignment Matrix can be used for this purpose. Such a document provides a list of the different activities in the work breakdown structure and the persons who are responsible for these activities. This section can be done through Microsoft Project.
⦁ Communication plan
⦁ Stakeholder Analysis
Identify the key stakeholders and all pertinent information necessary to communicate with them.
⦁ Project Reports
⦁ Project Meetings
⦁ Project Information Accessibility
Specify the location where files and data related to <project name> will be stored. For instance, a project website can provide a centralized location for storing templates, project documents, and other communications.
⦁ Communications Summary
Include communication matrix here to document each stakeholder involved in <project name> and their communication needs.
Professional presentation and other aspects
Formatting and document control
Inclusion of Appropriate Appendices
Project plan is realistic, implementable and likely to succeed
Consistency of information across the project plan
⦁ Project Procurement Management, including but not exclusively:
⦁ Processes to Support Project Procurement
⦁ Outsourcing [if appropriate]
⦁ Planning Purchases and Acquisitions
⦁ Appropriate Documentation
project management assignment help, business management assignment help, business management assignment, management assignment help services, strategic management assignment help, management accounting assignment, management homework help, marketing management assignment help, human resource assignment help, human resource management assignment help, managerial accounting assignment help, management accounting assignment help, financial management assignment help, it management assignment help, project management homework help, hospitality management assignment help, hr management assignment help, operations management homework help, brand management assignment help, database management homework help