canmove, Confirmed users
1,953
edits
Engagement/MDN Durable Team/Processes: Difference between revisions
Jump to navigation
Jump to search
Engagement/MDN Durable Team/Processes (view source)
Revision as of 19:48, 25 August 2016
, 25 August 2016→Planning Sprints: size and confidence estimates
(→Planning Sprints: size and confidence estimates) |
|||
| Line 52: | Line 52: | ||
==Planning Sprints== | ==Planning Sprints== | ||
Selection of User Stories to be worked on during a [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint|Sprint]] happens in the week before the start of a new Sprint. Durable team members in the content and | Selection of User Stories to be worked on during a [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint|Sprint]] happens in the week before the start of a new Sprint. Durable team members in the content, development, and community areas work separately to select and flesh out the User Stories in each area, so that they are ready to be placed in the [[Engagement/MDN_Durable_Team/Agile_glossary#Task_Board|Task Board]]. The groups also review the [[Engagement/MDN_Durable_Team/Agile_glossary#Task_|Tasks]] for each User Story, to ensure that they can be done in one Sprint, and are complete enough to ensure that the [[Engagement/MDN_Durable_Team/Agile_glossary#Acceptance_Criteria|Acceptance Criteria]] will be met. | ||
The whole team convenes for a [[Engagement/MDN_Durable_Team/Agile_glossary#Sprint_Planning_Meeting|Sprint Planning Meeting]] (usually on Thursday), to review and refine all the selected stories for the sprint. User stories are given "t-shirt" (S/M/L) size estimates, and confidence ratings (High/Medium/Low). The size estimate categories are based on the number of days they are expected to take to complete: | |||
;Small | |||
: a few days | |||
;Medium | |||
: about a week | |||
;Large | |||
: more than a week, up to the whole sprint | |||
The team's committed User Stories are shared with the broader Marketing team. | |||
When prioritizing and planning a sprint, it is a good idea to consider "What will we want to demo at the end of the Sprint?" The user stories that are expected to lead to demo-worthy accomplishments should therefore get a high priority. | When prioritizing and planning a sprint, it is a good idea to consider "What will we want to demo at the end of the Sprint?" The user stories that are expected to lead to demo-worthy accomplishments should therefore get a high priority. | ||