canmove, Confirmed users
1,953
edits
Engagement/MDN Durable Team/Processes: Difference between revisions
Engagement/MDN Durable Team/Processes (view source)
Revision as of 21:33, 21 June 2019
, 21 June 2019→Tracking progress
(→Planning Sprints: Added note about AC requirement) |
|||
| Line 121: | Line 121: | ||
===Tracking progress=== | ===Tracking progress=== | ||
During the 12 work days of a Sprint, team members need to communicate regularly about progress and obstacles. The MDN does this mostly asynchronously, using [https://statushero.com/ Status Hero]. The sub-teams hold a synchronous [[Engagement/MDN_Durable_Team/Agile_glossary#Standup|Standup]] meeting on the first Wednesday of a sprint, and the whole team meets for a [[Engagement/MDN_Durable_Team/Agile_glossary#Mid-sprint_check-in|Mid-sprint review]] on the second | During the 12 work days of a Sprint, team members need to communicate regularly about progress and obstacles. The MDN does this mostly asynchronously, using [https://statushero.com/ Status Hero]. The sub-teams hold a synchronous [[Engagement/MDN_Durable_Team/Agile_glossary#Standup|Standup]] meeting on the first Wednesday of a sprint, and the whole team meets for a [[Engagement/MDN_Durable_Team/Agile_glossary#Mid-sprint_check-in|Mid-sprint review]] on the second Monday of the sprint. | ||
==Sharing Outcomes== | ==Sharing Outcomes== | ||