Always Bright Project

  • December 2019
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Always Bright Project as PDF for free.

More details

  • Words: 1,100
  • Pages: 9
Company Logo

Always Bright

Project Charter

LG & E Address Louisville, KY Phone Number

Charter Approval

Project Name Project Charter Version xx.x

Logo

This document represents the approval and authority to begin the project and represents a consensus agreement from the participants about the goals, responsibilities, schedule, costs and product quality for the project.

Name Title Project Sponsor

Date

Name Title Business Owner

Date

Name Title Product Manager

Date

Name Title Project Manager

Date

Author: XXXXXXXX Company Name Address City, State Zip

Confidential

Date Page 2

Project Name Project Charter Version xx.x

Logo

Table of Contents Section

1.0

2.0

Description

Page

Charter Approval

1

Project Charter

3

1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18

x x x x x x x x x x x

Project Name Project Officers Purpose of Document Background Description Funding Approval and Amount Previous Efforts Goals and Objectives Scope and Deliverables Assumptions Constraints Project Risks Project Steering Committee Project Participants Project Stakeholders Estimated Milestones Estimated Cost Project Communications & Reporting

Attachments

x x x x x x x x

Document Control Version

Date

Author/Editor

Final

Author: XXXXXXXX Company Name Address City, State Zip

Confidential

Date Page 3

Project Name Project Charter Version xx.x

Logo

SECTION 1.0

PROJECT CHARTER

This section provides preliminary information used to charter the project. 1.1 Project Name. abbreviated to x. 1.2

The name of the project is x. The project name can be

Project Officers. The project officers are: • • • •

Project Sponsor: Business Owner: Project Manager: Product Manager:

1.3

Purpose of Document. The purpose of the project is:

1.4

Background. The background of the project …….

Many Kentucky residents lost power during and after the big storms. The trees or broken branches fell on the power lines because of either strong winds or ice. Residents themselves did not maintain trees or the tree branches, which caused the power outage. LG & E owns power lines and is responsible for maintaining the trees that could become potential points of power outage. 1.5

Description. The project can be described as x.

Always Bright Project is a series of activities that in a sum could provide continuous power to residents and businesses. Essentially, it is a framework to set up a system, which will proactively maintain power lines. 1.6 Funding Approval and Amount. Funding approval for the project was provided by xxxxx. The project has been funded for $x. The estimated capital cost is xxxxx. The estimated expense cost is xxxxxxxxx. 1.7

Previous Efforts. Previous efforts related to this project include: • •

Right tree in the right place (see PDF) It’s Time to Trim the Trees (see PDF)

Author: XXXXXXXX Company Name Address City, State Zip

Confidential

Date Page 4

Project Name Project Charter Version xx.x

Logo

1.8

Project Goals and Objectives. The goals and objectives of the project follow. Goals. The goals of the project include: • x Objectives. The objectives for each goal of the project include: • x

Author: XXXXXXXX Company Name Address City, State Zip

Confidential

Date Page 5

Project Name Project Charter Version xx.x

Logo

1.9

Scope and Deliverables. The scope and deliverables are: •

The estimated scope of the project does not include efforts for: •

x

1.10 Assumptions. Assumptions are conditions or factors that are understood to be in place during the project. Assumptions for the project include: •

x

1.11 Constraints. Constraints can affect the project or set a parameter for the project (e.g., budget, available resources, technology). Constraints for the project include: •

x

1.12 Project Risks. Risks are potential events that can positively or negatively affect a project if they occur. Identified risks for the project include: •

x

1.13 Project Governance Committee and Core Team. The Project Governance Committee and Core Team for this project consists of members who have the authority to approve project schedules, deliverables, budgets, change requests, and the recommendations from the project team. Their role will be to provide approvals and directions when needed. The members are shown on the following table. Steering Committee Member and Department/Area

1.14 Project Participants. The Project Participants will be directly responsible for performing the tasks or assigning the tasks to other resources to complete the project Author: XXXXXXXX Company Name Address City, State Zip

Confidential

Date Page 6

Project Name Project Charter Version xx.x

Logo

deliverables according to schedule. The Resource Assignments for the project are: Project Team

Department/ Area

Role

1.15 Project Stakeholders. The following individuals may be involved in the project. Their interests may be affected by the project execution and / or completion or they may influence the project and its results. Project participants are also considered project stakeholders and are included in the above list. The stakeholders list is used to identify individuals who will receive various communications about the project. Project Stakeholders

1.16

Department/Area

Estimated Milestones. The estimated major milestones for the project are: Activity

Estimated Completion Date

Business Case Project Charter Start Date Project Management Plan Work Breakdown Structure Analysis Design Implementation End Date Project Close Post-Project Review

Author: XXXXXXXX Company Name Address City, State Zip

Confidential

Date Page 7

Project Name Project Charter Version xx.x

Logo

1.17

Estimated Cost. The estimated costs of this project are: Items

Capital Costs

Expense Costs

Total Estimated Costs

DEVELOPMENT Hardware (servers and component) Software (name of software) Warranty and Annual Maintenance Software - Other (Additional server licenses, user licenses, etc.) Consultants Costs Consultants Travel Manpower - Internal (G&A) Manpower - IT Other Consultants Training (Materials) Other Expenses: Travel Hotel Food Auto Rentals Miscellaneous Total Estimated Project Cost Costs will be budgeted to x Department, and the job code for the project is x. 1.18 Project Communications and Reporting. guidelines follow: • • • • • •

Communications and reporting

Project meetings will be held biweekly beginning x Project reports from participants are due at the close of business every Friday Problems/issues should be reported to the Project Manager as they occur Documentation from deliverables will be distributed to the team for approval The Work Breakdown Structure is considered a work in progress The Project Management Plan and Work Breakdown Structure contain additional details regarding project communications and reporting

Author: XXXXXXXX Company Name Address City, State Zip

Confidential

Date Page 8

Project Name Project Charter Version xx.x

Logo

SECTION 2.0

ATTACHMENTS

The following is a list of attachments related to this Project Charter: • • • •

Work Breakdown Structure WBS Dictionary OBS Terminology Glossary

(Add any other document that is helpful and pertinent)

Author: XXXXXXXX Company Name Address City, State Zip

Confidential

Date Page 9

Related Documents

Always Bright Project
December 2019 5
Always
November 2019 40
Bright Star.docx
November 2019 30
Aqua Bright
June 2020 17
Bright Star
May 2020 16
Bright Water
June 2020 6