If any small adjustments are needed, we make them live on the call.ī.
The squad asks any clarifying questions to help us better understand the work required.Ī.The stakeholder who wrote the Story gives a brief overview of the Story.We go through the Stories, in order of priority (assigned by product) one by one in the following way: Every other week, we hold a 1-hour meeting with the entire squad. We use pointing poker ( the StoryPlan plugin for Slack) to assign points to Stories during our Refinement process.
#SET UP SHORTCAT CODE#
8 points: A pretty complex task and/or a task that is mostly unknowns.Įxample: Building a feature in an area of the code we are unfamiliar with or that may have dependencies with other squads.
5 points: A more complex task and/or a solid amount of unknowns that will eat up time while the task is worked on.Įxample: Building a small feature in a part of the code that we may be unfamiliar with. 3 points: A mildly complex task and/or some unknowns that may cause an increase in complexity as we build (but we have a pretty solid idea of how we will approach the work).Įxample: Returning a new response in a payload for the frontend to consume, in an API we have worked in before. 2 points: A pretty straightforward task, with a low risk of an unknown or unexpected complexity cropping up.Įxample: Creating a new tracking event in our system, which is a task we do consistently. 1 point: A very straightforward task with NO unknown risks.Įxample: Copy change in a place where we’ve changed copy before. So that we can account for all work we’re doing, we assign all stories at least 1 point. 0 points: We do not use 0 points in our process - even for a task that may not require development time, it will still require someone’s time and energy.
0 kommentar(er)
