Phase  Project Management

Project Name

Project Governance

Date

Author

PhaseProject Management

Table of Contents

Document Information

Terms and conditions

Distribution

Additional copies

Version history and status

Document history

Review history

Distribution of final document

Approval of final document

1.Introduction

1.1.Background

1.2.Governance Model

2.Introduction

2.1.Roles

2.1.1.PROJECT NAME Steering Committee

2.1.2.PROJECT NAME Core Team

2.1.3.PROJECT NAME Programme Team

2.1.4.Line of Business Steering Committee

2.2.PROJECT NAME Core Team Responsibilities

2.2.1.Program Manager

2.2.2.Architecture and Infrastructure

2.2.3.Meta Data

2.2.4.LoB Support

2.2.5.Company

2.2.6.Program Administration

Document Information

Terms and conditions

This document is strictly ‘Commercial in Confidence’ and is subject to the prevailing terms and conditions under which it is both written and distributed.

Distribution

Copies of this document are restricted to the following names:

Additional copies

Further copies of this document can be obtained from:

Version history and status

The current version is located in < location >

Versions other than the current one are archived in <location >

Version / Date / Revision history
0.1

Document history

Date / New version no. / Summary of changes

Review history

Date / Type / Reviewer

Distribution of final document

The following people are designated recipients of the final version of this document:

Name / Organisation

Approval of final document

These signatories confirm that this document will serve as the Project Name. This is not a static contract. Both the project manager(s) and sponsor(s) recognise that the content of this document will evolve throughout the Planning phase. The subsequent Project Plan Document will form the static project baseline.

Name / Signature / Date

1.Introduction

This document describes the:

  • Governance model for the Project Name Programme Team
  • Roles of the major areas within the Project Name Programme Team
  • Roles of the Line of Business Project Teams
  • Responsibilities of each of the positions within the Project Name Programme Team.

1.1.Background

1.2.Governance Model

2.Introduction

2.1.Roles

The following sections detail the roles of the:

  • Project Name Steering Committee
  • PROJECT NAME Core Team
  • PROJECT NAME Programme Team
  • Line of Business Steering Committees

2.1.1.PROJECT NAME Steering Committee

The role of the PROJECT NAME Steering committee is to:

  • Govern the direction of the PROJECT NAME Programme Team
  • Approve the introduction of PROJECT NAME infrastructure (hardware, software and applications)
  • Set Line of Business priorities
  • Ensure that the PROJECT NAME programme direction, infrastructure and applications fit within the overall Bank strategy for e-Business etc.

The PROJECT NAME Steering Committee will comprise the following:

  • Representatives from each of the business lines (the Content Working Group)
  • Representatives of relevant IT staff from the business lines
  • The PROJECT NAME Programme Manager
  • A member of the LoB Steering Committee.

2.1.2.PROJECT NAME Core Team

The role of the PROJECT NAME Programme Team is to:

  • Define the infrastructure required
  • Define the base set of meta data for the PROJECT NAME system.
  • Manage the relationship with the vendors
  • Manage outsourced resource
  • Provide governance over meta data defined and owned by the Lines of Business within the PROJECT NAME space.
  • Represent the PROJECT NAME Programme on the PROJECT NAME Steering Committee.
  • Provide planning for the roll-out of the infrastructure and assist in the roll-out of LoB applications.
  • Define and source staff/consultants for the PROJECT NAME programme team, including Perot Engineering etc.
  • Provide QA function to ensure consistency and fitness for purpose of LoB applications.
  • Represent the PROJECT NAME Programme on the LoB teams.

2.1.3.PROJECT NAME Programme Team

The role of the PROJECT NAME Programme Team (excluding the Core team) is to:

  • Provide consultancy to the LoB Projects
  • Develop the infrastructure for the PROJECT NAME Programme
  • Provide hardware engineering, network, operating system and database resource to the PROJECT NAME.
  • Provide consultancy to the LoBs.

2.1.4.Line of Business Steering Committee

The role of the LoB Steering Committee is to:

  • Govern the direction of the individual projects within the LoB.
  • Approve the introduction of PROJECT NAME infrastructure (hardware, software and applications) within the LoB.
  • Set priorities for implementation of solutions within the LoB.

A member of the LoB Project Team (chair or nominee) is represented on the LoB Project Representatives committee.

A member of the LoB support team will be co-opted into the project team to support the LoB Application development Team and to ensure minimum meta data standards are met and cross business line synergies are maximised.

2.2.PROJECT NAME Core Team Responsibilities

The following sections detail the responsibilities of the major positions within the PROJECT NAME Programme.

2.2.1.Program Manager

The Program Manager is responsible for the overall running of the PROJECT NAME Program, with specific responsibilities including:

  • Management of the PROJECT NAME Program Team
  • Ownership and control of Program Timelines
  • PROJECT NAME representative on the PROJECT NAME Steering Committee
  • Budget Control – in consultation and agreement with the PROJECT NAME Program Business Manager.

The Program Manager, as of 1/9/00 is NAME

2.2.2.Architecture and Infrastructure

Architecture and Infrastructure is the responsibility of the PROJECT NAME Program Chief Technology Officer (CTO) whose responsibilities include:

  • Physical and Logical design of the infrastructure.
  • Roll-out of infrastructure solution across the Bank.
  • Integration design between Product Name and Product Name.
  • Technical QA of Product Name and Product Name products.
  • Technical QA of the LoB applications before roll-out.
  • Main point of contact for all vendors relating to any technical issue relating to the PROJECT NAME Programme and interfaces to other projects or programmes that impact on the PROJECT NAME programme.

The CTO for the Program as of 1/9/00 is Name

2.2.3.Meta Data

Meta data design and governance forms one of the core strands of the PROJECT NAME program team structure. Without a consistent meta data structure cross functional re-use will be severely limited. This function is the responsibility of the Meta Data Manager, whose responsibilities include:

  • Management of the overall meta data definition process within the PROJECT NAME space.
  • Ensure consistency of meta data across business lines
  • Own core meta data attributes.
  • Manage any external consultancy used to define and manage meta data.

Meta data management within the PROJECT NAME Programme is the responsibility, as of 1/9/00 is Name.

2.2.4.LoB Support

The LoB Support team is provides a link between the PROJECT NAME Programme Team and each of the LoB application development teams. LoB Support responsibilities include:

  • Providing programme support to the LoB
  • Ensuring that Programme standards (QA and meta data) are met
  • Provide single point of contact between LoB Project and the PROJECT NAME Programme
  • Ensure requirements from LoB Project are fed back to the PROJECT NAME Programme (eg, capacity planning etc)

The LoB Support Team comprises, as of 1/9/00, Name

2.2.5.Company

Company support provides the link between the PROJECT NAME Programme Team and Company Engineering staff. Responsibilities include:

  • hardware procurement and roll-out
  • liaison with other areas of Company to ensure 24x7x365 availability of systems
  • capacity planning (with the CTO).

Company support is the responsibility, as of 19/9/00, of Name.

2.2.6.Program Administration

The Project Administrator is responsible for the following:

  • Providing initial point of contact for the PROJECT NAME programme team
  • Assisting in Budgetary reporting
  • Assisting in Project planning and reporting
  • Managing the PROJECT NAME Programme Web site

The Project Administrator, as of 1/12/00 is Name.

© 2002,

Wednesday, 16 April 2003; Page 1 of 8.