|
|
|
 |
 |
Process Overview |
Process Narrative |
|
This process document outlines the main processes related to the
Collaboration Program. Through the use of sub-process it will branch
into the various aspects.
In each case the 'Owner' for the sub-process and/or activity will be
identified. Required inputs and outputs of the sub-process/activity
will be document under the section titled 'Requirements' (limitation
placed by the tool). Finally, the 'Performed By' section will identify
the key stakeholders.
In addition to this document, it is strongly recommended that the
guideline document ‘ Using the Collaboration Workspace for Document
Release’ be referenced as it gives useful information as to how to use
the Collaboration workspace to assist with the document release process.
|
|
|
|
Process Overview |
Process Narrative |
|
New requirements may be captured from a number of different sources.
These requirements need to brought together into a single, consolidated
requirements stream with an agreed priority level.
Refer to detailed 'Requirements capture and rationalisation' sub process
for complete details.
Owner
 |
Name |
Description |
Type |
 |
Product manager
|
Manages the development and delivery of products
|
Role |
|
|
|
|
Process Overview |
Process Narrative |
|
The Project Approval sub-process describes the activities necessary for
the approval of a new project. A new project can take the form of 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 |
|
AC Coordinator
|
Staff person supporting the Approval Committee and approval process
|
Role |
|
|
|
 |
|
Process Overview |
Process Narrative |
|
During this phase of the project, the project team must operate within
the scope of the approved project charter and according to the TM Forum
by-laws and IPR rules as defined in the Operating Guide.
This section focuses on agreeing to the exact format of the
deliverables, creating the deliverables and ensuring initial quality
assurance is completed.
Refer to the detailed 'Development Phase' sub process for complete
details
Owner
|
Name |
Description |
Type |
|
Product manager
|
Manages the development and delivery of products
|
Role |
Requirements
|
Name |
Description |
Type |
 |
Approved Project charter
|
Project charter that has sucessfully completed the approval process and has been approved by the AC
|
Requirement |
|
Consolidated Requirements
|
Requirements collected from various sources are collected into a set of consolidated requirements
|
Requirement |
|
Project management report
|
Report against project plan and charter
|
Requirement |
|
Project plans
|
Detailed projects plans identifying deliverables and projected delivery dates
|
Requirement |
|
Roadmaps
|
User focussed roadmaps identify the furture funtionality for the product and projected delivery dates.
|
Requirement |
|
Team draft deliverables for approval
|
The team deliverables developed by the team in final draft form ready to be submitted to the AC for approval
|
Requirement |
|
TMF413 Approvals Submission form
|
Form to be submitted with any request for approval, charter or deliverable
|
Requirement |
|
|
|
|
Process Overview |
Process Narrative |
|
The purpose of this sub-process is to concentrate on the final phase of
the Technical Project Lifecycle – namely evaluation and release of the
project/Team deliverables. It is to clearly outline the various steps a
typical project will go through. Exceptions will be mentioned but not
addressed in any great detail.
Refer to the detailed 'Initial Deliverable Approval' Sub Process for
complete details.
Owner
|
Name |
Description |
Type |
|
AC Coordinator
|
Staff person supporting the Approval Committee and approval process
|
Role |
Requirements
|
Name |
Description |
Type |
|
Team draft deliverables for approval
|
The team deliverables developed by the team in final draft form ready to be submitted to the AC for approval
|
Requirement |
|
TMF413 Approvals Submission form
|
Form to be submitted with any request for approval, charter or deliverable
|
Requirement |
|
|
|
|
Process Overview |
Process Narrative |
|
This sub-process describes the process for reviewing deliverables
submitted for approval by the Approvals Committee.
Refer to the detailed 'Deliverable Review' Sub Process for complete
details.
|
|
|
|
Process Overview |
Process Narrative |
|
The process which is undertaken to achieve formal TM Forum Approval
status for a deliverable.
Refer to the detailed 'Formal TM Forum Approval' sub process for
complete details.
Owner
|
Name |
Description |
Type |
|
Product manager
|
Manages the development and delivery of products
|
Role |
Requirements
|
Name |
Description |
Type |
|
Approved Deliverables
|
Deliverables that have completed the approval process
|
Requirement |
Performed By
|
Name |
Description |
Type |
 |
Membership
|
The TM Forum membership
|
Group |
|
|
|
|
Process Overview |
Process Narrative |
|
Change Control Board (CCB) will provide a single body for the approval
of changes to the existing NGOSS baseline.
The NGOSS Change Control Board will report to the TMF Approvals Board
and is chartered with responsibility for ensuring that the change
control process as documented, is adhered to by the TMF Collaboration
Program.
In addition to the process description outlined here, CCB definition and
Terms of Reference are documented in the Word document Tech-07, Change
Control Board definitions and terms of reference.
Linked Resources
|
Name |
Description |
Type |
 |
|
|
Hyperlink |
|
|
|
|
Process Overview |
Process Narrative |
|
The CCB process starts with the receipt of a request by the CCB.
Registration and Initial assessment of the CR decides on the appropriate
process for the request.
Refer to the Receipt of CR Submission Sub process for complete details.
Owner
|
Name |
Description |
Type |
|
CCB Admin
|
|
Role |
Requirements
|
Name |
Description |
Type |
|
New Request for CCB
|
|
Requirement |
|
Request or Approvals Submission Form
|
|
Requirement |
|
|
|
|
Process Overview |
Process Narrative |
|
An NGOSS team, with a current approved charter, can submit NGOSS Base
Artifacts (NGOSS documents or models) to the CCB for approval.
Refer to the detailed 'Base Artifact Request' Sub process for more
details.
Owner
|
Name |
Description |
Type |
 |
CCB Chairperson
|
|
Role |
|
|
|
|
Process Overview |
Process Narrative |
|
To avoid spending a large amount of effort on many small changes, the
CCB, at its discretion, may vote to use a fast-track option for small
changes & corrections that have no expected wider impact, or Team
Submissions.
Refer to the 'Fast Track' Sub Process for complete details.
Owner
|
Name |
Description |
Type |
|
CCB Chairperson
|
|
Role |
|
|
|
|
Process Overview |
Process Narrative |
|
The process steps which the majority of Change Requests will follow.
Refer to the 'Normal CR' Sub process for complete details.
Owner
|
Name |
Description |
Type |
|
CCB Chairperson
|
|
Role |
|
|
|
|
|
|
|
|
