Acme Hotels Case Study project charter

PROJECT CHARTER TEMPLATE PURPOSE OF THE DOCUMENT: The Project Charter will serve as an internal document that captures high level planning information (scope, deliverables, assumptions, etc.) about the Project. The Project Manager creates the Project Charter in the Initiation Phase of the Project, in consultation with the Business Manager. Its purpose is to recognize the existence of the project and to begin the planning process required to accomplish the Project goals. It is not intended to be shared with the customer as a formal contract or legal document. The Project Charter is an input to the Definition Phase of the Project where much of the information contained herein forms the basis for detailed project planning. Version 0.1 PROJECT CHARTER Project Name: Project Number: Date: Revision Number: 1. JUSTIFICATION Describe the financial and/or non-financial reasons for approving this project including how the organization benefits from the project outcomes 2. BACKGROUND Provide the conditions, environmental factors and/or other background information that explains what triggered the need for this project 3. PROJECT /GOALS/OBJECTIVES Describe the business need, opportunity or problem that the project was undertaken to address i.e., the project justification. 4. DELIVERABLES Provide a high level list of what needs to be done in order to reach the goals of the project. Each deliverable should be sufficiently detailed so that the Project Team will understand what needs to be accomplished. Describe the deliverable using action words (verbs) such as deliver, provide, create, research, etc. Deliverables should be measurable, so the Project Sponsor and Team can determine whether the deliverable has been successfully completed at the projects conclusion. 5. SCOPE DEFINITION Document the scope of work to be delivered. Business requirements, functional specifications, etc. In Scope is what the project will include to meet the requirements of the Project goals. Out of Scope excludes responsibilities, activities, deliverables or other areas that are not part of the Project. The project will include: The project will not include: 6. PROJECT MILESTONES Identify the significant project milestones, including invoicing dates to the client. 5. PROJECT BUDGET Item and Details Quarter and Fiscal Year Item and Details Quarter and Fiscal Year Item and Details Quarter and Fiscal Year Item and Details Quarter and Fiscal Year Item and Details Quarter and Fiscal Year Item and Details Quarter and Fiscal Year Item and Details Quarter and Fiscal Year 6. ASSUMPTIONS, CONSTRAINTS & DEPENDENCIES Identify the assumptions that were made to form the basis of defining scope. Also identify any assumptions that will be made for the purposes of planning the project. The objective here is to set the boundaries and address how the triple project management constraint (scope, time and cost) is potentially impacted/managed. List any constraints (potential factors that will impact the delivery or make it difficult to manage the project) on the project or dependencies on resources or funding to the project. Consider time, cost, dates and regulatory issues as constraints or dependencies to the project. 7. PROJECT SUCCESS CRITERIA List what the Business will use to measure if the project is successful 8. RISKS List Risks 9. PROJECT AUTHORIZATION Approved by: Business Manager Date Approved by: Project Manager Date