Question: BUS 5 0 0 3 - Project Charter Project Title Document Version History Creation / Change Date Author Reason for Change Distribution List 1 .

BUS 5003- Project Charter
Project Title
Document Version History
Creation / Change Date Author Reason for Change
Distribution List
1.
2.
3.
4.
5.
6.
Table of Contents
1.0 Project Overview 2
2.0 Project Objectives 2
3.0 Project Scope 3
4.0 Project Preliminary Schedule 4
5.0 Project Organization & Communications 5
6.0 Project Risk Identification and Assessment 5
7.0 Project Cost 6
8.0 Acceptance Criteria 7
Appendix A: Project Network Diagram 8
Appendix B: Project Team Structure 9
Appendix C: Change Control Process 10
Appendix D: Optional 11
1.0 Project Overview
Provide an executive summary of the proposed project in a few sentences. Makes sure you include the following (and delete these instructions after you complete this section);
1. Project Title
2. Aim / purpose of the project
o Problem the project will address / solve
o Rationale for the proposed solution
3. Anticipated results (what will be different after the project has been completed), including a description of the value of this project to the public.
2.0 Project Objectives
Describe the overall goal of your project and the opportunity the project deliverables will provide its Stakeholders. Provide this high-level information in one sentence.
Then provide a numbered list of your objectives (e.g. next level WBS, should be around five objectives), and ensure each objective is a full statement / sentence that includes an action and a result (e.g. Develop and approve the rubric for this assignment to ensure students understand how they will be evaluated). Delete these instructions after you complete this section.
1.
2.
3.
4.
5.
3.0 Project Scope
Objective
(must match wording from the precious section exactly) In Scope
(sub-objectives / next level WBS) Out of Scope Sequencing (consecutive / concurrent)
1.1a)1b)1c)
2.2a)2b)2c)
3.3a)3b)3c)
4.4a)4b)4c)
5.5a)5b)5c)
4.0 Project Preliminary Schedule
Key Activities / Milestones Estimated Start Estimated Finish
1. List your first objective here...
1.a) first sub-objective here...1.b)
2. Same as above...2.a)
3. Same as above...3.a)
4. Same as above...4.a)
5. Same as above...5.a)
5.0 Project Organization & Communications
5.1 Project Stakeholders - Groups or organizations whose interests may be impacted by the execution or completion of the project, and who may exert influence over the project and its deliverables. It should always include the Project Sponsor (authorizes the project) and the client/ business owner (the person/ group who will accept the project deliverables upon completion - may be the same as the sponsor).
Group/Individual Role (Project Interest or Impact) Internal/External
(e.g. Departmental Employees as identified in the Case Study)(e.g. users of the new service)(e.g. internal)
5.2 Project Team - Names for critical resources and/or identified team members who will be responsible for performing the work of the project.
Name Organization / Department Role
(e.g. Susan Jones as identified in the case study)(e.g. Office of Strategy Management)(e.g. Project Manager)
5.3 Project Communications Plan Key information to be collected and distributed to stakeholders based on project requirements.
What Information? Target Audience Frequency / When? Method of Communication Provider
1. e.g. Project Status Report and agendas Project Sponsor, Team, staff and customers Weekly Email Project Manager
2.
3.
4.
5.
6.
6.0 Project Risk Identification and Assessment
6.1 Risk List - the following list identifies early project risks, assumptions, constraints, etc., including, (but not limited to) the scope, schedule, budget (including vendor management), resource availability, organizational structure, legal requirements, etc.
# Risk (uncertain event that may be impact the project either positively or negatively)
1. Vendor technical resource availability
2.
3.
4.
5.
6.2 Risk Analysis the following analysis expands upon the risks listed above to consider the following;
o Impact of the risk occurring High, Medium, Low
o Probability of the risk occurring High, Medium, Low
o Timeframe in which the risk might occur Near, Mid, Far
o Consequence of the risk occurring potential impacts on the project
o Strategy - for managing the risk
This analysis will be discussed by the Project Manager (PM), Sponsor and Client/Business Owner. Ranking should be determined by the PM, based on anticipated levels of Impact/Probability/Timeframes.
No. Risk (from list above) Impact Probability Timeframe
1. IF, the vendor technical resources are not supplied to the project by February 29,2008. High Medium Mid-Term
THEN (consequence), project may not kick off March 12,2007 causing a delay.
RESPONSE: Avoid,

Step by Step Solution

There are 3 Steps involved in it

1 Expert Approved Answer
Step: 1 Unlock blur-text-image
Question Has Been Solved by an Expert!

Get step-by-step solutions from verified subject matter experts

Step: 2 Unlock
Step: 3 Unlock

Students Have Also Explored These Related General Management Questions!