<Project Name> Charter

Transcription

1 < NOTE: Remove the italicized, bracketed guidance before routing for approvals. > General Information 1. Project Number: 2. Project Name: 3. Executive : 4. Business : 5. IT : 6. Project Manager/Lead: Executive Summary < Provide a brief overview of this project, objectives, and associated metrics. > Business Problem < State in specific terms the problem or issue this project will resolve. For example, does this project solve a problem, enhance a process, or support Churchill Downs Incorporated s Strategic Plan? > Business Objectives < Insert as many objectives and associated metrics/measurements as necessary. > 1. Objective 1: Associated metrics to measure current state and benefit realization. 2. Objective 2: Associated metrics to measure current state and benefit realization. 3. Objective 3: Associated metrics to measure current state and benefit realization. 4. Objective 4: Associated metrics to measure current state and benefit realization. Assumptions and Constraints < Insert all identified assumptions and constraints. Assumptions are factors that, for planning purposes, are considered to be true, real, or certain. Assumptions affect all aspects of project planning, and are part of the progressive elaboration of the project. Project teams frequently identify, document, and validate assumptions as part of their planning process. Assumptions generally involve a degree of risk. Constraints are applicable restrictions which will affect the scope, schedule, etc... > 1. Assumptions: a. Assumption 1 b. Assumption 2 2. Constraints: Define primary constraints by placing an X in the column that applies for each item. Add additional items if necessary. Page 1 of 5

2 Budget Human Resources Schedule Scope Not Flexible Somewhat Flexible Most Flexible Project Description, Scope and Major Milestones Description: < Describe the project approach, specific solution, customer(s), and benefits. > Scope: < The Project Scope defines all of the products and services provided by a project and identifies the limits of the project. In other words, the Project Scope establishes the boundaries of a project. > Major Milestones: < Provide a list of Project Management Milestones and Deliverables. This list of deliverables is not the same as the products and services provided, but are specific to management of the project. Examples are provided below. Insert Rows in the table as necessary. > Milestone 1. < WBS Baseline Complete > 2. < Testing Complete > Estimated Complete Date Project Authority 1. Projects are authorized by: 2. Authority to allocate resources: 3. Approval of project role descriptions and their associated responsibilities: Project Organization < Provide a hierarchal diagram of the project organization that begins with the Executive and includes the project team and other stakeholders. Describe the type of organization used (if external resources are necessary) for the project team, its makeup, and the lines of authority. > Resources / Funding < Identify the initial funding sources for capital, personnel, and other resources committed to this project by the project sponsor(s). Additional resources may be committed upon completion of the detailed project plan. > Benefit Realization & Measurement Page 2 of 5

3 < Define approximate benefit realization timelines for the objectives defined, the measurement methods, resources required for measurement, and the associated reporting required to validate/confirm benefit realization. > Risk Identification & Analysis < Define potential risks (preliminary assessment) and define their probability and potential impact on meeting the project objectives. > Risk Questionnaire (Note: This is not a comprehensive list of risk indicators.) 1. Are the project deliverables well defined and understood? 2. Are the business objectives fully defined? 3. Are major milestone dates flexible? 4. Has all project resources (human resources and equipment) been identified? 5. Are all impacted business units fully engaged? 6. Does IT have experience with the technology? 7. Will business processes, policies, and/or procedures require substantial change? 8. Are training resources defined for the end users? 9. Is there a business analyst familiar with the business processes assigned to the project team? 10. Are project budget and schedule well described and reasonable? 11. Are external dependencies (if present) fully defined? # Risk Description Probability Impact Note: Insert rows as necessary. This preliminary risk table will be the foundation for the project risk and issues log. Page 3 of 5

4 Role Artifact Business Case Charter Project Plan (WBS) Risk / Issues Log Change Control Log Acceptance Close-out Benefit Realization / Measurement Project Approval Authority Executive Business IT Project Manager / Lead Project Team PMO Vendor (s) Other < The RACI chart must be completed with specific names for each role prior to signatures. > R = Responsible: Owns the process and/or document; performs the task; responsibility can be shared A = Accountable: Accountable for task being complete; answers to executive sponsors and/or business and IT sponsors; approves documents, modifications, etc as necessary C = Consult: Has information and/or capability necessary to complete the work; communicated with prior to task being completed; may provide resources I = Inform: Notified of results, updates, modifications, etc Page 4 of 5

5 Approvals NOTE: s must update their Management Incentive Plans to reflect accountability for benefit realization. < Add approvals as necessary. > Project Manager / Lead IT Business Executive Page 5 of 5