Project approval process

Ownership Document
 




   Table of Contents

1.0   Roles 
1.1   AC Coordinator 
1.2   CTO Review 
1.3   Director of Catalyst Program 
1.4   Document Release Manager 
1.5   Program Management 
1.6   Subject Matter Expert 
1.7   Submitter 
1.8   SVP Member Collaboration 
1.9   TMF Staff Support Person 
2.0   Groups 
2.1   Approval Committee 
2.2   Project Team 
2.3   SPLC 
2.4   Technical Committee 
2.5   Technical Program Council 
2.6   The Membership 
2.7   TPC 


1.0   Roles

1.1  

AC Coordinator

Staff person supporting the Approval Committee and approval process


1.2  

CTO Review

On completion the Submitter 'presses the submit button'.  If the submission is for a non-Catalyst project CTO is notified of the project proposal submission.

The CTO has sole responsibility for reviewing project submissions. On completion of the submission form, the Submitter 'presses the submit button' and the CTO is notified of the project proposal submission. The CTO accesses the proposal and project plan online.

The CTO evaluates the proposal against the following criteria (examples):

Does the project support the TM Forum strategy?

Is the proposal already covered by an existing team?

Will the project deliver real benefits to the membership / industry?

Does the project have a reasonable chance of success?

Are the deliverables appropriate for the project?

Are the proposed deliverable dates appropriate?

Will the cost to the TM Forum justify the project?

The CTO may refer to the TPC, Technical Committee or other for guidance if they feel that they need further guidance.

Responsible CTO

Accountable V.P. Member Collaboration

Support SourceForge Support

Consulted Technical Committee, TPC

Informed Product Management, Program Management

Direct Responsibilities

Name Description Type
Approval CTO approves or rejects the charter Decision


1.3  

Director of Catalyst Program

The Catalyst Director has sole responsibility for reviewing Catalyst project submissions. On completion of the submission form, the Submitter 'presses the submit button' and the Catalyst Director is notified of the project proposal submission. They access the proposal and project plan online.

The Catalyst Director evaluates the proposal against the following criteria (examples):

Does the project support the TM Forum strategy?

Is the proposal already covered by an existing team?

Will the project deliver real benefits to the membership / industry?

Does the project have a reasonable chance of success?

Are the deliverables appropriate for the project?

Are the proposed deliverable dates appropriate?

Will the cost to the TM Forum justify the project?

The director may refer to the TPC, Technical Committee or other for guidance if they feel that they need further guidance.

Responsible Catalyst Program Director

Accountable V.P. Member Collaboration

Support SourceForge Support

Consulted Technical Committee, TPC

Informed Product Management, Program Management

Direct Responsibilities

Name Description Type
Approval CTO approves or rejects the charter Decision


1.4  

Document Release Manager

Responsible for processing and posting documents


1.5  

Program Management

The TM Forum central Program Management function monitors all projects against their milestones and provides a complete view of all projects and roadmaps.

Direct Responsibilities

Name Description Type
Approved Project The approved submission is made public as an approved project charter Activity
Approved Project Charter Approved project chater Controlled Document
Online Submission form The online submission form includes the necessary infortion necessary for the CTO to evaluate the proposal Controlled Document
Start Project Approval process Start Point


1.6  

Subject Matter Expert

Individuals with detailed knowledge in a specific domain area


1.7  

Submitter

Individual responsible for submitting the project proposal and may also be the project leader.

Direct Responsibilities

Name Description Type
Complete project proposal form Initiator completes the online project proposal form Activity
TMF413 Approvals Submission form Approval Committe Submission Form Requirement


1.8  

SVP Member Collaboration

Responsible for all collaboration activities including extending our reach through the value chain via our Sector Development activities.

Direct Responsibilities

Name Description Type
Project approval process Project
Project submission criteria A minimum set of criteria will control whether a project proposal is accpted for approval Controlled Document


1.9  

TMF Staff Support Person

Person assigned to assist a particular team




2.9   Groups

2.1  

Approval Committee

The Approval Committee is the operational body that approves technical work projects and the release of technical team deliverables to the membership or the public. It is comprised of selected members of the Technical and Operations Committees of the Board of Directors, the Service Provider Leadership Council (SPLC) and TM Forum technical staff. The Approval Committee is chaired by the TM Forum President.


2.2  

Project Team

The team established o approval of the project submission and responsible for devloping the deliverables.

Direct Responsibilities

Name Description Type
End Project Approval process End of Project Approval process Start Point
Project plan A project plan describing the key project dates is extracted from the project proposal Controlled Document


2.3  

SPLC

The Service Provider Leadership Council (SPLC) consists of a group of service providers from around the world who work together to create a unified voice for service providers’ needs from their OSS/BSS vendors.

The SPLC recommendations are used to drive TM Forum work, and as such drive development of industry standards for the telecom software community as a whole.


2.4  

Technical Committee

The chief duties of this committee are to develop the technical strategy for the TMF collaboration program. It also provides advice and guidance to the board, participates in the review and approval of project charters and documents as well as input to the Strategic Operating Plan.


2.5  

Technical Program Council

The TPC consists of representatives of all of the active project teams. Most projects are represented by the project leader


2.6  

The Membership

The great and vast mass which makes up the communications industry.


2.7  

TPC

The team leaders of all the standing technical teams are invited to join the Technical Program Steering Council. The objectives of the council are:

• To maintain an oversight of the overall progress of the technical program

• To help review project charters and technical documents prior to submission to the approvals committee

• To identify complimentary areas between programs which may help to accelerate work

• To identify possible areas where programs are creating duplication or divergent approaches from strategic TMF directions (such as NGOSS)

• To help in allocation of resources between projects where appropriate

• To help resolve conflict between teams and make recommendations to the technical committee/Approvals Committee

This team represents a broad constituency and have a good spread of technical knowledge. This team will get sight of project charters and technical documents so that comments and recommendations can be made to the approvals committee to help them in voting. The collated comments from the TPC and forward them to the Approvals Committee for their consideration

The council aims to

• meet by conference call once a month and at TAW to share progress in work and to discuss any points of conflict or overlap

have a significant impact on the direction of the TMF technical program