From 8102dc51fe65774ed66d8ca6c4c3091d5c67ce2b Mon Sep 17 00:00:00 2001 From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com> Date: Mon, 30 Oct 2023 14:43:21 -0400 Subject: [PATCH] Update product handbook (#14794) - Make "Design sprint review" and "Design sprint kickoff" cross-group --- handbook/product/README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/handbook/product/README.md b/handbook/product/README.md index 5ff98f666c..f34193c092 100644 --- a/handbook/product/README.md +++ b/handbook/product/README.md @@ -422,13 +422,11 @@ Directly Responsible Individuals (DRI) engage in the ritual(s) below at the freq | Ritual | Frequency | Description | DRI | |:-----------------------------|:-------------------------|:----------------------------------------------------|-------------------| -| Design sprint review (#g-endpoint-ops) | Sprintly (Wednesday) | After the last estimation session, the Head of Product reviews the board with each group PM and designer and de-prioritizes all design issues that were not estimated. The Head of Product also collects all items that are product-driven and puts them in the 🎁ðŸ—Ģ Feature fest meeting agenda to consider for continuing work. The number of de-prioritized issues should be recorded in the KPI spreadsheet. | Noah Talerman | -| Design sprint review (#g-mdm) | Sprintly (Thursday) | After the last estimation session, the Head of Product Design reviews the board with each group PM and designer and de-prioritizes all design issues that were not estimated. The group PM collects all items that were de-prioritized and, if desired, puts them in the 🎁ðŸ—Ģ Feature fest meeting agenda to consider for continuing work. The number of de-prioritized issues should be recorded in the KPI spreadsheet. | Noah Talerman | +| Design sprint review | Sprintly (Thursday) | After the last estimation session, the Head of Product Design reviews the board with each group designer and de-prioritizes all design issues that were not estimated. The Head of Product Design also collects all items that are product-driven and puts them in the 🎁ðŸ—Ģ Feature fest meeting agenda to consider for continuing work. The number of de-prioritized issues should be recorded in the KPI spreadsheet. | Noah Talerman | | 🎁 Feature fest prep | Sprintly (Thursday) | The Head of Product Design reviews the agenda and pre-comments on items in order to be well-prepared for the discussion. | Noah Talerman | | 🎁ðŸ—Ģ Feature fest | Sprintly (Thursday) | We make a decision regarding which customer and community feature requests can be committed to in the next six weeks. We create issues for any requests that don't already have one. | Noah Talerman | | 🎁 Feature fest cleanup | Sprintly (Thursday) | Clean up the agenda in anticipation of the next meeting | Noah Talerman | -| Design sprint kickoff (#g-endpoint-ops) | Sprintly (Thursday) | the Head of Product Design introduces and determines the order of the newly prioritized list of work with each group PM | Noah Talerman | -| Design sprint kickoff (#g-mdm) | Sprintly (Thursday) | the Head of Product Design introduces and determines the order of the newly prioritized list of work with each group PM | Noah Talerman | +| Design sprint kickoff | Sprintly (Friday) | The Head of Product Design introduces and determines the order of the newly prioritized list of work with each group designer | Noah Talerman | | ðŸ—Ģ Product office hours | Weekly (Tuesday) | Ask questions to the product team | Noah Talerman | | Sprint kickoff review | Sprintly (Monday) | After each sprint kickoff, the Head of Product Design reviews the Estimated column with each group EM and de-prioritizes the features that were not included in the sprint and prepares recommended highlights for the release notes. The number of de-prioritized issues should be recorded in the KPI spreadsheet. | Noah Talerman | | ðŸĶĒðŸ—Ģ Design review (#g-mdm) | Daily | Review designs from the MDM team | Marko Lisica |