Project Charter Template 4

Reviews

Shared by: ocak

Tags

Stats

views:: 1357
rating:: not rated
reviews:: 0
posted:: 1/28/2008
language:
pages:: 0

State of Minnesota Department of Office of Project Charter For the Project Revised Presented to: Prepared by: 08/12/2008 Project Charter Template v. 1.7 05/30/2006 Page 1 Office of Enterprise Technology, Project Management Office Table of Contents A. B. C. D. E. F. G. BUSINESS NEED OR OPPORTUNITY ................................................................................................................................... 3 BUSINESS OBJECTIVES .......................................................................................................................................................... 4 PRODUCT DESCRIPTION ....................................................................................................................................................... 5 CONSTRAINTS ........................................................................................................................................................................... 6 ASSUMPTIONS ........................................................................................................................................................................... 7 RISKS ........................................................................................................................................................................................... 8 AUTHORIZATIONS ................................................................................................................................................................... 9 PROJECT CHARTER APPROVAL FORM ...................................................................................................................................... 10 08/12/2008 Project Charter Template v. 1.6 07/12/2002 Page 2 Office of Technology Project Management Office A. Business Need or Opportunity Describe the business need or opportunity this proposed project will address. If the proposed project is large, complex or is critical (high impact), a separate Business Case document may be appropriate. If there is a separate Business Case document, provide a brief summary and reference that document. The discussion of the need/opportunity should be stated in business terms and should provide an understanding of:      What created the need, or how the opportunity was recognized The magnitude of the need/opportunity Contributing factors, such as workload increases or staff reductions, and fiscal constraints An understanding of the extent to which the need/opportunity would be addressed if an appropriate alternative were implemented The consequences for the Department and its “customers” if the need or opportunity is not addressed. By understanding the magnitude of the need or opportunity, the Department will be better able to estimate reasonable amounts of resources to expend in responding to it, and the extent to which a response will resolve it. 08/12/2008 Project Charter Template v. 1.6 07/12/2002 Page 3 Office of Technology Project Management Office B. Business Objectives Description Define the business objectives of the organization, which are used to establish organizational performance goals. These goals represent planned levels of what will be accomplished as a result of the project, and which can be compared to actual results. These measures can be quantified to see if the project has met the agency’s objectives. Business Objectives can be described in two different ways:  Hard Objectives—These relate to the time, cost and operational objectives (scope) of the product or process. For example: Reduce staffing expenses by 10%. Reduce cycle time of a process from six months to three. Reduce operational expenses by $150,000 per year.  Soft Objectives—These relate more to how the objectives are achieved, and which may include attitude, behavior, expectations and communications. For example: Improve customer service by doing x, y, z Improve the timeliness and accuracy of the XXXXX report Improve inter-agency communication by doing a, b, c… 08/12/2008 Project Charter Template v. 1.6 07/12/2002 Page 4 Office of Technology Project Management Office C. Product Description Describe the proposed solution, including high level estimates of cost, schedule, and key resources. Description Provide a concise, measurable statement of what the project will accomplish, and, if appropriate, what it will not try to accomplish. Project scope is documented here, at a high level. Discuss the proposed solution and the business processes that will be used with the solution and describe their characteristics. The level of detail in this section must be sufficient to allow for a more detailed scope and solution development in the Scope Statement, developed in the Planning Stage. Note: Scope creep (adding work without corresponding updates to cost, schedule and quality) may render original plans unachievable. Therefore, initial clarification of scope, and adherence to the plan throughout the project, are of the utmost importance. This effort includes the following:     This effort does not include the following:   08/12/2008 Project Charter Template v. 1.6 07/12/2002 Page 5 Office of Technology Project Management Office D. Constraints The following limitations and constraints have been identified for this project:     Upon approval of this Project Charter, the next Checkpoint will be the completion of the Scope Statement. It is estimated that the effort to create the Scope Statement will take XXXX weeks, and cost $YYYY. Under most conditions the next funding checkpoint will be the completion of the Scope Statement, as stated above. However, if the effort to create the Scope Statement is large, state the reporting requirements and define the intermediate checkpoints to ensure adequate controls are established. 08/12/2008 Project Charter Template v. 1.6 07/12/2002 Page 6 Office of Technology Project Management Office E. Assumptions Think of assumptions in terms of business, technical or project assumptions. The following assumptions were made when developing this Project Charter:       08/12/2008 Project Charter Template v. 1.6 07/12/2002 Page 7 Office of Technology Project Management Office F. Risks Describe the major risks and the risk management strategy associated with those risks. 08/12/2008 Project Charter Template v. 1.6 07/12/2002 Page 8 Office of Technology Project Management Office G. Authorizations Specific project roles and responsibilities have been agreed-upon as follows: The project sponsor: The project owner: The project manager: The Project Charter will be approved by: The Project Sponsor The Project Owner Project Changes will be approved by: The Project Owner 08/12/2008 Project Charter Template v. 1.6 07/12/2002 Page 9 Office of Technology Project Management Office PROJECT CHARTER APPROVAL FORM Project Name: Project Manager: The purpose of this document is to provide a vehicle for documenting the completion of the project initiation stage. It is used to reach a satisfactory level of mutual agreement among the project sponsor, the project owner, and the project manager on the high level objectives and scope of the project before significant resources are committed and expenses incurred. I have reviewed the information contained in this Project Charter and agree this project should continue to the next funding checkpoint, as defined in this document. ____________________________________________________________________________________ Project Owner: Date ____________________________________________________________________________________ Project Sponsor: Date 08/12/2008 Project Charter Template v. 1.6 07/12/2002 Page 10 Office of Technology Project Management Office