Write up initial team definitions - General
We need to write up the initial team definitions for when we move to a team model described in #158 (closed) to ensure team members understand the purpose of each team ahead of making any team allocations. We'll likely iterate heavily on these for the next 6-12 months.
Please create an MR for updating https://about.gitlab.com/handbook/engineering/infrastructure/team/reliability/#how-we-work--team-configuration using https://about.gitlab.com/handbook/engineering/starting-new-teams/#team-page-template as guide and include the following items:
- Mission (What is the team there to do)
- Boundaries (Describe which parts of the system are owned by this team, describe overlap with other teams (and what to do in the overlap) and describe parts that are explicitly not that team but could be perceived as theirs.)
- Performance Indicators (What are the signals this team is achieving its mission)
- Key technical skills (What technical skills are needed to be successful in this team)
- Common links (Include issue trackers, slack channels, etc)
At this time there is no need to describe:
- Team Members (We'll do that as part of team allocations at a later stage)
- Stable Counterparts (The team will define these if required when formed)
- How to work with us (The team will define that early in their inception)
- Hiring (We'll update these once we confirm our FY24 hiring plans)
As you're doing this exercise you'll likely come across areas that are falling between the cracks or you're unsure if we are covering them. Please capture those in either the associated issue for the team you think should be covering or in #164 (closed) for ones where you are unsure and we'll cover them later.
If anything is unclear tag @alanrichards in a message in #Reliability-Staff
and I'll help to clear it up.