TEMPLATE Project Charter

  • View
    57

  • Download
    2

Embed Size (px)

Transcript

Department or Program Name

[SYSTEM/APPLICATION NAME]Template Project Charter

SYSTEM/APPLICATION NAME

PROJECT CHARTER

Project CharterTemplate GuidelineRemove these guidelines from the completed document.Definition The Project Charter is the end result of all the activities done in the Ideation Phase. This is NOT intended to be a Business Case, Statement of Work (SOW) or Business Requirements Definition (BRD) at this early stage, but rather a high level summary of what the proposed project is to deliver. This template is used to define project deliverables to a level of detail known at the time and to then authorize the work to be completed. It documents the project vision, scope, goals and objectives. It builds off the project Business Case, and is the starting point for the project management plan and MS Project schedule. The Project Manager produces a Project Charter document in conjunction with the project business sponsor. Prior to proceeding, approval is required from the key Stakeholders within the requesting line of business. As the culmination of the Ideation Phase, it is normally completed very early in the project lifecycle. A Project Charter is a required deliverable on all Large and Medium projects. A combined project charter/project plan is required for all Fast Tracked projects. Template Flexibility This Project Charter template includes data input fields that support internal controls and processes, corporate policies and risk mitigation principles, governance drivers, and/or project management control standards and proven best practices as well as detailed project scope or deliverables. It provides the minimum basic fields required to complete the project charter deliverable in meeting PMO requirements. The amount of detail included in the template will depend on the size, complexity and type of proposed project, as well as the extent of information that is known about the project at the time of completion. Authors are empowered to utilize this template as necessary to best serve the needs of the proposed project and business owner. Each data input field provided in this template should be considered for applicability and relevance to the project. Template Completion 1. This Template Guidelines section is for reference purposes only. It should be printed and deleted prior to completing the final document. 2. To input text within a text field (), place the cursor inside the field and just start typing. 3. Enter the required information on the document information sections and the working sections of the Project Charter. 4. Complete the document utilizing suggested text where applicable and entering text/fields where shown within brackets. Note that the blue text is NOT to be included in your final document. Its purpose is to either provide guidance for completing requested information, or to show where text is to be input. 5. As changes are made to the document, ensure that the Document Contributors, Revision History and Table of Contents (TOC) sections are updated

Purpose

Ownership

When

2009 Regents of the University of Minnesota. All rights reserved.

Page 1

SYSTEM/APPLICATION NAME

PROJECT CHARTER

accordingly. 6. Complete the attached Project Charter Review & Approval attachment per the provided instructions, listing all necessary reviewers, approvers and others who only require acknowledgement. 7. Upon receipt of the Review & Approval attachments, notify the reviewers and approvers of any critical requirements that will NOT be incorporated and the rationale. (Continued) Template Completion 8. Information within the Project Charter can be used to complete other subsequent documents, such as the Project Management Plan, Statement of Work (SOW), Business Requirements Document and MS Project schedule. 9. Once the Project Charter is completed and after the project has been closed, this document is to be retained with other project documentation in accordance with the records management policy and the business lines records schedule, storage and destruction requirements. As this template may change, it is highly recommended that you access a blank template from the Program Management Office website (http://www.uservices.umn.edu/pmo/) each time you need one for a new project and not merely use one from a previous project by changing the old text.

Important Notices

2009 Regents of the University of Minnesota. All rights reserved.

Page 2

SYSTEM/APPLICATION NAME

PROJECT CHARTER

DOCUMENT INFORMATION AND APPROVALSVERSION HISTORYVersion # 1.0 Date 9/17/09 Revised By Aaron Demenge Reason for change PMO Review

DOCUMENT APPROVALSApprover Name Project Role Signature/Electronic Approval Date

2009 Regents of the University of Minnesota. All rights reserved.

Page 3

SYSTEM/APPLICATION NAME

PROJECT CHARTER

TABLE OF CONTENTSProject Definition.............................................................................................................5Project Description..................................................................................................................................5 Project Objectives....................................................................................................................................5 Preliminary Scope...................................................................................................................................5 In Scope..............................................................................................................................................5 Out of Scope.......................................................................................................................................5 Uncertain............................................................................................................................................5 Project Deliverables.................................................................................................................................5 Known Risks/Assumptions/Dependencies..............................................................................................5 Critical Success Factors..........................................................................................................................6

Project Authorization - Charter Acceptance.................................................................6 Appendix A Project Resource Group Roles and Responsibilities .........................7Group Roles............................................................................................................................................7

Appendix B - Feasibility Study (if one is conducted)..................................................9

2009 Regents of the University of Minnesota. All rights reserved.

Page 1

SYSTEM/APPLICATION NAME

PROJECT CHARTER

PROJECT AUTHORITYEnter the name of the planned resource for each project role. Name Role Project Manager The role of the Project Manager is to own and drive the solution delivery process. The Project Manager mobilizes and uses the project team to complete the project successfully. He or she is responsible and accountable for the overall planning, execution and control of the project. Responsibilities Define the project management strategy and approach adhering to PMO guidelines and standards Provides guidance on the overall project with regard to scope, budget, schedule, quality, risks and issues. Liaison with business to ensure participation and ownership Plan, organize, and control the activities and resources of the project team and report on the teams progress Facilitates identifying and bringing closure to open issues while maintaining overall change control. Executive Sponsor The role of the Executive Sponsor is to be the champion of the project and to provide high-level vision and University-wide perspective. The Executive Sponsor has ultimate responsibility for the success of the project team in fulfilling its mission Business Sponsor The role of the Business Provides guidance and direction for key business strategies Prioritizes issues Resolves issues when escalation is required The key goal of this role is communication and mission/vision fulfillment Goal The key goal of this role is solution delivery within project constraints. The project manager is the person accountable for the project.

Provides funding Resolves business

The key goal of this role is business direction and customer satisfaction

2009 Regents of the University of Minnesota. All rights reserved.

Page 2

SYSTEM/APPLICATION NAME

PROJECT CHARTER

Name

Role Sponsor is to provide guidance and direction for key business strategies. The Business Sponsor answers the businessdriven question, "Why are we doing this?" and ensures that all members of the team know and understand the answer.

Responsibilities policy issues Resolves business issues or assists with issue resolution when escalation is required Business and Technical Sponsors are partners in decision making Business and Technical Sponsors will consult on issues before they are brought to the Executive Sponsor Provides Go/No Go authorization that product is ready for release as part of implementation planning and launch process.

Goal

Technical Sponsor The role of the Technical Sponsor is to provide technical support for system definition and implementation

Makes resources available Resolves technical issues or assists with issue resolution when escalation is required Business and Technical Sponsors are partners in decision making Provides Go/No Go authorization that product is ready for release as part of implementation planning