Stabilize Uptime of Editor Experience #19397
Labels
CMS Team
CMS Product team that manages both editor exp and devops
Initiative
Initiatives are collections of epics that drive toward a common goal defined within Crew's Objective
Needs refining
Issue status
Problem Statement
There have been 4 times (source) over the last 3 months (from July - September 2024) that the editor experience (prod CMS) has been unavailable. Therefore, prod CMS' uptime fell to 99.786% in the last 3 months, which is below the industry standard of 99.9% uptime. To be in alignment with industry standard (99.9% uptime) and maintain trust with editors, how might me reduce the amount of times the editor experience goes down?
Business Outcomes
Hypothesis or Bet
How will this initiative impact the quality of VFS or Platform teams' work?
How will this initiative be easy for VFS or Platform teams? Or how will it be easier than what they did before?
We will know we're done when... ("Definition of Done")
Known Blockers/Dependencies
List any blockers or dependencies for this work to be completed
Projected Launch Date
Launch Checklist
Guidance (delete before posting)
This checklist is intended to be used to help answer, "is my Platform initiative ready for launch?". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given Platforminitiative. All links or explanations can be provided in Required Artifacts sections. The items that can be skipped are marked as such.
Keep in mind the distinction between Product and Initiative --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. VSP Product Terminology for details.
Is this service / tool / feature...
... tested?
... documented?
... measurable
When you're ready to launch...
Required Artifacts
Documentation
PRODUCT_NAME
: directory name used for your product documentationTesting
Measurement
TODOs
The text was updated successfully, but these errors were encountered: