Governance Model For Project Server

Project Server Governance Model
Enterprise Service
Project Server
Functional Unit
Document Code
Description
Governance Model for Project Server
Edition & Date
26-Nov-15
Originator /
Prepared By
Bilal Farooq
Document Change Owner
Bilal Farooq
Hassan Farouk
Reviewed By
Document Owner
Bilal Farooq
Approved By
Muhammad Umer Shahbaz
First Edition
26-Nov-2015
First Draft
02-Dec-2015
Document Location
Distribution List
The master copy of this document is stored on an electronic database (Intelex) and is write-protected; it
can only be changed by the relevant identified personal. Copies cannot be printed. However any hard or
soft copy of this document is considered to be an uncontrolled copy used for reference only.
Technology Division, Telenor Pakistan
Page 1
Table of Contents
Table of Contents
Document Revision History ..........................................................................................................................3
Definitions ......................................................................................................................................................4
Purpose .........................................................................................................................................................4
Scope .............................................................................................................................................................4
Inputs, Outputs and Linked Processes ..........................................................................................................4
Tools ...............................................................................................................................................................4
Roles and Responsibilities ............................................................................................................................5
Document Owner / Process Owner............................................................................................................5
Document Change Owner ..........................................................................................................................5
Decision Making ............................................................................................................................................6
New Operational Request ..........................................................................................................................6
Boarding New Stakeholders Operational Request .....................................................................................6
Enabling of Project Server Features ...........................................................................................................6
Granting Access Rights ...............................................................................................................................6
Operating Procedures ...................................................................................................................................7
Follow Asia Harmony Process ....................................................................................................................7
Project Server Health Status Reports .........................................................................................................7
New Operational Requests.........................................................................................................................7
RACI Matrix ................................................................................................................................................7
Appendix .......................................................................................................................................................8
Appendix A .................................................................................................................................................8
Appendix B ...............................................................................................................................................10
Appendix C................................................................................................................................................12
This document is the property of Technology Division-Telenor Pakistan (Pvt.) Ltd. It may not be divulged to
organizations, divisions or persons outside the Technology Division /Telenor Pakistan without prior consent of
the relevant line management authority of Technology Division.
Page 2
1. Document Revision History

Sr.
No
Version
1.0
1.1
1.2
Change Description
First Draft
Updated By
Bilal Farooq
Review By
Hassan Farouk
Review
Date
2-Dec-2015
Important Note:
Only the Document Change Owner is authorized to update the Document

Revision History.
Any change in the document will be done by consensus (mutual agreement)

of stakeholders.
Page 3
2. Definitions
PD: Product Development
ES: Enterprise Services
EAO: Enterprise Application Operations
EPMO: Enterprise Project Management Office
SOR: Split of responsibility
RACI: RACI Matrix
Document Owner/Process Owner: ES Planning
Document Change Owner: ES Planning
3. Purpose
This document provides the guidelines and instructions to different teams in Telenor
Pakistan regarding governance of project server.
4. Scope
This document is applicable to for all stakeholders involved in governance of
Project Server as an Enterprise Service and users.
5. Inputs, Outputs & linked processes

Input: Understanding and Discussions with Stakeholders for Project Server
Governance.
Output: Governance Model for Project Server

Linked Processes: Asia Harmony Processes
6. Tools
Project Server
Page 4
Governance Model Project Server
7. Roles & Responsibilities
ES Planning
Responsible for upgrade (H/W and S/W), Planning, Change Requests,
Documentation and Capex handling
EAO
Responsible for operational management (Application Management,
Resolution of errors, uninterrupted availability of solution and implementation
of CRs as per direction of ES Planning) of Project Server, FLMs, daily Health
Checks, Escalations incase if issues persists after FLM.
EPMO / PD
Responsible for reporting of projects added in project server.
PM
Responsible for integrity of projects added in project server.
Users
Responsible for using project servers according to their access rights without
violating any company policy.
7.1 Document Owner/ Process Owner
To review the model periodically.
To identify any changes required in the governance model.
To help in documenting the changes and get them implemented.
To train the staff on the changes.
To communicate the changed version of document to stakeholders.
Page 5
7.2 Document Change Owner
Implement the changes in the governance model after receiving feedback

from concerned Stakeholder.
Get the governance model reviewed.
8. Decision making
Different types of decisions require different forms of approval. For example, proposing
project server to any department for use should be decided mutually by all stakeholders. This
section defines how certain actions will be performed, the types of approval, and which types
of decision require which type of approval.
8.1.
New Operational Requests
PD will raise request for any new operational request with the operations team.
Operations will guarantee the implementation of new operational request as per

their SLAs.
8.2.
Boarding New Stakeholder to Project Server
PD will decide and raise a request to ES Planning enable new department or

user to start using project server.
Whenever any stakeholder weather it is a department or user is brought on

board to start using project server, it will require approval of ES Planning.
Operations will ensure that nominated department / user is able to use the
project server once they are given access rights to project server.
8.3.
Enabling of Project Server Features
PD will raise request for enabling of new features of Project Server to ES

Planning.
ES Planning will evaluate the effects of enabling the feature and will give its
recommendations accordingly.
Operations will guarantee the implementation of new operational request as per

endorsements of ES Planning.
8.4.
Granting Access Rights
PD will raise request for granting access rights to any individual according to the
use access rights mentioned in Appendix C. Approval of Line Manager or
authorized authority will be required for granting access rights.
Operations will provide the access rights to the concerned stakeholder as per
endorsements of ES Planning.
Page 6
9. Operating Procedures
It is important that all the operating procedures follow certain processes finalized by Telenor
Pakistan.
9.1.
Follow Asia Harmony Processes.
It will be ensured by all stakeholders that processes laid out for our guidance in Asia
Harmony are followed in true spirit for all operating procedures related to project
server.
9.2.
Project Server Health Status Reports
Operations team will periodically share the health status report of project server with
ES Planning for future expansions and up gradations.
9.3.
New Operational Requests
New operational requests or change request will be raised on email with attachment of
respective forms see. Appendix A and B. Approval from line manager or authorized
authority of respective department will be required for every new operational request.
9.4.
RACI Matrix
Below mentioned
responsibilities.
is
the
RACI
Matrix
TASK(s)
which
EPMO
will
help
everyone
about
ES/OSS
Planning
ES/OSS Ops
Project Entry / Information ownership
Reporting
Handling Operational Issues in the Web App / Server
R/A
Configuration changes
R/A
Development on the Server / New Enhancements
R/A
the
Page 7
Appendix A
Change Request Form

Prepared By
Hassan Faruok
Approved By
Owner
ES Planning
Approval Date
10-10-2015
Revision
1.0
DOC#
NO_ES_001v02_Change Request
Revision History
Version
Author
Date
Comment
Page 8
Change Request Details

Change Title:
Customer/Requested By:
Name:
Date:
Required Change Description:
Requesting the Change Request conforms that the requesting department

will accept all the changes in the system due to the change request
implemented and will be responsible for the direct and indirect outcome and
behavior of the system/modules as the result of change request
implemented.
Change Request Approved and Accepted

Customer
Name:
Title:
Date:
ES Planning
Name:
Title:
Date:
Change Request Rejected

Customer
Name:
Title:
Date:
ES Planning
Name:
Title:
Date:
Page 9
Appendix B
New Operational Request Form

Prepared By
Bilal Farooq
Approved By
Owner
ES Planning
Approval Date
10-10-2015
Revision
1.0
DOC#
NO_ES_001v02_New Request
Revision History
Version
Author
Date
Comment
Page 10
New Operational Request Details

Change Title:
Customer/Requested By:
Name:
Date:
Operational Request Description:
Requesting the new operational Request conforms that the requesting

department will accept all the changes in the system due to the change
request implemented and will be responsible for the direct and indirect
outcome and behavior of the system/modules as the result of new request
implemented.
New Operational Request Approved and Accepted

Customer
Name:
Title:
Date:
ES Planning
Name:
Title:
Date:
New Operational Request Rejected

Customer
Name:
Title:
Date:
ES Planning
Name:
Title:
Date:
Page 11
Appendix C
Permission
Name
Access
Project
Server
Reporting
Service
Build Team
On New
Project
Can Be
Delegate
Change
Workflow
Clean Up
Project
Server
Database
Contribute to
Project Web
App
Edit Status
Report
Requests
Log On
Log on to
Project
Server from
Project
Professional
Manage
Active
Directory
Settings
Manage
Check-Ins
Manage
Cube
Building
Service
Manage
Drivers
Manage
Administrators
Portfolio
Managers
Portfolio
Viewers
Project
Managers
Resource
Managers
Team
Leads
Team
Members
Page 12
Enterprise
Calendars
Manage
Enterprise
Custom
Fields
Manage
Exchange
Integration
Manage
Gantt Chart
and
Grouping
Formats
Manage Lists
in Project
Web App
Manage My
Delegates
Manage My
Resource
Delegates
Manage
Notification
and
Reminders
Manage
Personal
Notifications
Manage
Portfolio
Analyses
Manage
Prioritizations
Manage
Project
Server
Backup
Manage
Project
Server
Restore
Manage
Project Web
App Views
Manage
Queue
Manage
Resource
Notifications
Page 13
Manage
Rules
Manage
Security
Manage
Server
Configuration
Manage
Server Events
Manage
SharePoint
Foundation
Manage Time
Reporting
and Financial
Periods
Manage Time
Tracking
Manage
Users and
Groups
Manage
Workflow
Project Detail
Pages
New Project
New
Resource
New Task
Assignment
Open Project
Template
Reassign
Task
Save
Enterprise
Global
Save Project
Template
Save
Unprotected
Baseline
Self-assign
Team Tasks
Status Broker
Permission
View
Approvals
View
Business
Page 14
Intelligence
Link
View OLAP
Data
View Project
Center
View Project
Schedule
Views
View Project
Timesheet
Line
Approvals
View
Resource
Availability
View
Resource
Center
View
Resource
Plan
View
Resource
Timesheet
View Task
Center
View Team
Builder
View
Timesheets
Page 15

Governance Model For Project Server

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Governance Model For Project Server

Uploaded by

Copyright:

Available Formats

Project Server Governance Model