From 9c671c04dfcd2009319b4134ebc543a7c7126a61 Mon Sep 17 00:00:00 2001 From: Luke Heath Date: Thu, 24 Apr 2025 16:52:22 -0500 Subject: [PATCH] Update pushed story process (#28544) --- handbook/engineering/README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index 15c6477a1b..371bc8cbd4 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -273,13 +273,15 @@ In these cases there are two differences in our pull request process: ### Notify stakeholders when a user story is pushed to the next release -[User stories](https://fleetdm.com/handbook/company/product-groups#scrum-items) are intended to be completed in a single sprint. When the EM suspects a user story is at risk for getting pushed, it is the product group EM's responsibility to notify stakeholders: +[User stories](https://fleetdm.com/handbook/company/product-groups#scrum-items) are intended to be completed in a single sprint. When the EM knows a user story will be pushed, it is the product group EM's responsibility to notify stakeholders: 1. Add the `~pushed` label to the user story. 2. Update the user story's milestone to the next minor version milestone. 3. Comment on the GitHub issue and at-mention the Head of Product Design and anyone listed in the requester field. 4. 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, or #g-orchestration Slack channel. +> Instead of waiting until the end of the sprint, notify stakeholders as soon as you know the story is being pushed. + ### Run Fleet locally for QA purposes