About This Epic

The purpose of this Epic is to provide a Jira Template for tracking Service Team adoption of the Hybrid SRE model [V1]. The template contains an Epic with a list of Stories and Subtasks, one corresponding to each deliverable required for transitioning to Hybrid SRE.

Before You Get Started

• Reach out to the Service Delivery Strategy, Enablement + Architecture (SEA) team for an "Intro to Hybrid SRE" presentation to prepare your team to adopt the Hybrid SRE model. We can also help direct any questions that you might have as you kick off this process.

HyperShift

• What's this service: HyperShift is middleware for hosting OpenShift control planes at scale that solves for cost and time to provision, as well as portability across cloud service providers with strong separation of concerns between management and workloads. Clusters are fully compliant OpenShift Container Platform (OCP) clusters and are compatible with standard OCP and Kubernetes toolchains.
• Contacts: Product Manager azaalouk , Manager asegurap1@redhat.com , Engineering Lead agarcial@redhat.com

Guidelines for using this template

1. Clone this epic (And subtasks!) Into your teams Jira project. You must check the option to clone subtasks in the clone wizard or the subtasks will not be cloned. This template will be updated to keep up with any newer versions of this spreadsheet (Similar to ROMS).
   https://docs.google.com/spreadsheets/d/1z0dt9wQnXmwix8Yu49lt-iBkTvvLT7ZkVS-bsnZ1Izc/edit#gid=1273005524
2. Copy the Heat Map and On-Call participants sheets from the above Google Sheet as you will need to create versions for your team.
3. Update Summary, Epic Name, and Description with your service information.
4. Add any necessary labels based on your team's needs. Please do not remove any labels from the template – the SEA team will use these for tracking!
5. Walk through the template with your team (looping in your SnP liaison as you see fit) and assign the Jira tickets as appropriate.
6. Keep a record in the Jira ticket of what's been done before closing out.
7. If a decision was made to not complete a task, please comment on the reasoning and risk assessment carried out.
8. Service teams will be responsible for managing the Jira Epic/Stories/Tasks and keeping the status up to date, so that the SEA team can track progress via our Jira dashboard. The SEA team does not have someone allocated to manage or update Service Team work in Jira. 
9. Join the #wg-hybrid-sre Internal Red Hat Slack channel. This community is a good resource for questions and knowledge-gathering. 

Definitions:

• SEA - Strategic enablement and Architecture Group
• SnP Liason - Standards and Practices team member (an SRE in SEA) who works with each service team to accomplish their phased gates tasks.
• Service Team: The developers, Project Managers, BU representatives etc. Responsible for deliveing a managed service at Red Hat.
• Hybrid SRE Working Group - The subset of the service team + SEA + SRE who will ensure the tasks in the epic are complete (see: https://issues.redhat.com/browse/SEA-26)