Project Charter Sample
Project Charter Sample
Project Charter Sample
Prepared for
Contoso, Ltd
Prepared by
Jonathan Haas, Proseware, Inc. Sr Project Manager
Proseware, Inc.
Table of Contents
1 INTRODUCTION ................................................................................................................................ 1
2 PROJECT SCOPE ................................................................................................................................ 2
BUSINESS OBJECTIVES .......................................................................................................................................... 2
PROJECT OBJECTIVES ............................................................................................................................................ 2
RELEASE 1 SCOPE ................................................................................................................................................ 2
PROJECT DEPENDENCIES........................................................................................................................................ 3
OUT OF SCOPE .................................................................................................................................................... 3
3 PROJECT GOVERNANCE MODEL ........................................................................................................ 5
KEY STAKEHOLDERS .............................................................................................................................................. 5
PROSEWARE, INC. ROLES AND RESPONSIBILITIES ........................................................................................................ 6
CONTOSO, LTD ROLES AND RESPONSIBILITIES ........................................................................................................... 7
PROJECT TEAM STRUCTURE ................................................................................................................................... 9
REPORTING....................................................................................................................................................... 10
COMMUNICATIONS ............................................................................................................................................ 11
4 PROJECT APPROACH ....................................................................................................................... 12
CONSTRAINTS AND ASSUMPTIONS ......................................................................................................................... 12
ISSUES AND RISKS .............................................................................................................................................. 12
HIGH-LEVEL SCHEDULE ....................................................................................................................................... 13
1. Increase Admissions staff productivity and drive consistency of Admissions staff performance.
2. Provide effective communications with the student through the student life cycle
3. Increase the weekly completed applications by 16% per ADA
4. Improve the application to start rate by 45%
5. Improve employee satisfaction by decreasing ramp up time by providing an intuitive easy to use
system
6. Improve the predictability and consistency of key business metrics
7. Improve data access for real-time access to management and monitoring
PROJECT OBJECTIVES
Release 1
1. Establish Microsoft Dynamics CRM as the system of record for Contoso, Ltd lead information
2. Design and implement a solution for the Contoso, Ltd Lead to Application new and re-entry student
processes using an integrated solution
3. Design and implement a solution for the Contoso, Ltd Application to Enrollment new processes
using an integrated solution
4. Integrate the solution with the existing Leads and Siebel applications
5. Test and deploy the integrated solution to the Contoso, Ltd user base
Release 2
1. Design and implement a solution for the Lead to Application new and re-entry student processes
using an integrated solution
2. Integrate the solution with the existing Leads and Siebel applications
3. Test and deploy the integrated solution to the user base
4. Design and implement dashboard reporting for the entire user base
RELEASE 1 SCOPE
2. Business Processes
a. Lead to Application Student processes
b. Application to Enrollment Student processes
c. New and Re Entry Student processes
PROJECT DEPENDENCIES
Migration of Contoso, Ltd student information system to Siebel is in progress and expected to be
completed by the end of May 2008. Contoso, Ltd will be responsible for ensuring cross project
communications take place to ensure there are no schedule impacts.
OUT OF SCOPE
1. Student Alumni processes are out of scope for both releases of the project
2. Future state business process definition or re-engineering beyond the processes impacted by the
Microsoft Dynamics CRM solution for Release 1 and 2
3. Microsoft Dynamics CRM Workflows or multiple sales processes and\or methodologies (except for
Lead to Enrollment)
4. Modifications to the core Microsoft Dynamics CRM SDK or coding/scripting on third party
applications
5. Integration or interface to any third-party or legacy systems the systems identified in the scope
section
6. Preparation/formatting, data cleansing, de-duplication and export of legacy data for the migration
to Proseware, Inc. provided template
11. Creation of end-user training collateral. Proseware, Inc. will provide a template to Contoso, Ltd who
will be responsible for customizing it for their needs.
13. Support documentation, as this comes with the Proseware, Inc. Microsoft Dynamics CRM 4.0
Software
15. Desktop, OS upgrades or service pack maintenance to meet minimum product operating
requirements
Rasmussen,
Morten Proseware, Inc. Engagement Manager
Executive Sponsors
Stakeholders
Hao, Junmin VP
Hanson, Mark VP
Solution Architect The Solution Architect is the primary resource for determining the approach
to be utilized in an implementation. The Solution Architect will also assist in
scoping and documenting customizations the project may require. The
Solution Architect should possess a thorough understanding of the product
from both a functional and technical perspective.
Application Consultant The Application/Functional Consultant will participate in every aspect of the
implementation from analyzing the customer’s business requirements to
configuring the Proseware, Inc. Microsoft Dynamics application to meet the
customer’s needs. The Application/Functional Consultant communicates with
the customer’s organization on many levels to obtain the necessary
understanding of the business processes.
Development The Development Consultant is responsible for the design and development
Consultant of modifications to the standard Proseware, Inc. Microsoft Dynamics
application.
Technology Consultant The Technology Consultant is tasked with solving issues that relate to
implementing Proseware, Inc. Microsoft Dynamics and related software in
the customer's current IT environment.
Executive Sponsor The Customer Executive Sponsor is a senior level executive who has accepted
ownership of investigating and investing in a business system initiative and
will promote funding and staffing of the project.
Business Decision Business Decision Makers are management level individuals within the
Maker customer's organization responsible for a specific aspect of the organizational
process that will be impacted by the implementation.
Customer Project The Customer Project Manager is responsible for ensuring all customer
Manager requirements are planned and executed in a manner that will meet the
implementation goals for the project.
QA Manager The QA Manager is responsible for managing and coordinating the Systems
and Integration Test, Performance Test and User Acceptance Test activities.
These activities include ensuring the availability of test users, test resources
and scheduling the test activities.
Key Users Key Users (or Subject Matter Experts) represent a functional area or
department within the customer organization, for example, marketing or
inside sales. They are typically a more experienced user who has in-depth
knowledge of the business processes and procedures currently being used in
their functional area or department.
End Users End Users are the individuals from various functional areas or departments
who will use the new solution to perform their daily activities.
PROJECT TEAM STRUCTURE
Executive Steering
Committee
(Contoso / Vendor)
Project Management
1
2 1
2
1 Business Owners
2 Key Users
Fitzmaurice, Mike
Frank, Jill
Development Consultant(s) Valverde, Eva Proseware, Inc.
Li, Yan
Czernek, Pawel
REPORTING
1. Proseware, Inc. team status reports from the Functional Lead and Technical Lead are due to the
Proseware, Inc. Project Manager by Thursday every week at 9:00am EST
2. Proseware, Inc. Project Status Report from Proseware, Inc. Project Manager due to Contoso, Ltd
Project Manager by Thursday every week at 4:00pm EST
3. Steering Committee Report from the Proseware, Inc. and Contoso, Ltd Project Managers due every
Friday at 10:00am EST
COMMUNICATIONS
1. Proseware, Inc. team internal status meeting will occur every Friday at 8:00am EST
2. Proseware, Inc. and Contoso, Ltd project status meeting will occur every Thursday at 03:00pm EST.
Meeting attendees will include all team leads and project leads.
3. Proseware, Inc. and Contoso, Ltd Steering Committee update will occur every Thursday at 01:00pm
EST
4. Phase Tollgate review meetings will be scheduled at the end of every phase completion
5. Change control board meetings will be scheduled on a weekly basis upon completion of the Design
phase
4 PROJECT APPROACH
Proseware, Inc. will leverage the Sure Step Methodology to execute this implementation. Sure Step
provides a structured approach to implementing Proseware, Inc. Microsoft Dynamics products. The Sure
Step Methodology provides detailed guidance on roles required to perform activities and proven best
practices. Flowchart diagrams within this implementation methodology point to tools and templates that
can be used at different phases of an implementation project.
Sure Step Methodology organizes the approach into five distinct phases during the implementation project
lifecycle
None identified
None identified
HIGH-LEVEL SCHEDULE
RELEASE ROADMAP
Contoso, Ltd
Release
2
Adm. V2 CM V2 Future
Release 2 Release 3
Contoso, Ltd
3
RELEASE 1 SCHEDULE
All dates are draft and to be finalized based on the project plan.