governance model for project server

8/16/2019 Governance Model for Project Server

1/15

Technology Division, Telenor Pakistan Page 1

Project Server Governance Model

Enterprise Service Project Server

Functional Unit

Document Code

DescriptionGovernance Model for Project Server

Edition & Date 26-Nov-15

Originator /Prepared By Bilal Farooq

Document Change Owner Bilal Farooq

Reviewed ByHassan Farouk

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 ”; itcan only be changed by the relevant identified personal. Copies cannot be printed. However any hard orsoft copy of this document is considered to be an uncontrolled copy used for reference only.


2/15



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 toorganizations, divisions or persons outside the Technology Division /Telenor Pakistan without prior consent ofthe relevant line management authority of Technology Division.


3/15



1. Document Revision History

Sr.

No

Version Change Description Updated By Review By Review

Date 1 1.0 First Draft Bilal Farooq Hassan Farouk 2-Dec-2015

2 1.1

3 1.2

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.


4/15



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 TelenorPakistan regarding governance of project server.

4. Scope

This document is applicable to for all stakeholders involved in governance ofProject Server as an Enterprise Service and users.

5. Inputs, Outputs & linked processes

Input: Understanding and Discussions with Stakeholders for Project ServerGovernance.

Output: Governance Model for Project Server Linked Processes: Asia Harmony Processes

6. Tools

Project Server


5/15

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 implementationof CRs as per direction of ES Planning) of Project Server, FLMs, daily HealthChecks, 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 withoutviolating 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.


6/15



7.2 Document Change Owner

Implement the changes in the governance model after receiving feedbackfrom concerned Stakeholder.

Get the governance model reviewed.

8. Decision making

Different types of decisions require different forms of approval. For example, proposingproject server to any department for use should be decided mutually by all stakeholders. Thissection defines how certain actions will be performed, the types of approval, and which typesof 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 pertheir SLAs.

8.2. Boarding New Stakeholder to Project Server

PD will decide and raise a request to ES Planning enable new department oruser to start using project server.

Whenever any stakeholder weather it is a department or user is brought onboard to start using project server, it will require approval of ES Planning.

Operations will ensure that nominated department / user is able to use theproject 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 ESPlanning.

ES Planning will evaluate the effects of enabling the feature and will give itsrecommendations accordingly.

Operations will guarantee the implementation of new operational request as perendorsements of ES Planning.

8.4. Granting Access Rights

PD will raise request for granting access rights to any individual according to theuse access rights mentioned in Appendix C. Approval of Line Manager orauthorized authority will be required for granting access rights.

Operations will provide the access rights to the concerned stakeholder as perendorsements of ES Planning.


7/15



9. Operating Procedures

It is important that all the operating procedures follow certain processes finalized by TelenorPakistan.

9.1.

Follow Asia Harmony Processes.It will be ensured by all stakeholders that processes laid out for our guidance in AsiaHarmony are followed in true spirit for all operating procedures related to projectserver.

9.2. Project Server Health Status Reports

Operations team will periodically share the health status report of project server withES 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 ofrespective forms see. Appendix A and B. Approval from line manager or authorizedauthority of respective department will be required for every new operational request.

9.4. RACI Matrix

Below mentioned is the RACI Matrix which will help everyone about theresponsibilities.

TASK(s) EPMO ES/OSSPlanning ES/OSS Ops

Project Entry / Information ownership R

Reporting R

Handling Operational Issues in the Web App / Server I C R/A

Configuration changes I C R/A

Development on the Server / New Enhancements I R/A C


8/15



Appendix A

Change Request Form

Prepared By Approved By Owner Approval Date Revision DOC#Hassan Faruok ES Planning 10-10-2015 1.0 NO_ES_001v02_Change Request

Revision History

Version Author Date Comment


9/15



Change Request Details

Change Title:

Customer/Requested By:

Name:

Date:

Required Change Description:

Requesting the Change Request conforms that the requesting departmentwill accept all the changes in the system due to the change request

implemented and will be responsible for the direct and indirect outcome andbehavior of the system/modules as the result of change request

implemented.

Change Request Approved and Accepted

Customer ES Planning Name: Name:Title: Title:Date: Date:

Change Request Rejected



10/15



Appendix B

New Operational Request FormPrepared By Approved By Owner Approval Date Revision DOC#Bilal Farooq ES Planning 10-10-2015 1.0 NO_ES_001v02_New Request

Revision History

Version Author Date Comment


11/15



New Operational Request Details

Change Title:

Customer/Requested By:

Name:

Date:

Operational Request Description:

Requesting the new operational Request conforms that the requestingdepartment will accept all the changes in the system due to the changerequest implemented and will be responsible for the direct and indirect

outcome and behavior of the system/modules as the result of new requestimplemented.

New Operational Request Approved and Accepted


New Operational Request Rejected



12/15



Appendix C

PermissionName

Administrators PortfolioManagers

PortfolioViewers

ProjectManagers

ResourceManagers

TeamLeads

TeamMembers

AccessProjectServerReportingService

× × ×

Build TeamOn NewProject

× × × ×

Can BeDelegate

×

ChangeWorkflow

×

Clean UpProjectServerDatabase

×

Contribute toProject WebApp

× × × ×

Edit StatusReportRequests

× × × × × ×

Log On × × × × × × ×Log on toProjectServer fromProjectProfessional

× × × ×

ManageActive

DirectorySettings

×

ManageCheck-Ins

× ×

ManageCubeBuildingService

× ×

ManageDrivers

× × ×

Manage × ×


13/15



EnterpriseCalendarsManageEnterpriseCustomFields

× ×

ManageExchangeIntegration

×

ManageGantt ChartandGroupingFormats

×

Manage Listsin ProjectWeb App

× × × ×

Manage MyDelegates

× ×

Manage MyResourceDelegates

× ×

ManageNotificationandReminders

×

ManagePersonal

Notifications

× × × × × × ×

ManagePortfolioAnalyses

× × ×

ManagePrioritizations

× × ×

ManageProjectServerBackup

×

Manage

ProjectServerRestore

×

ManageProject WebApp Views

× ×

ManageQueue

×

ManageResourceNotifications

× × × × × ×


14/15



ManageRules

× ×

ManageSecurity

×

Manage

ServerConfiguration ×

ManageServer Events

×

ManageSharePointFoundation

×

Manage TimeReportingand FinancialPeriods

×

Manage TimeTracking ×

ManageUsers andGroups

×

ManageWorkflowProject DetailPages

×

New Project × × ×NewResource

× × ×

New TaskAssignment

× × × ×

Open ProjectTemplate

× × × ×

ReassignTask

× × ×

SaveEnterpriseGlobal

× × ×

Save ProjectTemplate

× × ×

SaveUnprotectedBaseline

× ×

Self-assignTeam Tasks

× × × × ×

Status BrokerPermission

×

ViewApprovals

× × × × × × ×

ViewBusiness

× × × ×


15/15


IntelligenceLinkView OLAPData

× × × ×

View Project

Center× × × × × × ×

View ProjectScheduleViews

× × × × × × ×

View ProjectTimesheetLineApprovals

× ×

ViewResourceAvailability

× × × × ×

ViewResourceCenter

× × × × ×

ViewResourcePlan

× × × × ×

ViewResourceTimesheet

×

View TaskCenter

× × × × × × ×

View TeamBuilder × × × ×ViewTimesheets

× × × × × × ×

governance model for project server

Documents