From e17ba7abba13f54e22b909dc3634595f93cda7a9 Mon Sep 17 00:00:00 2001 From: Marko Lisica <83164494+marko-lisica@users.noreply.github.com> Date: Fri, 23 Jan 2026 21:41:03 +0100 Subject: [PATCH] Revise stakeholder notification for user story pushes (#38711) - We no longer have a requester field in the issue template. - Updated the notification process for user stories pushed to the next sprint to include the release DRI. - Not sure if we have documented in other spot when to ping the release DRI, but I think we should in this case as well. --- handbook/product-design/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/product-design/README.md b/handbook/product-design/README.md index 9f97065055..e1133c514e 100644 --- a/handbook/product-design/README.md +++ b/handbook/product-design/README.md @@ -196,7 +196,7 @@ If the original request is a customer request, the PD also assigns the relevant [User stories](https://fleetdm.com/handbook/company/product-groups#scrum-items) are intended to be [drafted](#drafting) and estimated in a single sprint. When the Product Designers (PD) knows a user story will be pushed, it is the PD's responsibility to notify stakeholders: -1. Comment on the GitHub issue and at-mention the Head of Product Design and anyone listed in the requester field. +1. Comment on the GitHub issue and at-mention the Head of Product Design and [release DRI](https://fleetdm.com/handbook/company/communications#directly-responsible-individuals-dris). 2. If `customer-` labels are applied to the user story, at-mention the [VP of Customer Success](https://fleetdm.com/handbook/customer-success#team) in the #g-mdm, #g-software, #g-orchestration, or #g-security-compliance Slack channel. > Instead of waiting until the end of the sprint, notify stakeholders as soon as you know the story is being pushed.