Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 09:28:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 52

Revise stakeholder notification for user story pushes (#38711)

Browse source 
- 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.
This commit is contained in:
Marko Lisica 2026-01-23 21:41:03 +01:00 committed by GitHub
parent a266ac0515
commit e17ba7abba
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
handbook/product-design/README.md
View file

@ -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.