Fast track request Sub Process

Process Narrative
 




Document Preferences 

Table of Contents

   1.0   Fast track request Sub Process
1.1   Start Fast track sub process
1.2   Assign to team
1.3   Plan & Schedule
1.4   Development Sub Process
1.5   Work Request Rationalisation sub-process
1.6   End Fast track sub-process


1.0  
Fast track request Sub Process

Fast track request Sub Process
Fast track request Sub Process

The fast track mechanism allows for the quick turn around for work requests which are straight forward in nature and/or are of an urgent nature.

Refer to the Fast Track Request sub-process for details.

Owner

Name Description Type
CR Manager Role


1.1   Start Fast track sub process 

1.2   Assign to team 

Work requests can only be fast tracked to a single team or an existing orchastrated set of teams which are currently working on 'the' or highly related activity.

The CR Manager presents the work request to the team giving an indication to the urgency & Priority of the item and the timeframe in which it should be implemented.  

The team does a final review and confirms that it is able to address the item in an agreed timeframe.  If not or if the work request does not belong within the team scope, then it is returned to the normal process.


1.3   Plan & Schedule 

1. The agreed urgency and priority is set against the work request. This is used to determine if the change is required for immediate implementation within a fix release or to be included in the next or a future release.  If work is required now, then the team charters are examined to determine if an ammendment is required.  If so, then all ammendments are made and approved prior to commecment of the work.

2. A scheduled delivery timeframe and release are agreed and a plan created using the provided tools as appropriate.  (e.g. Trackers, task manager etc. )

3. The request then enters the development process.

4.As a default the CR Manager manages the requested change though out the process.  However, It is intended that once assigned to a team, the Team Leader will take up ownership of the work request and reiodically, report progress back to the CCG.

Note: Once the change is implemented and verified by the implementing team,  it will enter the deliverable approval process - where the CCG as part of the expert reviewers team will verify that it has been implemented correctly.

Maturity Level will typically be a level 2 at this point.

Owner

Name Description Type
Team Leader Role


1.4   Development Sub Process 

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
SVP Collaboration Program Person heading up the Collaboration Program of the TM Forum. Role
Team Leaders Group Group


1.5   Work Request Rationalisation sub-process 

Within this sub-process the more complex work requests are put forward for initial assessment by the complete CCG and from here it will get routed down the most appropriate path. This could be to be deferred, rejected or continue on for further analysis/investigation, and assigned to the appropriate investigating body.  At this point the bulk of work requests will go for further assessment.

This phase should be completed by 2 weeks of request submission.

Maturity level of work requests at this phase would typically be of a level 1,  Request such as Fast track items, which would have completed their assessment phase would be upgraded to maturity level 2.

Refer to the Work Request Rationalisation Sub-process for complete details.

Owner

Name Description Type
CR Manager Role


1.6   End Fast track sub-process