From a60b906339b5fb1fa20d5c36c63f670a2c96765b Mon Sep 17 00:00:00 2001 From: Rachael Shaw Date: Wed, 30 Aug 2023 16:38:51 -0500 Subject: [PATCH] Handbook: Add content about how to address potential blockers when implementing a user story (#13556) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Updated the "Product groups" page to emphasize **🟢 iteration** when considering whether to bring a user story back for expedited drafting. --------- Co-authored-by: Sampfluger88 <108141731+Sampfluger88@users.noreply.github.com> --- handbook/company/product-groups.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index 379c7c3d03..b9b163b3ea 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -191,6 +191,7 @@ Design consultations are scheduled as needed with the relevant participants, typ - Review wireframes - Discuss design input - Discuss implementation details + #### Design reviews Design reviews are [conducted daily by the CEO](https://fleetdm.com/handbook/company/ceo#calendar-audit). @@ -208,7 +209,23 @@ The product designer prepares proposed changes in the form of wireframes for thi #### Developing from wireframes Please read carefully and [pay special attention](https://fleetdm.com/handbook/company/why-this-way#why-do-we-use-a-wireframe-first-approach) to UI wireframes. -Designs have usually gone through multiple rounds of revisions, but they could easily still be overlooking complexities or edge cases! When you think you've discovered a blocker, communicate. Leave a comment [mentioning the appropriate PM](https://fleetdm.com/handbook/company/development-groups) or ask for feedback at your next standup. Then update this user story's estimation, wireframes, and "definition of done" to reflect your updated understanding. +Designs have usually gone through multiple rounds of revisions, but they could easily still be overlooking complexities or edge cases! When you think you've discovered a blocker, here's how to proceed: + +**For implementation concerns...** + +Communicate. Leave a comment [mentioning the appropriate PM](https://fleetdm.com/handbook/company/product-groups#current-product-groups) so they can update the user story and estimation to reflect your new understanding of the issue. + +**For all other concerns...** + +At Fleet, we prioritize [iteration](https://fleetdm.com/handbook/company#results). So before raising the alarm, think through the following: + ++ Would addressing this add design work and/or delay shipping the feature? ++ Will this hurt the first-time user experience if we ship as-is? ++ Is this change a "one-way door"? + +After these considerations, if you still think you've found a blocker, alert the [appropriate PM](https://fleetdm.com/handbook/company/product-groups#current-product-groups) so that the user story can be brought back for [expedited drafting](https://fleetdm.com/handbook/product#expedited-drafting). Otherwise, this concern may be better suited to a [feature request](https://fleetdm.com/handbook/product#intake). + + #### Sub-tasks