Custom Writing Service http://StudyHub.vip/ANALYSIS-OF-PROJECT-CHARTER-PROJECT-MAN 👈

1. ANALYSIS OF
PROJECT CHARTER
PROJECT MANAGEMENT
By :
Nindy Aditya Dewi 18214052
INFORMATION SYSTEM AND TECHNOLOGY
INSTITUT TEKNOLOGI BANDUNG
2015

2. ANALYSIS OF PROJECT CHARTER
This Project Charter has several part. That are document revision history, purpose of charter,
background and opportunity, goals, objectives and success criteria, project scope, governance structure
and stakeholders, high-level timeline and milestones, project budget, assumptions, dependencies, risks
and constraints, status reporting and change control, and document repository.
DOCUMENT REVISION HISTORY
Document Revision History provide information on how the development and distribution of the
Project Charter up to the final point of approval was controlled and tracked. It provide the date of
version, the version number, the brief description of the reason for creating the revised version, and
the author implementing the version. From this document revision history, it can be seen that the
document of this project has been revised for six times, until the approved version published at May
19, 2014.
PURPOSE OF CHARTER
This part of project charter provide the purpose of project charter. The purpose of this Project
Charter is to establish consensus on key aspects of the University of North Carolina General
Ad i ist atio ’s (UNC-GA) Intranet Project in advance of its implementation. This project charter
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.
BACKGROUND AND OPPORTUNITY
Ba kg ou d a d Oppo tu it ’s pa t of this project charter provide the information about the
things underlying this project. The background of this project is the launching of UNC’s e a ped
external facing website on the Internet, and is now positioned to redesign its internal content to
support internal GA and UNC system-wide stakeholders. UNC-GA will take advantage of the opportunity
to design a new intranet using industry standard principles and best practices to create a user-centered
intranet.
GOALS, OBJECTIVES AND SUCCESS CRITERIA
This part of project charter tell us about the goals and objectives of the project. The goal of the
UNC-GA Intranet Project is to leverage a redesigned intranet site in order to provide a more efficient
communication channel between stakeholders, to increase the knowledge flow within the organization,

3. and to support operational processes that deliver business benefits. In support of this goal, there are
also some objectives like create user-centric intranet, redesigned intranet site to consolidate processes
and procedures, and make it single interface to organization application.
Furthermore, in this project charter also has been mentioned the success criteria of this project,
that are increased usage of intranet; intranet content is up-to-date, complete, and accurate; interactive
application work as intended; and criteria related to operational efficiency.
PROJECT SCOPE
Project scope provide the inclusive and exclusive boundaries of the project.
IN SCOPE (INCLUSIVE BOUNDARIES)
There are some inclusive boundaries that should be followed in this project. First, the intranet
will provide a vehicle for UNC-GA and campus stakeholders to communicate, collaborate and
disseminate information to internal GA and UNC system-wide stakeholders. The intranet will also
provide access to both unsecured content and secured content requiring Shibboleth federated
authentication. In this project, a consistent naming convention will be developed for content in order
to support efficient search capabilities for information on the intranet. Besides, the intranet will provide
mechanisms for collaboration, managing meetings and meeting materials, and presenting directories
and contact information for specialty groups. The intranet will also provide content owners with the
ability to easily modify content. After that, select operational processes will be redesigned in order to
automate them for the intranet and produce efficiencies. As required, the intranet will support current
features of the internal facing content currently housed on old.northcarolina.edu. And the last, a
support model will be developed to maintain the intranet on an ongoing basis
OUT-OF-SCOPE (EXCLUSIVE BOUNDARIES)
There are also some exclusive boundaries that should be noticed in this project. First, campus
processes that do not include a touch point/interface with UNC-GA are excluded from the scope of the
UNC-GA Intranet Project. Besides, the improving use s’ a ilit to sea h the UNC poli a ual o the
Internet is out-of-scope for the Intranet Project, and some online collaboration solutions include e-mail
integration to support meeting management. Replacing UNC-GA’s e isti g e-mail capabilities is not
within the scope of the Intranet Project.
GOVERNANCE STRUCTURE AND STAKEHOLDERS
This part of project charter shows the hierarchical structure of the governance and stakeholder.
The Intranet Project regards the entities and individuals reflected below as primary stakeholders.

4. Primary stakeholders are defined as individuals and groups that are content owners and users of the
intranet, and that play a key role in fulfilling the implementation of the Intranet Project. The
stakeholders that play roles here are Executive Sponsor, Executive Committee, Steering Committee,
Project Manager, Applications Development / Technical Team, Business / Functional Teams,
Co u i atio s, Se eta ’s Offi e, State Relatio s, Fede al Relatio s, Hu a Resou es, Fi a e,
Business Services, and Division of Compliance and Operational Efficiency. In addition, there are also
some roles of the stakeholders.
HIGH-LEVEL TIMELINE AND MILESTONES
In High-Level Timeline and Milestone, there is a draft timeline reflects the high-level milestones
and estimated timing for implementing the UNC-GA I t a et P oje t. I this p oje t ha te ’s ti eli e,
the ti eli e is filled just i Pla i g a d Busi ess Re ui e e t’s pa t. Planning was begined on
February 28, started from Establish governance structure. Then, the project would continue with
identify stakeholders and team members on March. On March 31, they would start to develop detailed
project plan will be updated throughout the passage of the project. April 30, 2014 was the planned date
to develop and approve Project Charter, and on August 28, they would like to develop and approve
intranet support/maintenance model. The development of communication plan for organizational roll-
out has been planned started from June.
For business requirement, they planned to develop business requirements framework on March.
Business requirements framework must be completed in advance of meetings with stakeholders. On
April until May, they would ike to define, document and approve business requirements.they would
prioritize business requirements on June.
For addition, dates beyond May will be determined upon the prioritization of business
requirements and sizing of the work effort, which is dependent on knowing which platform will be used
for the intranet.
Beside planning and business requirement, they also made time slot for design, business
development, IT development, deployment, and completion or maintenance. But in this project charter
the ha e ’t s heduled it.
PROJECT BUDGET
The detail p oje t udget as ’t itte i this p oje t ha te . I this ha ter just written to
establish and track a budget for any projected additional expenses associated with hardware, software,
new content, licensing, etc.

5. STATUS REPORTING AND CHANGE CONTROL
This part of project charter provide the information about status reporting of the project and
change controll process. Status reports will be produced and shared with the Intranet Project Steering
Committee in order to monitor progress and to ensure that the Intranet Project is delivered within
expectations. Change control documentation will be created to capture and manage any changes to
the p oje t’s aseli e s ope, s hedule o osts. The change control process is beginned with change
request is directed to Project Manager, then recommended change and rationale is documented. After
that impacts to the project are assessed, and then change and associated impacts are reviewed by the
Intranet Steering Committee, and as necessary, the Executive Committee, and either approved or
rejected. Next, project Charter is modified to reflect the agreed upon change, and the new version of
the Project Charter replaces previous versions. And the last, change is incorporated into the project plan
and implemented.
ASSUMPTIONS, DEPENDENCIES, RISKS AND CONSTRAINTS
This part of project charter provide about assumptions used, dependencies, risk of the project, and
constraint of the project. Assumption means identifies the statements believed to be true and from which a
conclusion was drawn to define this project charter. Assumption used there are the intranet will be designed
using its own branding and theme, and the internal facing content currently housed on
old.northcarolina.edu will be migrated based on content strategies developed in conjunction with each
stakeholder group that owns content. Constraint means identifies any limitation that must be taken into
consideration prior to the initiation of the project. The constraint in this project is the intranet will support
use of the Shibboleth federated identity and authentication process. One of dependency in this project is
the Intranet Project is dependent on the decisions made about content migration to the public website, and
the navigation links from the public website to content. And the risk of thisproject is the project does not
have an imposed end date; however, there is a desire to launch the intranet by late summer 2014.
Prioritizing and launching functionality in phases can mitigate this risk.
DOCUMENT REPOSITORY
This part of project charter provide information where project documentation will be stored. It
will be stored in the ActiveCollab project folder titled: GA Intranet Redesign, and could be accessed by
project team members using the given hyperlink.