From 7aa47f425c85f3d9ea1555070fe767cd95000c24 Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Wed, 16 Apr 2025 11:04:10 -0700 Subject: [PATCH] Product groups handbook (#28295) --- handbook/engineering/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index b60ad615a6..15c6477a1b 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -273,12 +273,12 @@ 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 a user story selected for a release has not merged into `main` by the time the release candidate is created, 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 suspects a user story is at risk for getting 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 PM 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). +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. ### Run Fleet locally for QA purposes