UNC General Administration
Intranet Project
Project Charter
Approved Version (1.0)
May 19, 2014
Table of Contents
Document Revision History 3
Purpose of Charter 3
Background and Opportunity 3
Goals, Objectives and Success Criteria 4
Project Scope 4
This section outlines the deliverables and features that will and will not be part of the UNC-GA Intranet Project. 4
In Scope 4
Out-of-Scope 5
Governance Structure & Stakeholders 5
High-Level Timeline and Milestones 12
Project Budget 15
Assumptions, Dependencies, Risks and Constraints 15
Status Reporting and Change Control 16
Document Repository 17
Date
|
Ver.
|
Description
|
Author
|
March 10, 2014
|
.01
|
Initial draft of project charter (leverages components of the UNC-GA Intranet Vision and Scope document prepared by Terri L. Amer)
|
M. Thorland
|
March 17, 2014
|
.02
|
Revised to reflect input from first Steering Committee meeting
|
M. Thorland
|
April 8, 2014
|
.03
|
Revised to include additional business/functional team members, as well as information pertaining to the document repository
|
M. Thorland
|
April 14, 2014
|
.04
|
Incorporated modifications resulting from 4/14 Steering Committee meeting (team members, potential constraints)
|
M. Thorland
|
April 14, 2014
|
.05
|
Removed dates in timeline that extend beyond June.
|
M. Thorland
|
May 14, 2014
|
.06
|
Included additional assumptions and scope items, adjusted timeline
|
M. Thorland
|
May 19, 2014
|
1.0
|
Approved version
|
M. Thorland
|
Purpose of Charter
The purpose of this Project Charter is to establish consensus on key aspects of the University of North Carolina (UNC) General Administration’s (UNC-GA) Intranet Project in advance of its implementation. The Project Charter serves as the organizational directive for the Intranet Project to exist. In its entirety, this Project Charter is a “scope” document. It establishes the boundaries for the project by defining specific goals and objectives, deliverables and a high-level timeline, as well establishing responsibilities for team members and procedures for how deliverables and changes will be approved. Once the Intranet Steering Committee approves the Project Charter, it will be designated as a “fixed baseline” and will be used as part of the change control process to judge the impact and potential value of any new or modified requirements. The Change Control section of this Project Charter provides details regarding the process.
|