From 169046697faed29e293b9f766437563640cfebdd Mon Sep 17 00:00:00 2001 From: Tim Lee Date: Tue, 22 Jul 2025 17:19:11 -0400 Subject: [PATCH] Refresh story descriptions from template during design sprint kickoff (#31098) Proposing we add a ritual to refresh story descriptions based on the latest story template. Why? We bring in stories into the design sprint that were created before changes were made and refreshing the description ensures we don't miss important scope discussions. This came up today during user story review where we almost missed gitops changes because the story description didn't have the associated checkboxes. Additional question: Is there anywhere else we need to document this so we don't forget? --- 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 4f9e9d2a1e..7b63aedf1e 100644 --- a/handbook/product-design/product-design.rituals.yml +++ b/handbook/product-design/product-design.rituals.yml @@ -16,7 +16,7 @@ task: "Product design sprint kickoff" # 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: "Review stories (and, as needed, create engineering research stories) for feature requests prioritized during Feature fest; assign Engineering DRIs to stories; align on priorities; and create an upcoming reference docs release branch." + description: "Review stories (and, as needed, create engineering research stories) for feature requests prioritized during Feature fest; refresh descriptions from the latest story template; assign Engineering DRIs to stories; align on priorities; and create an upcoming reference docs release branch." moreInfoUrl: dri: "noahtalerman" -