Purpose (The Why): Throughout the lifecycle of the service, regular checks are required to ensure that onboarding tasks are progressing and that the team remains on track for launching the service. The Program Manager will create the overall ROMS checklist and dashboard prior to kick-off. Individual teams (e.g., SRE/CEE, Console.dot etc)  will have their own readiness checklists (linked to these higher level ROMS tasks). The program manager will track progress of checklists at program level and prior to GA will confirm sign-off from all stakeholder teams and completion of ROMS tasks. ** Note ** Streamlining of this process through automation is under review **

Responsible: The Program Manager is responsible for ensuring that high-level ROMS tasks are created and completed.  Each team is responsible for creating and maintaining their own checklists and readiness criteria.The Program Manager will work with the teams involved to ensure that sign-off is confirmed prior to GA

If I don't complete this task, what is the risk

You MUST complete this task to obtain sign off from the responsible teams before launching the service. 

Consulted: All stakeholders

Prerequisite/ Input: All teams have checklists in place, ROMS dashboard in place

Next task: Once Readiness is confirmed, the next stage is public launch

Dependencies: Completion of ROMS tasks for final readiness check. If a task is deemed not required then the reasons for this should be confirmed and a risk assessment carried out at program level

Deliverable/ Competition criteria:  Confirm sign/off from all stakeholder teams. Confirm ROMS tasks are complete. 

Expected duration/ effort: Progress checked weekly/on a regular basis throughout the lifecycle of the service.. Final checkpoint completed before GA/launch to confirm readiness. 

Supporting documentation/ Best Practices: 

Exception Process: This is a required task ** 

How to get help: 

Managed Services CoP GChat

ROMS Jira ticket

Before you close

• Update the Jira to confirm sign off from all teams 
• Link any associated documentation including risk logs, decision logs
• If risks have been accepted at launch stage you should include details