From 0c66a09797c2f530ebcb5c2410bc3bdd262e48ff Mon Sep 17 00:00:00 2001 From: Luke Heath Date: Wed, 31 May 2023 15:29:14 -0500 Subject: [PATCH] Clarify bug prioritization process (#12071) --- handbook/product/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/handbook/product/README.md b/handbook/product/README.md index 6a61ccd741..761c16cf87 100644 --- a/handbook/product/README.md +++ b/handbook/product/README.md @@ -82,6 +82,8 @@ Product Managers prioritize all potential product improvements worked on by cont Bugs are always prioritized. (Fleet takes quality and stability [very seriously](https://fleetdm.com/handbook/company/why-this-way#why-spend-so-much-energy-responding-to-every-potential-production-incident).) +If a bug is unreleased or [critical](https://fleetdm.com/handbook/engineering#critical-bugs), it is addressed in the current sprint. Otherwise, it may be prioritized in the sprint backlog for the next sprint. Bugs are never carried more than one sprint. + > Anyone can [suggest improvements](#intake). ## Writing user stories