From 61e3e0c8ab223e3bc2898c05f8b600759b165bd5 Mon Sep 17 00:00:00 2001 From: Mike McNeil Date: Mon, 29 Apr 2024 09:34:47 -0500 Subject: [PATCH] Handbook: Update product-groups.md (#18590) (The numbers were confusing. It was like: "(1) P0, (2) P1, (3) P2") --- handbook/company/product-groups.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index cf1fa78169..fc66b775b3 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -431,20 +431,20 @@ Bugs will be verified as fixed by QA when they are placed in the "Awaiting QA" c ## High priority user stories and bugs All issues are treated as standard priority by default. Some issues are assigned a priority label to indicate urgency for the business. -1. Emergency: `P0` -- Examples: Customer outage, confirmed security vulnerability ([critical bug](https://fleetdm.com/handbook/company/product-groups#release-testing)), a new feature is needed to address an immediate business emergency. -- Response: Immediately stop other work to swarm the issue. Work 24/7 in shifts until resolved. -- Impact: Significant impact. May void current sprint. +- Emergency: `P0` + - Examples: Customer outage, confirmed security vulnerability ([critical bug](https://fleetdm.com/handbook/company/product-groups#release-testing)), a new feature is needed to address an immediate business emergency. + - Response: Immediately stop other work to swarm the issue. Work 24/7 in shifts until resolved. + - Impact: Significant impact. May void current sprint. -2. Critical: `P1` -- Examples: A supported workflow is broken ([critical bug](https://fleetdm.com/handbook/company/product-groups#release-testing)), a potential security vulnerability, a new feature is required to address an immediate critical business need. -- Response: Issue brought to next standup for estimation and immediately brought into the sprint. Necessary team members are assigned as their top priority. -- Impact: High impact. Does not void sprint, but reduces overall velocity and requires deprioritizing other work. +- Critical: `P1` + - Examples: A supported workflow is broken ([critical bug](https://fleetdm.com/handbook/company/product-groups#release-testing)), a potential security vulnerability, a new feature is required to address an immediate critical business need. + - Response: Issue brought to next standup for estimation and immediately brought into the sprint. Necessary team members are assigned as their top priority. + - Impact: High impact. Does not void sprint, but reduces overall velocity and requires deprioritizing other work. -3. Urgent: `P2` -- Examples: A supported workflow is not functioning as intended, a newly drafted feature has an associated urgent business need. -- Response: Issue is prioritized at the top of the next sprint. If opporunity cost of waiting for the next sprint is too high, it may be considered for current sprint. -- Impact: Low to medium impact. If prioritized into current sprint, may reduce overall velocity and require deprioritizing other work. +- Urgent: `P2` + - Examples: A supported workflow is not functioning as intended, a newly drafted feature has an associated urgent business need. + - Response: Issue is prioritized at the top of the next sprint. If opporunity cost of waiting for the next sprint is too high, it may be considered for current sprint. + - Impact: Low to medium impact. If prioritized into current sprint, may reduce overall velocity and require deprioritizing other work. Add as much context as possible to the issue description and assign labels to help the team understand the problem and what is driving the urgency. All issues with a `P0`, `P1`, or `P2` label should be assigned to the [DRI for what goes in a release](https://fleetdm.com/handbook/company/communications#directly-responsible-individuals-dris). For immediate action, follow up on Slack or by phone.