Project Charter Sample

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    1 Favorite

    Project Charter Sample - Presentation Transcript

    1. ENTERPRISE DATA WAREHOUSE Name of ProjectEDW Customer/Equipment Daily (CED) PROJECT CHARTER PMT ID: Prepared by: Orlando Moreno omoreno@hotmail.com 408.656.2498 Draft 0.2Baselined 1.0 Date:
    2. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: Page 2
    3. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: Table of Contents Enterprise Data Warehouse ........................................................................................................................ 1 WWWaWateWaWarehouse ........................................................................................................................ 1 High Level Project Description ........................................................................................................................ 7 Project Objectives ........................................................................................................................ 7 1.Business Problem .............................................................................................................................................................. 7 2.Project Objectives .............................................................................................................................................................. 7 Users ........................................................................................................................ 7 Client/Sponsor/Budget Information ........................................................................................................................ 7 Project Tracking Information ........................................................................................................................ 7 Source of Record IT Contacts ........................................................................................................................ 7 Project Scopes/Dependencies Page 3
    4. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: ........................................................................................................................ 7 1.In Scope .............................................................................................................................................................. 7 2.Out of Scope .............................................................................................................................................................. 7 Proposed Solution ........................................................................................................................ 7 1.Proposed Design Solution .............................................................................................................................................................. 7 2.Proposed Implementation Approach .............................................................................................................................................................. 8 3.Modeling .............................................................................................................................................................. 8 4.Metadata .............................................................................................................................................................. 8 5.Testing/Validation .............................................................................................................................................................. 8 6.Project Tracking and Oversighting .............................................................................................................................................................. 8 7.Project Related Publication/Reference .............................................................................................................................................................. 8 8.Communication Plan .............................................................................................................................................................. 8 Project Assumptions, Risks and Constraints ........................................................................................................................ 8 1.Assumptions .............................................................................................................................................................. 9 2.Risks .............................................................................................................................................................. 9 Page 4
    5. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: Related Projects Matrix ........................................................................................................................ 9 High Level Project Estimates ........................................................................................................................ 10 1.Resources and Hours Estimate .............................................................................................................................................................. 10 2.Teradata Capacity Estimate .............................................................................................................................................................. 11 High level Project Timeline* by Phase ........................................................................................................................ 12 KEY OPEN ISSUES ........................................................................................................................ 13 Attachment I - Organization, Responsibility and Resources ........................................................................................................................ 14 Attachment II - Project Change Management Plan ........................................................................................................................ 14 Introduction .............................................................................................................................................................. 14 The Change Management Process .............................................................................................................................................................. 14 Change Request .............................................................................................................................................................. 15 CMR Log Sheet .............................................................................................................................................................. 17 Attachment III - Project Issue Management Plan Page 5
    6. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: ........................................................................................................................ 17 Executive Summary .............................................................................................................................................................. 18 The Method and Procedures .............................................................................................................................................................. 18 Issue Management .............................................................................................................................................................. 18 Issue .............................................................................................................................................................. 18 Evaluation .............................................................................................................................................................. 18 Escalation Procedure .............................................................................................................................................................. 19 Document History ........................................................................................................................ 20 Page 6
    7. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: High Level Project Description Project Objectives 1. Business Problem 2. Project Objectives Users Client/Sponsor/Budget Information Client: Sponsor: Budget: ← Non-labor expense (Teradata space) – ← Labor expense for employees will be . Project Tracking Information EDW PMT ID: AIT INIT Code: Source of Record IT Contacts Project Scopes/Dependencies Merger – Cross Dependency 1. In Scope EDW Subject Area: 2. Out of Scope Proposed Solution 1. Proposed Design Solution • Tables - • Processes - Page 7
    8. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: 2. Proposed Implementation Approach 3. Modeling Note: This work effort will depend on the outcome of AIT Merger Project analysis that is currently underway. Fran MacDonald is coordinating the PM from AIT to work with this project team. The purpose is to evaluate if the integrated table structure will support this project. It is expected that decision will be made within two weeks. 4. Metadata 5. Testing/Validation 6. Project Tracking and Oversighting • This charter contains multiple work efforts for each subject area and each of the efforts has funding and approval and will be resourced and charged appropriately using available PMT ID in the Corporate CMPM time management tool. • Project Status Review meetings will be held regularly starting on. Team deliverables and timelines will be observed; issues and jeopardies discovered/discussed will be administered according to the communication plan defined in section 8. ← Frequency: BI-weekly status review during requirement phase. Weekly status review after requirements are completed ↑ Time - (PT)/ (CT).- (PT)/ (CT) → Kick-off Meeting - The team kick-off meeting will be held on (PT)/ (CT). 7. Project Related Publication/Reference A project control folder has been established on the EDW shared server to house project documents. All team members will have the accessibility to these documents. Primary communication vehicles are electronic mail and the project control folder. The EDW shared server is located at: prism01EDWprojectsCustomer Equipment Daily 8. Communication Plan ← Change Management Plan Provides procedures on how change to the project’s Charter, budget, schedule, and deliverables are processed. See Attachment II ↑ Issues Management Plan Provides Procedures for the timely identification and resolution of project level issues. See Attachment III. C:UsersomorenoAppDataLocalTempTemp1_Charter.zipIssue ManagementIssues Management Plan.doc Project Assumptions, Risks and Constraints Page 8
    9. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: 1. Assumptions 2. Risks Related Projects Matrix Dependent Projects (There are no dependent projects as of now unless we are required to build integrated tables as specified with the AIT Merger.) EDW Application Name Specs Contact Remarks Page 9
    10. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: High Level Project Estimates 1. Resources and Hours Estimate The EDW Project team for the ??? Project includes a Lead Architect, a Team Lead, a Project Manager, Data Specialists, a Data Quality Analyst, an Application Developer, a Lead DBA, a DBA, and a Modeler. Lead Architect The Lead Architect will have the major responsibility for approval of the architecture strategy for this project. Provides advice and guidance to the project team on the project implementation direction. Roles/Resources Task Estimated hours Project Manager- / Provide project charter, and project definition report Team Leader- Identify resources PM: ??? Perform project tracking and Oversighting function Team Leader: ??? Conduct a project team kick off meeting Conduct project status review meetings Manage escalations and jeopardy issues Maintain project schedule and monitor project progress SPOC for Client community As the Lead Data Specialist, the Team Leader also conducts design walk through Data Specialists: Provide Consultation on project deliverables, schedule DS –??? and design issues through out the SDLC DS – ??? Data Analysis Requirements Document Design Specs Develop test plans Support unit and system testing Conduct data validation Assist clients with end user acceptance testing. Data Modeler- Logical data model ??? (TBD) Document Metadata (Approx. Estimate. Modelers will modify the estimate as requirements are completed.) Data Quality Analyst – Data Analysis Reporting (Evoke, SAS frequency, ??? pattern analysis, etc) Assist test plans and data validation Developer: Extract program logic ??? Document Design Conduct unit and system testing. Make code changes where necessary Document SIA Schedule release into production. Page 10
    11. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: DBAs: Physical data model Lead Develop program logic for loading tables DBA ??? Document EDW Teradata Design DBA ??? Conduct unit and system testing. Make code changes where necessary Schedule release into production. Total ??? Note: estimate does not include time and cost for end user participation. 2. Teradata Capacity Estimate Currently, the T81A22_EQUIPMENT_EOM_CURR requires 88 gigabytes of storage capacity. It is estimated that the daily update table will require a minimum of 88 gigabytes (w/o fallback). The T82A08_CUSTOMER_EOM_CURR requires 8 gigabytes of EDW storage. It is estimated that the daily update tables would require a minimum of 8 gigabytes (w/o fallback). Detail: EDW Functional Areas Estimated Capacity W/Fallback PSOD T82A08_CUSTOMER_EOM_CU 8 gig 16 gig RR T81A22_EQUIPMENT_EOM_CU 88 gig 176 gig RR Reference Others Apps (ECM/Contact…) Total Page 11
    12. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: High level Project Timeline* by Phase TASK START DATE END DATE Project Duration 9/7/00 12/15/00 Requirements / 9/7/00 10/13/00 Validate if AIT structures will support CED project requirements Identify business rules for deriving daily updates to product and services Identify business rules for updating customer account data Create data acquisition design documents (ongoing) 9/7/00 12/1/003/30/00 Modeling 9/7/00 9/29/0010/19/00 Define data elements and definitions Create logical model (TBD- based on use of AIT integrated tables Design 10/13/00 11/3/00 Finalize design include plans for reconciliation, Program development / Coding 9/3010/23/00 11/8/0012/4/00 Build Prototype tables in EDW development Build program logic for updating billing account information Build program logic for updating product and services Unit test System Test Data validation and testing 11/8/0012/4/00 11/1512/15/01 Validate with requirements User acceptance Checkpoint revisit requirements / adjust program development 11/15/0012/15/00 11/30/002/2/01 Integration testing User acceptance testing Production Implementation 11/302/2/01 12/152/16/01 (Propose limited access view until Dec. journal processing in January ) Checkpoint – Client and EDW approval for GA Release 12/272/16/01 1/3/20012/28/01 EDW General Release 1/1/3/1/2001 1/13/1//2001 Project documentation complete: 12/153/1/01 1/30/20013/30/01 EDW Meta data , design documentation, logical model, physical model * This Timeline is subject to Change Page 12
    13. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: KEY OPEN ISSUES Issue # Originator Issue Description Possible Resolution(s) Issue Owner Targeted Due Actual Sataus Date Due Date 01 Page 13
    14. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: Attachment I - Organization, Responsibility and Resources Name Responsibility Area Telephone E-Mail Address Number Attachment II - Project Change Management Plan Introduction The purpose of this Change Management Plan is to have an organized approach with which to maintain control of changes during the project’s life cycle in order to minimize potential adverse impacts to the quality. This plan describes the process flow from change origination to completion, which will be used to manage change to the project schedule baseline. The following are the procedures when administer changes. The Change Management Process 1. Timing of Change Management The change management process is to start at the baseline of the schedule. The EDW project team must agree to deviations to the baseline, then and only then will the baseline schedule be revised and approved changes implemented. It is recognized that in order to be effective and to mitigate risk as much as possible, the change management process must be responsive. Because of this, team meetings will be called to consider all changes to the project baseline. If an emergency exists and decisions concerning change must be made on the fly, the request should be submitted to the team lead or the project manager as an emergency request to be decided on. 2. Process The following Flow Chart depicts the change management process scenario. The Change Request (CR) Form and the CMR log are included following the flow chart. •Authorized Change Process Page 14
    15. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: The requesting client functional organization project manager is responsible for preparing and issuing a Change Request (CR) to the EDW project manager. Once this is completed, the EDW project manager will perform initial preliminary impact analysis of the proposed change on time lines, budgets and other resources that could affect the baseline of the project. The EDW team lead will provide formal assessment result back to the requesting organization project manager. CR WORK PROCESS FLOW CHARTS C o m m u n it e C h a n g e D e s c r ip t io n / S t a t u s R e c o rd C h a n g e S ta tu s (E D W P M ) I m p a c t e d S u b je c t C hange R equest g e n e ra te s A re a P M (C R ) No S u b m it s C R P r e lim in a r y Im p le m e n t EDW A p p ro v e R e v ie w C h a n g e Y es C hange (T e a m L e a d /P M ) C hange? (E D W T e a m ) (E D W T e a m ) Change Request Page 15 Change Request Report Project Name: Customer/Equipment Daily Update Project ID: Prepared By : UUID/SBCUID: Phone #: Date Created: Document Version: Last Updated By: Last Date Updated: Page 15
    16. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: Change Raised By: _________________ Phone #: _________ Date Raised: _________ Change #: _______ Change Summary: Detailed Description: Project Manager/Work Effort Owner Initial Evaluation: Status: To be determined Type of Change: To be determined Priority: To be determined Target Date: ________ Evaluation Summary: Total Cost: Impact: Comments: Sub-Project/Work Effort Cost/Schedule Impacts and Comments Implementation: Status: To be determined Phase/Release: ______ Contract Change TBD Contract #: _______ Incorporated into plan by: __________________________ Implemented by: _______ Additional Implementation Detail: Approved By/Signed: _________________________________________________________________________ (print name here) Approved By/Signed: _________________________________________________________________________ (print name here) Page 16
    17. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: CMR Log Sheet Page 17 Change Request Log Project Name: Project ID: Prepared By: UUID/SBCUID: Phone #: Date Created: Document Version: Last Updated By: Last Date Updated: Change Summary Date Raised Status Type of Total Close Date # Change Cost 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. Attachment III - Project Issue Management Plan Page 17
    18. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: Executive Summary Definition – • An ISSUE is a circumstance or question that if left unresolved will most likely result in a risk event occurring. • ISSUE MANAGEMENT is the process concerned with identifying and resolving problems that affect a project and to minimize negative impacts. Objective - This document provides the method and procedures used to timely identify and to resolve issues that threaten the completion of tasks on the Customer/Equipment Daily Project Implementation timeline. The Method and Procedures At a high level, the process for managing issues can be illustrated as follows: Issue Management Issue Issue Issue Identification Issue Documentation Tracking and Reporting The process involves the following roles: • Originator: The person who initially identifies the issue. Any member of the project team can raise an issue • Owner: The person best equipped to determine the resolution to an issue from a content perspective based on knowledge, skills, and relationships will own the issue identified. In this project, the issue owner will be the person who owns the EDW subject area. • Facilitator: Acts as a process “quality gate” to ensure that complete and appropriate issues are being entered (i.e. documented). The PM/ the project team leader will perform this duty Issue identification Issue identification involves constantly monitoring the progress of the project in an effort to isolate those situations that negatively impact its progress. Issues can be identified at any time when they arise. Issue Evaluation Issue evaluation involves assessing its nature and impact. The purpose of evaluating an issue is to assist the team to prioritize the order in which issues will be resolved. All issues will be identified /evaluated /assigned ownership during the team status review meeting. Page 18
    19. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: Issue documentation All issues will be documented in an accurate and timely fashion so that they can be tracked and shared with team members. Following information will be documented once the meeting is adjourned: Id#: Numerical code representing the sequence of the issue. Originator: Person responsible for surfacing the issue Issue description: The description will capture the basic component needing res resolution. It should be descriptive enough so that any one reading the document can understand the issue. Possible Solution: Dated comments describing activity related to issue resolution. Each time status is obtained on the issue it should be documented here. This field should also contain the resolution decision. Owner: Person responsible for issue resolution. Targeted Due date: Date issue is targeted to be resolved Actual Due date: Date issue is actually being resolved Status: This should reflect whether the item is open or closed. If item is closed, the date should be listed here also. Issue tracking and reporting After the issue has been properly documented, regular status updates will be obtained at each team meeting or via email/telephone contact and documented in the project management folder on the shared server. The Team Lead/Project Manager will be responsible for working with the content owner to facilitate issue resolution and for ensuring that the issue log is updated with new status information. If at any point during the process, the project Team Lead/PM believes that an issue prevents work from moving forward, it will be escalated to the Upper Management. Escalation Procedure If an issue should require escalation to the upper management in order to be resolved, The PM will be responsible for the coordination of the escalation to the next level of management and for inclusion on the project open issue log. The Team Leader is to be included in the entire process. The Team leader will be responsible for reassess the timeline against deliverables with the assistance from the team. Page 19
    20. ENTERPRISE DATA WAREHOUSE Name of Project Project Charter Work Effort Name: PMT ID/INIT Code: Prepared By: Orlando Moreno UUID: ME1984 Phone: 408-656-2498 Date Created: Document Version: 1.0 Last Updated By: Orlando Moreno Date Updated: Document History DOCUMENT SECTION VERSION # BY DATE SYNOPSIS OF CHANGES ??? Project Charter Draft Initial outline for review. Timeline Draft Initial outline for review Page 11 – Key Open Draft 0.2 Added Key open issue for project Issues implementation. Timeline Baselined 1.0 Team Updated/Baselined Timeline Page 20
    SlideShare Zeitgeist 2009

    + Orlando MorenoOrlando Moreno Nominate

    custom

    1285 views, 1 favs, 0 embeds more stats

    This is a sample of the many project management doc more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 1285
      • 1285 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 0
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?