Work Request Capture and Rationalisation Sub Process

Process Narrative
 




Document Preferences 

Table of Contents

   1.0   Work Request Capture and Rationalisation Sub Process
1.1   Start Work Request capture & Rationalisation sub-process
1.2   Work Request Capture
1.3   Work Request Rationalisation sub-process
1.4   Work Request analysis & Assignment sub-process
1.5   End Work Request capture & Rationalisation sub-process


1.0  
Work Request Capture and Rationalisation Sub Process

Work Request Capture and Rationalisation Sub Process
Work Request Capture and Rationalisation Sub Process

New work and change requests may be captured from a number of different sources using a common on-line entry point, (http://www.tmforum.org/Community/groups/collaboration_program_center/changerequest.aspx) .  These work requests are brought together into a single, consolidated list, indicating a priority level. Thes eare then filtered and assigned to an appropriate working group.

By default items entered here will be of a Maturity level 0 (not set) or 1.

Refer to detailed 'Work Request capture and rationalisation' sub process for complete details.

Owner

Name Description Type
Change Control Group Group


1.1   Start Work Request capture & Rationalisation sub-process 

Work requests are captured, consolidated into a single stream and sanity checked.


1.2   Work Request Capture 

Work requests entered via the online form are automatically stored in a central repository. From here it is sanity checked by TM Forum staff and the appropriate Maturity level, (default 1) is set.  It is then assigned and forwarded to a CR Manager who will manage it through the remainder of its life.  

A quick pre-assessment is conducted by the CR Manager to ensure straightforward items can be addressed quickly and more complex ones are sent for more detailed analysis.  Approx 10% of the requests will complete its assessment at this phase of the process.

The duration of this phase should be a 1 to 2 days.

Maturity level for items in this phase would typically be of a level 1 (IPR and other sanity checks having been completed).

Refer to the Work Request sub-process for more details.

Owner

Name Description Type
CCG Admin Role


1.3   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.4   Work Request analysis & Assignment sub-process 

Within this phase, The stakeholders, (who could be a single person or a team of people depending on complexity of the request), review the work requests and provide an assessment, (which can be a single line in the requestor tracker or a detailed report - once again, depending on complexity of request), on their findings & recommendations. These return to the CCG where they are rejected or allocated to existing projects or a proposal to start the procedure to initate a new project.

Duration of this phase can take from 1 day to 3 months depending on completxity.

Once work request have completed their assessment, they will have progressed to a Maturity level 2.

Refer to the detailed 'Requirements Analysis and Assignment' Sub Process for complete details.

Owner

Name Description Type
Change Control Group Group


1.5   End Work Request capture & Rationalisation sub-process