canmove, Confirmed users
1,953
edits
Engagement/MDN Durable Team/Processes: Difference between revisions
Engagement/MDN Durable Team/Processes (view source)
Revision as of 23:05, 15 June 2018
, 15 June 2018→Planning Sprints
| Line 59: | Line 59: | ||
This work can be done asynchronously, or during project- or team-specific planning meetings. | This work can be done asynchronously, or during project- or team-specific planning meetings. | ||
The whole team convenes for a final [[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 confidence ratings (High/Medium/Low), indicating how confident the team is that the user story can be completed during the sprint. The team also reviews 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 acceptance criteria will be met. | The whole team convenes for a final [[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. The team should keep in mind the number of person-days available in the sprint (based on the number of days in the sprint, the number of people on the team, and the number of exceptions, such as holidays, PTO, travel, etc.). The total number of story points for the stories in the sprint should not exceed (and preferably be less than) the number of available person-days. | ||
User stories are given confidence ratings (High/Medium/Low), indicating how confident the team is that the user story can be completed during the sprint. The team also reviews 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 acceptance criteria will be met. | |||
GitHub milestones are used to represent sprints. For each sprint, a milestone is created with a deadline of the last day of the sprint. | GitHub milestones are used to represent sprints. For each sprint, a milestone is created with a deadline of the last day of the sprint. | ||