Engagement/MDN Durable Team/Processes: Difference between revisions

Brainstorming of user stories to be worked on happens in a Sprint Goals document (for example, this one from [https://docs.google.com/document/d/1jwXzBDQPpou5gzZKbq_pjOOWTo4G7lyI66BlvVsvD0g/edit?usp=sharing Q3 2018]). Typically, user stories are categorized by the quarterly Key Results they support. However, a given Key Result might not have supporting user stories happening in any given sprint, and a sprint may contain  miscellaneous user stories not connected to a Key Result. Based on this brainstorming, team members create or modify the corresponding user stories as issues in GitHub, and ensure they are ready to be placed in the Backlog in ZenHub. The team optionally identifies a Sprint Goal for Content and Development, which is an area of highest priority for the sub-team; team members are expected to contribute to or support the Sprint Goal foremost if possible. However, it is not required that each sub-team has a Sprint Goal for every sprint, or that team members must work on it, if doing so is not suited to their skill set.