From 2991e08ecc102ba50699cbaa958667448a243646 Mon Sep 17 00:00:00 2001
From: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com>
Date: Mon, 4 Mar 2024 16:53:54 -0600
Subject: [PATCH] Update product-design.rituals.yml (#17327)

Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
---
 handbook/product-design/README.md             | 29 ---------
 .../product-design/product-design.rituals.yml | 64 +++++++++++++++++++
 2 files changed, 64 insertions(+), 29 deletions(-)

diff --git a/handbook/product-design/README.md b/handbook/product-design/README.md
index 5d09c497d4..21e61fe871 100644
--- a/handbook/product-design/README.md
+++ b/handbook/product-design/README.md
@@ -185,35 +185,6 @@ Some of the data is forwarded to [Datadog](https://us5.datadoghq.com/dashboard/7
 ## Rituals
 <rituals :rituals="rituals['handbook/product-design/product-design.rituals.yml']"></rituals>
 
-<!-- TODO: Transfer to yaml 
-Directly Responsible Individuals (DRI) engage in the ritual(s) below at the frequency specified.
-
-| Ritual                       | Frequency                | Description                                         | DRI               |
-|:-----------------------------|:-------------------------|:----------------------------------------------------|-------------------|
-| Design sprint review | Sprintly (Thursday) | After the last estimation session, the Head of Product Design reviews the board with each group designer and de-prioritizes all design issues that were not estimated. The Head of Product Design also collects all items that are product-driven and puts them in the 🎁🗣 Feature fest meeting agenda to consider for continuing work. The number of de-prioritized issues should be recorded in the KPI spreadsheet. | Noah Talerman |
-| 🎁 Feature fest prep | Sprintly (Thursday) | The Head of Product Design reviews the agenda and pre-comments on items in order to be well-prepared for the discussion. | Noah Talerman |
-| 🎁🗣 Feature fest  | Sprintly (Thursday) | We make a decision regarding which customer and community feature requests can be committed to in the next six weeks. We create issues for any requests that don't already have one. | Noah Talerman |
-| 🎁 Feature fest cleanup | Sprintly (Thursday) | Clean up the agenda in anticipation of the next meeting | Noah Talerman |
-| Design sprint kickoff | Sprintly (Friday) | The Head of Product Design introduces and determines the order of the newly prioritized list of work with each group designer | Noah Talerman |
-| 🗣 Product office hours  | Weekly (Tuesday) | Ask questions to the product team | Noah Talerman |
-| Sprint kickoff review | Sprintly (Monday) | After each sprint kickoff, the Head of Product Design reviews the Estimated column with each group EM and de-prioritizes the features that were not included in the sprint and prepares recommended highlights for the release notes. The number of de-prioritized issues should be recorded in the KPI spreadsheet. | Noah Talerman |
-| 🦢🗣 Design review (#g-mdm)  | Daily | Review designs from the MDM team | Marko Lisica |
-| 🦢🗣 Design review (#g-endpoint-ops)   | Daily | Review designs from the Endpoint ops team | Rachael Shaw |
-| Product development process review | Sprintly | CEO, Director of Product Development, and Head of Product get together to review boards and process to make sure everything still makes sense | Noah Talerman |
-| Maintenance | Weekly (Friday) | Head of Product Design checks the latest versions of relevant platforms, updates the maintenance tracker, and notifies the #help-product-design Slack channel. | Noah Talerman |
-| Quality check  | Daily         | Every day, Head of Product design will review the "Settled" column on the drafting board to ensure all product action items are complete.                                | Noah Talerman |
-| Product confirm and celebrate                 | Weekly (Wednesday)       | The Head of Product meets with the designers and product managers to discuss completed user stories. They also verify all updates to documentation, communications, guides, and the pricing and transparency pages, ensuring everything is set for the next steps.                                      | Noah Talerman            |
-| Pre-sprint prioritization          | Sprintly (Monday)        | The Head of Product Design and each group's EM meet before each sprint to align on priorities and discuss what stories weren't completed in the previous sprint. Head of Product Design records number of stories that weren't completed in the "Stories dropped" product KPI.                                                                                                                                                              | Noah Talerman            |
-| Bug round-up   | Mid-sprint | Head of Product Design will compile a list of churned bugs, including issue numbers, specifics, and age. They will also notify the Customer Success team of any churned bugs that have customer tags  | Noah Talerman |
-| Churned bug review                            | Mid-sprint     | The Head of Product Design meets with the Head of Product Development to examine churned bugs and categorize them as either schedule, needs prioritization, or de-prioritize.                                                                    | Churned bug clean-up | Mid-sprint  | Following the churned bug review, Head of Product Design completes the churned bug clean-up, ensuring all necessary follow-up tasks are actioned to classify bugs as schedule, needs prioritization, or de-prioritized. This may include relocating bug tickets, adjusting labels, communicating with stakeholders, writing documentation, and closing issues. | Noah Talerman |                                                                 | Noah Talerman            |
-| Stand-up (#g-digital-experience)           | Daily (Monday - Thursday) | The Digital Experience team meets to discuss completed tasks, upcoming work, and address any questions. | Mike Thomas |
-| Prioritization session (#g-digital-experience) | Sprintly                | The website product team meets to prioritize tasks for the upcoming sprint. | Mike Thomas |
-| Design review (#g-digital-experience)      | Daily (Monday - Thursday) | Review designs from the website team.                                       | Mike Thomas |
-| PMMs R Us                     | Weekly (Sunday)         | The CEO meets with the Head of Design to discuss product marketing strategies. | Mike Thomas |
-
-                                                            |
--->
-
 
 #### Stubs
 The following stubs are included only to make links backward compatible.
diff --git a/handbook/product-design/product-design.rituals.yml b/handbook/product-design/product-design.rituals.yml
index a00a6ef9e0..020b1e4949 100644
--- a/handbook/product-design/product-design.rituals.yml
+++ b/handbook/product-design/product-design.rituals.yml
@@ -8,3 +8,67 @@
   autoIssue:   # Enables automation of GitHub issues
     labels: [ "#g-endpoint-ops" ] # label to be applied to issue
     repo: "confidential"
+-
+  task: "Design sprint review"
+  startedOn: "2024-03-07" 
+  frequency: "Triweekly" 
+  description: "Clear out the drafting board of all issues that are not estimated but leave the items we want to take in the next sprint on the drafting board. Record the number of dropped stories for KPIs (all user stories that did not meet the 3 week drafting timeline)." 
+  moreInfoUrl:  
+  dri: "noahtalerman" 
+-
+  task: "🎁 Feature fest"
+  startedOn: "2024-03-07" 
+  frequency: "Triweekly" 
+  description: "We make a decision regarding which customer and community feature requests can be committed to in the next six weeks." 
+  moreInfoUrl: 
+  dri: "noahtalerman" 
+-
+  task: "Design sprint kickoff"
+  startedOn: "2024-03-07" 
+  frequency: "Triweekly" 
+  description: "Add stories prioritized during Feature fest to Drafting board, assign stories to product designers, and align on priorities." 
+  moreInfoUrl: 
+  dri: "noahtalerman"
+-
+  task: "Sprint kickoff review"
+  startedOn: "2024-03-07" 
+  frequency: "Triweekly" 
+  description: "Identify stories that did not make it into this sprint and remove them from the board. Notify relevant requesters/stakeholders. Ensure bugs have been effectively prioritized across teams. Recommend highlights for next release notes. Record the number of drops for KPI reporting. Consider product group staffing. Are we scheduling what we prioritized?  Did we finish what we scheduled in the sprint?  (Look at org chart.)" 
+  moreInfoUrl: 
+  dri: "noahtalerman"
+-
+  task: "🦢🗣 Design review (#g-mdm)"
+  startedOn: "2024-03-07" 
+  frequency: "Daily" 
+  description: "Contributors present wireframes (UI changes) that are “Ready for review”. Head of Product Design provides feedback on UI/CLI/API changes." 
+  moreInfoUrl: "https://docs.google.com/document/d/1AduqZ9yuMQ8uvC5Z6GJFJtE0pbdqdX9zHIau_VCOqGI/edit#"
+  dri: "marko-lisica"
+-
+  task: "🦢🗣 Design review (#g-endpoint-ops)"
+  startedOn: "2024-03-07" 
+  frequency: "Daily" 
+  description: "Contributors present wireframes (UI changes) that are “Ready for review”. Head of Product Design provides feedback on UI/CLI/API changes." 
+  moreInfoUrl: "https://docs.google.com/document/d/1_lIlhaIpR7yYZz-sp8iE5OIipDgrq7AdZTkeoz3Mf9c/edit#"
+  dri: "rachaelshaw"
+-
+  task: "Maintenance"
+  startedOn: "2024-03-01" 
+  frequency: "Weekly" 
+  description: "Head of Product Design checks the latest versions of relevant platforms, updates the maintenance tracker, and notifies the #help-product-design Slack channel." 
+  moreInfoUrl: 
+  dri: "noahtalerman"
+-
+  task: "Product confirm and celebrate"
+  startedOn: "2024-02-27" 
+  frequency: "Weekly" 
+  description: "Review user stories we shipped but haven't closed/ Confirm all the loose ends are tied up: docs, internal and external comms, guides, pricing page, transparency page, user permissions." 
+  moreInfoUrl: 
+  dri: "noahtalerman"
+-
+  task: "Pre-sprint prioritization"
+  startedOn: "2024-02-27" 
+  frequency: "Triweekly" 
+  description: "The Head of Product Design and each group's EM meet before each sprint to align on priorities and discuss what stories weren't completed in the previous sprint. Head of Product Design records number of stories that weren't completed in the “Stories dropped” product KPI." 
+  moreInfoUrl: 
+  dri: "noahtalerman"
+