Growth:Adoption: Amplifying SaaS Reliability Focus for Q3FY22
This is the groupadoption specific issue for gitlab-com/Product#2881 (closed). The purpose is to provide a tracking and organization issue for surfacing the critical customer needs and opportunities to improve SaaS reliability for each group. Once collected, we can surface this back up to the main parent issue in a clear way.
Asks
See: gitlab-com/Product#2881 (closed)
- PM (@mkarampalas): Understand and share what are the minimal-must-do features/capabilities we should deliver to meet customer ARR commitments from 14.2 through 14.6
- EM (@pcalder): Understand and share What are the top most things you could advocate for to improve reliability of your areas. In addition to improving reliability, consider observability needs to detect and fix reliability issues when they do occur in SaaS
GUIDANCE
- Take a hard look at your particular area and see what you need to prioritize to prevent outages in SaaS from your area.
- Make sure your error budget is appropriate for your team
- Ensure corrective actions / infradev issues are prioritized to SLOs
- Connect with EM for high prio tech debt focused on SaaS reliability
- Ensure Eng allocation budget is enough to cover
- If 1 -3 exceed your team’s capacity for Q3, let Anoop and Scott know.
Edited by Michael Karampalas