1774709 MGT210: Project
Project Management Plan (Guidelines)
Title Page
Make it captivating but professional
List your team (names and student numbers)
Include your tutor’s name
Include the word count
Document Management
Distribution List
|
Name |
Position |
Signature |
Date |
|
|
Project Sponsor |
|
|
|
|
Project Manager |
|
|
|
|
Project Team Manager |
|
|
|
|
Project Team Member |
|
|
|
|
Project Team Member |
|
|
|
|
Project Team Member |
|
|
Version Control
|
Revision # |
Change Description |
Approval Date |
Author |
|
|
|
|
|
|
|
|
|
|
Project Registration
Project Name
Project Ref #
Creation Date
Sponsor
Project Manager & PM Company Details (Name, Email contact)
Executive Summary
Should include all this but with NO SUB-HEADINGS and in ONE PAGE ONLY (single spaced):
· Brief overview and background (provide some context)
· Key objectives, success criteria and benefits sought
· Inclusion of scope statement (applying SMART approach i.e. (Specific, Measurable, Achievable, Realistic and Timed)
· Bullet point list of recommendations
Table of Contents All headings should be numbered and include relevant page numbers TOC should also include a list of figures and tables included in the report and their page numbers
The Plan (Contents)
*Note: Please include all tables / charts / figures / diagrams in the body of the report (not the Appendix), unless you feel there’s a good reason to include in Appendix (which is fine).
1. Project Integration
· Discuss the importance of project integration throughout the plan and project
· Discuss how integration will be considered across the different PMBOK Knowledge Areas.
· More importantly, ensure that project integration is evident throughout the entire Project Plan with clear understanding about how each of the PMBOK Knowledge Areas impacts, or is impacted by other areas. The requirement to consider integration is directly related to marking Criteria 2 for this assessment task: “Demonstrate integration of the PM Plan processes and phases”
2. Project Stakeholders
· Discuss how stakeholders were identified
· Generate a Stakeholder Analysis Matrix
· Identify Stakeholders (internal v. external)
· Assess stakeholders (interest in & power/impact on project)
· Identify strategies to gain support / reduce obstacles from stakeholders
· Generate Success Criteria for Various Stakeholders (table)
· Identify appropriate communication plan (link to 4.) for key stakeholders
3. Project Team (Human Resources)
· Generate an organisational chart for the project
· Identify project team responsibilities / roles (table)
· Generate a Responsibility Assignment Matrix (to demonstrate RACI)
· Identify relevant organisational policies that should be considered
4. Project Communication
· Discuss the approach/strategy of managing communication for the project
· Discuss the project team and external stakeholder communication strategy
· Generate a ‘Communications Plan’ (table)
· Discuss the project team internal communication strategy
· Discuss and / or generate a Dispute Resolution Strategy/Plan
· Identify key reporting requirements
5. Project Scope and Requirements
· Discuss the project phases
· Discuss how Scope was determined (e.g. consultation? Source/s?)
· Provide Scope Definition / Statement
· Inclusions / exclusions / constraints / assumptions
· Present Scope Statement as a SMART goal (Specific, Measurable, Achievable, Realistic and Timed)
· Generate WBS
· Identify deliverables and Acceptance/Success Criteria
· Discuss the Planned scope change control processes
· Discuss how ‘lessons learned’ will be captured throughout the project
· Discuss the handover arrangements
6. Project Time Management
· Discuss how the project schedule was determined (e.g. estimation method/s)
· Generate a high-level timeline for the project (showing project phases and milestones)
· Provide further written explanation if desired
· Generate a GANTT Chart
· Discuss how the schedule will be controlled throughout the project
· Provide further written explanation if desired
7. Project Cost Management
· Generate a project budget and a cash flow statement (if you feel confident you might want to attempt a time-phased project budget that shows planned expenditure/costs per month over the length of the project – see exhibit 9.9 p. 257)
· Provide further written explanation if desired / required (and/or budget notes)
· Discuss Budget scenarios (e.g. best v. worst case budget scenarios and need for contingency fund…JUSTIFY!)
· Discuss sources of funding
· Discuss project management fees
· Discuss how project costs will be monitored and managed throughout the project
8. Project Procurement
· Discuss approach to procurement (e.g. make v. buy)
· In tabular format identify:
· Resources that need to be procured (e.g. people / equipment / trades / contractors)
· Selection criteria for assessing suppliers (e.g. availability, cost, specifications)
· Other relevant information for each resource required (e.g. risk associated with resource, relevant organisational policies to consider etc.)
· Discuss how procurement will be monitored and controlled throughout the project
9. Project Risk Management
· Discuss the risk context and risk profile of the organisation (i.e. risk adverse, risk neutral or risk seeking)
· Undertake a SWOT analysis
· Include a Risk Rating Matrix
· Generate a Risk Register / Plan
· Discuss the ongoing management of risk throughout the project (i.e. review / ongoing identification / evaluation / relevant policies)
10. Project Quality
· Discuss any standards that may apply to the project (e.g. ISO standards)
· Generate a table of the project’s Quality Plan:
· Identify deliverables / outputs that require a quality measure
· Identify the characteristics that will be measured
· Identify quality control and assurance measures
· Include any other stakeholder requirements for quality
· Identify accountability (i.e. assign team members) for monitoring quality for each deliverable / output
· Discuss how quality will be controlled throughout the project
Authorisation
11. Recommendations
· Approximately 3-5 key recommendations should be made to your Project Sponsor regarding your Project Plan
· Recommendations should be bullet pointed only
· Recommendations should adopt a ‘SMART’ approach where possible (Specific, Measurable, Achievable, Realistic and Timed)
12. Approval
· Statement detailing what the parties are agreeing to; followed by list of options (i.e. tick boxes for either Approved / postponed / cancelled
13. Sign off (signatures) (Project Manager and Project Sponsor)
14. List of References (e.g. text, websites where you’ve access policies, information, data etc)
15. Appendices (include a copy of your Project Charter)
1