Business Continuity Planning (BCP) (Public Cloud) - DevOps & Cloud Services

[garymatics]

Describe the Issue BCP is a component of the Office of the OCIO Business Continuity Management Program (BCMP). It provides a practical guide for staff working in the OCIO. Following a natural disaster or disruption to normal business, the BCP may be activated to coordinate the response to the event and recovery of OCIO business. There is a need for the CPF Team to update the DevOps & Cloud Services Branch BCP documents to ensure a planned response and recovery during a business disruption, thereby enabling the continuity of essential business processes.

Additional Context

*Acceptance Criteria

• DevOps & Cloud Services Branch team members responsible for updating BCP documents to meet to discuss shared responsibilities to develop/finalize BCP documents;
• Team members to connect with OCIO BCP Manager to discuss forms instructions & to become familiarized with BCP forms;
• Team members (Gary H. & Avneet K.) to discuss strategy to collaborate & divide tasks;
• Gary to collaborate with Jon & Warren to complete Business Impact Analysis (BIA) for public cloud;
• Gary to complete public cloud BCP;
• Team members (Gary H., Avneet K. & Nick C.) to connect to review/finalize public cloud & private cloud BCP templates;
• Templates to be competed by end of April; full BCP initiative be completed by June/July.

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

[garymatics]

Gary met with Avneet and Nick to discuss approach to working on BCP. Decision to produce two separate division BCPs: public cloud & private cloud. Gary to work on public cloud BCP; Avneet to work on private cloud BCP.