From 1930f904941995c7f01c781c513eececff968b80 Mon Sep 17 00:00:00 2001 From: mmendm Date: Mon, 19 Jan 2026 14:09:13 -0700 Subject: [PATCH] Update product-groups.md (#38482) --- handbook/company/product-groups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index a1a074474f..ea21896742 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -400,7 +400,7 @@ After these considerations, if you still think you've found a blocker, alert the #### Sub-tasks -The simplest way to manage work is to use a single user story issue, then pass it around between contributors/asignees as seldom as possible. But on a case-by-case basis, for particular user stories and teams, it can sometimes be worthwhile to invest additional overhead in creating separate **unestimated sub-task** issues ("sub-tasks"). +The simplest way to manage work is to use a single user story issue, then pass it around between contributors/assignees as seldom as possible. But on a case-by-case basis, for particular user stories and teams, it can sometimes be worthwhile to invest additional overhead in creating separate **unestimated sub-task** issues ("sub-tasks"). A user story is estimated to fit within 1 sprint and drives business value when released, independent of other stories. Sub-tasks are not.