Project Approval Sub-Process

Process Narrative
 




Document Preferences 

Table of Contents

   1.0   Project Approval Sub-Process
1.1   Start Project Approval Sub-Process
1.2   Create Charter Approval Submission
1.3   On-line submission form
1.4   Distribute for expert review
1.5   Collate Review Comments
1.6   Charter Type
1.7   Approval Decision
1.8   Approval Result
1.9   Process, post & include in roadmap
1.10   Roadmap
1.11   Posted Charter Details
1.12   Director of Demonstration Projects
1.13   Submitter/Requestor
1.14   Program Management
1.15   TM Forum Membership
1.16   Document Release Manager
1.17   SVP Collaboration Program
1.18   Expert Reviewer(s)
1.19   Technical Committee
1.20   End Project Approval sub process


1.0  
Project Approval Sub-Process

Project Approval Sub-Process
Project Approval Sub-Process

The Project Approval sub-process describes the activities necessary for the approval of a new project.  A new project could require a new team or a new phase of an existing team.

Refer to the detailed 'Project Approval Sub-process' for complete details.

Owner

Name Description Type
SVP Collaboration Program Person heading up the Collaboration Program of the TM Forum. Role


1.1   Start Project Approval Sub-Process 

1.2   Create Charter Approval Submission 

Team agree the contents of their charter, in particular the deliverable list and scheduled dates.  

Assigned team member, (usually the Team Leader) completes the charter template (TMF405) and stores in a working folder of the documents tab of their project workspace.  

Once the charter it ready, the document needs to be moved (via Cut & Paste) into the Submitted documents folder of the document tab, and a project charter submission request generated.  

This is done by creating a new artifact in the 'Project Charter Submission' Tracker, a link is available from the communities and completing the required fields. The charter document and request submission are linked together via the associations tab. Once saved, the request is automatically routed into the approval process.

Guidelines on how to complete the charter are available in the template with optional sections clearly identified.

Guidelines on how to create a Project Charter Submission entry within the tracker are available via the community/tool.

Owner

Name Description Type
Team Leader Role

Performed By

Name Description Type
Submitter/Requestor Person or team who have submitted the request. Role


1.3   On-line submission form 

1.4   Distribute for expert review 

The submission is taken, usually by the CP Program Manager and the appropriate review and approval dates are set.  Expert reviewers are notified by means of the contacts facitlity via the community and through the on-line reports which are available.

Expert reviewer have 1 week in which to review and return any comments & suggestions they may have.  All comments are to be entered directly into the system by:

  1. select the link (either in the Artifact ID or Title column) to open up the entry on the screen.

  2. Then provide any feedback into the ‘comment box’ to the left of the displayed screen,

  3. ( Attachements can also be included in the field underneath. )

  4. and select the ‘update’ button.


1.5   Collate Review Comments 

As all comments should have been entered directly into the charter submission, they will be automatically accessible from the history of 'comments' section of the artifact entry.


1.6   Charter Type 

There are two types of charters - one for demonstration projects and then, all the others.

Incoming Links

Name Description Link Label
Collate Review Comments All comments related to a charter submission are gathered together

Outgoing Links

Name Description Decision
Director of Demonstration Projects Person heading up the Demonstration Progam area. Catalyst
SVP Collaboration Program Person heading up the Collaboration Program of the TM Forum. All charters


1.7   Approval Decision 

The submitted charter is reviewed and all returned 'expert review comments' are considered.

In the Event of a Catalyst Project the approving party is made up of the Director of Demonstration projects and the SVP of Collaboration Program.  

For all other charters the approval decision is made by the SVP of Collaboration Program.

Approvers are given 3 days from end of expert review period to make their decision.


1.8   Approval Result 

Is charter approved for implementation or not

Incoming Links

Name Description Link Label
Approval Decision Approving parties review charter & returned comments and makes decision. result

Outgoing Links

Name Description Decision
Submitter/Requestor Person or team who have submitted the request. reject (email )
Process, post & include in roadmap Final processing of a charter after approval received Approved


1.9   Process, post & include in roadmap 

The approving team updates the charter entry with the results of their decision and enters any comments or actions they may have.  The entry is then routed back to the Program Manager for final processing.

The charter details are incorporated into the overall CP roadmap and tracked by the Program manager and will ensure that the approved charter is made available to the membership


1.10   Roadmap 

This is the complete roadmap for the Collaboration Program and is available from: http://collab.tmforum.org/sf/go/doc3395?nav=1


1.11   Posted Charter Details 

The final charter document which will be posted on the TM Forum web page, (www.tmforum.org), displaying from the Charter section of the document library and the particualar team area.


1.12   Director of Demonstration Projects 

Person heading up the Demonstration Progam area.


1.13   Submitter/Requestor 

This is a generic role to deplict the person or team who has submitted the request for modification or for approval, which ever is appropriate.


1.14   Program Management 

Person who manages and maintains the Collaboration Program roadmap.


1.15   TM Forum Membership 

Members of the TM Forum


1.16   Document Release Manager 

Person in charge of the final processing & posting of the charters or other deliverables.


1.17   SVP Collaboration Program 

Person heading up the Collaboration Program of the TM Forum.


1.18   Expert Reviewer(s) 

This role is generally held by the Team Leaders Group, Change Control Group, Service Provider Leadership Council and the various Sector heads.


1.19   Technical Committee 

The chief duties of this committee are to develop the strategic plan in collaboration with the members. It also provides advice and guidance to the board, participates in the review and approval of project charters and deliverables as well as input to the Strategic Operating Plan


1.20   End Project Approval sub process 

end of the project approval sub process.