Task: Develop Project Charter
Work with the project stakeholders to define the project’s goals, objectives, and scope. The Project Charter documents the initial requirements that satisfy the stakeholder’s needs and expectations. In multi-phase projects, this process is used to validate or refine the decisions made during the previous iteration of the Project Charter.
Purpose
The Project Charter sets the overall direction and initial scope of the project as well as clearly defining the role of each project team member. It is critical to have it reviewed and approved before proceeding into the more detailed Project Planning stage. This review should occur within the established oversight venue for the project.
Relationships
InputsMandatory:
    		Optional:
    • None
    Outputs
      Main Description
      The Project Charter will describe the problem to be solved, the project goals and objectives, scope, assumptions, constraints, risks, and roles. It may also identify the key issues that can be used in the development of a Request for Proposal (RFP) for vendors, the review of a new process or product, and the initial setup of the project schedule.
      Steps
      Determine Output Format
      Obtain the current Project Charter Template to be clear on the required format and content.
      Collect and Review Available Documentation
      Review existing documentation such as the Initiative Request Form, KBICO Business Case presentation, vendor proposals, contracts and Concept Phase output to gain an understanding of, and to leverage, information gathered to date.
      Identify Stakeholders

      Meet with the Project Sponsor or his/her designee and identify the business stakeholders that will need to participate in the project. Identify the Project Owner who will have day to day decision making authority for the project.

      Meet with the appropriate Technology resources who have worked with the business partners, vendor(s) and other Technology teams prior to the project receiving approval for Initiation. Identify the Technology stakeholders.

      Define Problem Statement
      Describe the business reason(s) for initiating the project, specifically stating the business problem.
      Document Project Description
      Describe the approach the project will use to address the business problem.
      Determine Project Goals & Objectives
      Describe the business goals and objectives of the project. Refine the goals and objectives stated in the Business Case. The goals should be measurable and verifiable.
      Determine Project Scope
      Describe the project scope. The scope defines project limits and identifies the products and/or services delivered by the project. The scope establishes the boundaries of the project and should describe products and/or services that are outside of the project scope.
      Define Impact to Processes

      Describe any changes to the following processes:

      • Training
      • Change Control
      • Internal Notifications
      • Inter-Departmental Processes
      • Business Continuity Processes (BCP)
      • Data Backup and Recovery
      • Security
      • Other.
      Define Customer Impact
      Describe any known impacts to customers.
      Identify Critical Success Factors, Assumptions & Constraints
      Describe the factors or characteristics that are deemed critical to the success of a project, such that, in their absence the project will fail.

      Describe any project assumptions related to business, technology, resources, scope, expectations, or schedules.

      Describe any project constraints being imposed in areas such as schedule, budget, resources, products to be reused, technology to be employed, products to be acquired, and interfaces to other products. List the project constraints based on the current knowledge today
      Define Major Project Milestones
      List the project’s major milestones and deliverables and the planned completion dates for delivery. This list should reflect products and/or services delivered to the end user as well as the delivery of key project management or other project-related work products
      SOX Compliance
      Determine if this project has any SOX impact.
      Internal/External Risks
      List the project’s internal and external risks. This section should be filled out with help from Audit, Vendor and Information Security Risk and Information Security Technology.
      Define Project Organization

      Departmental impact

      List any impacts or specific deliverables for the following departments:

      • Financial Planning & Analysis
      • Commercial
      • Compliance
      • Enterprise Risk Management
      • Facilities
      • Finance
      • HR / Training
      • Internal Audit
      • Legal
      • Marketing
      • Retail
      • Strategic Sourcing
      • Technology
      • Other

      Project Structure

      Describe the organizational structure of the project team and stakeholders.
      Roles and Responsibilities
      Summarize roles and responsibilities for the project team and stakeholders identified in the project structure.
      Obtain Approvals
      Review the current list of Project Charter Approvers, identify the specific people who fill these roles for this project, and obtain their written or electronic approval.
      Key Considerations
      Gain agreement with the stakeholders regarding the objectives and duration of the project.
      Alternatives
      None.

      Version and Release

      Unified Life Cycle (ULC): 5.1, November 3, 2014
      Phase Gates: 1.1, May 27, 2014
      Process Engineering Process (PEP): 1.1, May 27, 2014