From c0e2c904733e8505c7e8d1ea2ead51dda2fa3197 Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Thu, 26 Jun 2025 10:09:59 -0400 Subject: [PATCH] Update product-design.rituals.yml (#30336) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit No longer using Zenhub's roadmap chart. Using GitHub's "Sprint" feature instead: Screenshot 2025-06-26 at 10 07 05 AM --- handbook/product-design/product-design.rituals.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/product-design/product-design.rituals.yml b/handbook/product-design/product-design.rituals.yml index 5feebee8dd..7c1f0a0e56 100644 --- a/handbook/product-design/product-design.rituals.yml +++ b/handbook/product-design/product-design.rituals.yml @@ -2,7 +2,7 @@ task: "🦢📊 Product design sprint review" # 2024-03-06 TODO: Link to responsibility or corresponding "how to" info e.g. https://fleetdm.com/handbook/company/product-groups#making-changes startedOn: "2024-03-07" frequency: "Triweekly" - description: "1. For all stories that are not estimated, move them on the roadmap chart and add their respective customer requests to the feature fest board. For stories that we're no longer working on, remove them from the drafting board and roadmap chart, remove their respective customer requests from the 💝 Customer requests board, and notify stakeholders. 2. Retro: What went well? What could go better? What to remember for next time?" + description: "1. For all stories that are not estimated, update their target engineering sprint and add their respective customer requests to the feature fest board. For stories that we're no longer working on, remove them from the drafting board, remove their target engineering sprint, remove their respective customer requests from the 💝 Customer requests board, and notify stakeholders. 2. Retro: What went well? What could go better? What to remember for next time?" moreInfoUrl: dri: "noahtalerman" -