Вы находитесь на странице: 1из 8

<Project Name> Project Charter

Current Version:

Owner:

Date Last Updated:

Last Updated By:

Author:

Date Created:

Approved By:

Approval Date:

Revision History
Version Number Date Updated Revision Author Brief Description of Changes

Instructions: For the suggested topics below, replace <text within brackets> with project specific information. Some of the topics may not apply to all projects. In the topics where a response is optional, a choice, [N/A for this report] is included in the instructions.

<Project Name>

Project Charter Template Version 1.0

Doc. Version m.nn Page 2 of 8

< Generated Automatically. To update table based on changes in the document, select the table and hit F9. > 1 INTRODUCTION ....................................................................................................................................4 2 PROJECT SCOPE ..................................................................................................................................5 2.1 INITIAL PROJECT TEAM ........................................................................................................................5 2.2 MISSION STATEMENT...........................................................................................................................5 2.3 PROJECT OBJECTIVES .........................................................................................................................5 2.4 STAKEHOLDERS AND REQUIREMENTS PROVIDERS ........................................................................................5 2.5 PROJECT DEPENDENCIES ......................................................................................................................5 3 PROJECT MANAGEMENT STRATEGY.................................................................................................6 3.1 CONSTRAINTS , ASSUMPTIONS , EXCLUSIONS ..............................................................................................6 3.1.1 Constraints.................................................................................................................................6 3.1.2 Assumptions...............................................................................................................................6 3.1.3 Exclusions..................................................................................................................................6 3.1.4 Policies & Standards..................................................................................................................6 4 RECOMMENDED PROJECT STRATEGY .............................................................................................7 4.1 PROJECT STRATEGY ............................................................................................................................7 4.2 PROPOSED TECHNOLOGY ......................................................................................................................7 4.3 PROCESS CRITICAL SUCCESS FACTORS...................................................................................................7 4.4 BUSINESS VALUE...............................................................................................................................7 4.5 ORGANIZATIONAL CHANGE ISSUES..........................................................................................................7 5 SCHEDULE FOR PLAN PHASE.............................................................................................................8

Table of Contents

<Project Name>

Project Charter Template Version 1.0

Doc. Version m.nn Page 3 of 8

Introduction

[Purpose of this Section: Provide a brief introduction to the project. This is a summarization of the project history, project direction, and the work done in the Develop Process Design activity and reference to the Plan Tollgate]

<Project Name>

Project Charter Template Version 1.0

Doc. Version m.nn Page 4 of 8

2 Project Scope
[Purpose of this Section: Document in as specific terms as possible the factors which govern, limit and bound the project work necessary to satisfy the request.]

2.1

Initial Project Team

[Purpose of this Section: Provide a list of the members of the Project Team participating in Plan Phase activities. Indicate the business unit where they will work and their responsibilities to the project.]

2.2

Mission Statement

[Purpose of this Section: Provide a brief statement identifying the purpose of the project, and the goal that it is intended to meet. Reference the work done in the Clarify Goals task of the Develop Process Design activity.]

2.3

Project Objectives

[Purpose of this Section: Document the projects objectives identified in the Clarify Goals task of the Develop Process Design activity. Resolve any inconsistencies between Project Brief and Project Scope identified through current Project Objectives. Document the Project Scope exclusions here. Attach if required any Project Scope statements here.]

2.4

Stakeholders and Requirements Providers

[Purpose of this Section: Identify the organizational units and functions affecting and affected by the project. Identify potential individuals who will be targeted to provide requirements details about user functions, problems and needs. This information is developed in the Define Business Context Model task of the Develop Process Design activity. Stakeholders: Selected personnel representing Customers, End-Users, Developers, Testers, Deployment Team, Suppliers, Operations and Support Team, and others who are affected by the system or are accountable for the development of the system. Requirements Providers: Selected personnel representing Customers, End-Users, Developers, Testers, Deployment Team, Suppliers, Operations and Support Team, and others who provide requirements for the system being developed. Also identify the person among the identified requirements providers, who shall be responsible in resolving requirements conflict, if there are any while analyzing and managing requirements. This will avoid requirements misunderstanding and make validation of requirements easier. The identified requirement providers shall be required to approve requirements work products namely BRD, SRS before their baseline] Name of the Stakeholder John Smith Process Engineer Telephone Number Requirements Provider (Y/N) Responsibility
< Responsible to resolve the conflicting requirements>

Requirements Conflict Resolution Responsible Person: <Name of the Stakeholder from table above.> Criteria applied for resolution: < Criteria used to resolve the conflicting requirements>

2.5

Project Dependencies

[Purpose of this Section: Identify any existing systems or planned/in-process developments, which may affect or may be affected by the success of this project. An understanding of any related efforts is crucial to managing expectations and timetables.]

<Project Name>

Project Charter Template Version 1.0

Doc. Version m.nn Page 5 of 8

3 Project Management Strategy


[Purpose of this Section: Describe the Project management approach or a summary of other management plans for achieving Project deliverables.]

3.1

Constraints, Assumptions, Exclusions

[Purpose of this Section: Identify the constraints, assumptions and exclusions that exist for the project.] [Purpose of this Section: Identify the constraints, assumptions and exclusions that exist for the project.] [Purpose of this Section: Identify the constraints, assumptions and exclusions that exist for the project.] 3.1.1 Constraints [Purpose of this Section: Identify factors that will limit the Project Teams options and that options they must account for as they develop their solution. For example, a predefined budget is a constraint that is highly likely to limit the teams options regarding scope, staffing and schedule. Document other known constraints, such as using the Global Web Hosting environment for a web development.] [Purpose of this Section: Identify factors that will limit the Project Teams options and that options they must account for as they develop their solution. For example, a predefined budget is a constraint that is highly likely to limit the teams options regarding scope, staffing and schedule. Document other known constraints, such as using the Global Web Hosting environment for a web development.] [Purpose of this Section: Identify factors that will limit the Project Teams options and that options they must account for as they develop their solution. For example, a predefined budget is a constraint that is highly likely to limit the teams options regarding scope, staffing and schedule. Document other known constraints, such as using the Global Web Hosting environment for a web development.] 3.1.2 Assumptions [Purpose of this Section: Identify factors that, for planning purposes, will be considered to be true, real, or certain. For example, any resources assigned to the project will be assumed to remain with the project for the duration.] [Purpose of this Section: Identify factors that, for planning purposes, will be considered to be true, real, or certain. For example, any resources assigned to the project will be assumed to remain with the project for the duration.] [Purpose of this Section: Identify factors that, for planning purposes, will be considered to be true, real, or certain. For example, any resources assigned to the project will be assumed to remain with the project for the duration.] 3.1.3 Exclusions [Purpose of this Section: Identify products, services or processes that are not specifically a part of the project. Anything not explicitly included in the project deliverables is implicitly excluded from the project.] 3.1.4 Policies & Standards [Purpose of this Section: Identify all COMPANY XYZ and IS&S standards pertinent to this project.] The project will conform to all relevant COMPANY XYZ and IS&S policies and standards, including, but not limited to: COMPANY XYZ corporate Information Security Policy and Practices (ISP) Corporate Date Standards (CDS) IT Standards Process and Products Privacy Principles of Company XYZ Corporation

<Project Name>

Project Charter Template Version 1.0

Doc. Version m.nn Page 6 of 8

4 Recommended Project Strategy


[Purpose of this Section: Define the approach, which offers the greatest potential benefits. Factors to consider: what can be done to help achieve project objectives, what tools and techniques are available, and which tools and techniques seem best suited to the needs of this project. The key input to this section is the output from the Develop Process Design Activity.]

4.1

Project Strategy

[Purpose of this Section: Document the strategies identified in the Clarify Goals task of the Develop Process Design activity. Additionally document the implementation strategy as developed in the Perform Implementation & Process Management Planning task of the Develop Process Design activity.]

4.2

Proposed Technology

[Purpose of this Section: Document the IT Architecture vision, which states at a high-level, the technology that will be used to deliver a product solution for the project. This information is developed as part of the Develop To-Be Design task of the Develop Process Design Activity.]

4.3

Process Critical Success Factors

[Purpose of this Section: Document the Process Critical Success Factors (CSFs) identified in the Clarify Goals task of the Develop Process Design activity.]

4.4

Business Value

[Purpose of this Section: Document the business value as determined from the Perform Business Value Analysis task of the Develop Process Design activity. Attach the Business Case document if created by the Business Project Champion. Project Manager shall coordinate and provide details to Business Project Champion to create Business Case document for the Project.] [Purpose of this Section: Document the business value as determined from the Perform Business Value Analysis task of the Develop Process Design activity. Attach the Business Case document if created by the Business Project Champion. Project Manager shall coordinate and provide details to Business Project Champion to create Business Case document for the Project.]

4.5

Organizational Change Issues

[Purpose of this Section: Define all unresolved issues pertaining to organizational change that affect the project.]

<Project Name>

Project Charter Template Version 1.0

Doc. Version m.nn Page 7 of 8

5 Schedule for Plan Phase


[Purpose of this Section: Prepare the schedule for Plan Phase activities and more so for the Plan Tollgate Date. Estimation shall be done based on the Project Brief and Easy ROI. Basis for estimation should be typically the size estimates and the units of size. The units of size should be clearly documented. Document the assumptions used to arrive at the effort estimates]
# Activities Basis for the estimation Assumptions for Effort Estimates Effort (in person days) Planned Start Date Planned Finish Date

1. 2. 3. 4.

Develop Process Design Develop Project Charter Develop Plan for Define Phase Plan Phase Tollgate

<Project Name>

Project Charter Template Version 1.0

Doc. Version m.nn Page 8 of 8