Operations review - Creating Ops priorities & Scheduling support benefits use

**Describe the Issue**
With a double Sprint going into the New Year there is an opportunity to review what operational priorities will be the most important over the next quarter (up to end of fiscal)

**Additional Context**
This work should be in prep for an eventual/formal involvement of the AWS Enterprise Support 'Ops Review benefit', which will allow for an external review of our current platform Operations, as well as the addition of any further input on recommended platform Ops work, preparations and priorities

**Acceptance Criteria**
- Investigate latest operational best practices and technologies used for proper Governance and maintenance of the AWS Public Cloud for larger organizations
- Create a list of possible priorities around this and propose sequential draft
- Refine list with tech team and discuss most important items and details
- Present proposed priority list to Olena for further discussion and any refinement
- Refine again where necessary and complete a final Review with Pathfinder team
- This work should be ideally reviewed before the engagement of the formal AWS Enterprise Support 'Operations Review'
- This refined operational priorities work should be turned into team member tickets
.
.
.
.
.
.
.
.
.
.

**Extra Template Info**

***Definition of Ready***
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.

***Acceptance Criteria***
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for
- managing expectations
- defining scope
- reducing ambiguity
- establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

***Definition of Done***
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.
- Documented = Captured in Community Update (CU) deck
- Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU