From 4076d139769e15eaa82a941cda6c100901f62ac8 Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Wed, 1 Jul 2026 16:11:11 -0400 Subject: [PATCH] Product design sprint kickoff ritual: Remove retro (#48575) - Product Designers attend respective product group retros instead ## Summary by CodeRabbit * **Documentation** * Updated the Product design sprint kickoff guidance to include clearer steps for planning and capturing prioritized requests. * Removed the end-of-sprint retro reminder from this ritual description. --- 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 df0bf576de..74b045e2de 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: "1. Pull up all contributors' calendars to review time off and, if needed, update design review calendar events. 2. Create reference docs release branches for any milestones newly added to the drafting board 3. For feature requests prioritized during feature fest, add user stories to the drafing and release planning boards, add milestones to the stories, confirm available capacity in targeted release, and align on priorities. Retro last sprint: What went well? What could go better? What to remember for next time? Pick one improvement to implement next sprint." + description: "1. Pull up all contributors' calendars to review time off and, if needed, update design review calendar events. 2. Create reference docs release branches for any milestones newly added to the drafting board 3. For feature requests prioritized during feature fest, add user stories to the drafing and release planning boards, add milestones to the stories, confirm available capacity in targeted release, and align on priorities." moreInfoUrl: dri: "noahtalerman" -