Cost optimization planning & recommendations prep

[jon-mc-git]

Describe the Issue Cost optimization investigation and materials prep

Additional Context As part of the currently required AWS Cloud cost optimization efforts an analysis needed to be carried out by the team and information gathered and materials prepared as a base for a presentation and decision-making session with the Executive team

Acceptance Criteria

• Analysis of current costs associated with AWS Cloud Services usage so far with client and core infrastructure activity
• Discussion with team on results of initial review of costs
• Decisions on near-term cost management recommendations
• Organization of analysis and presentation by WS Enterprise Support on tenancy cost generating activity and recommended cost savings measures, both near and longer term
• Create base document\slide deck to use as framework for team Cost Optimization discussion & base material for a presentation to the Executive

. . . . . . . . . . .

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

[jon-mc-git]

This ticket is redundant to 2214 now so closing