Engagement/MDN Durable Team/Processes: Difference between revisions

Line 124: Line 124:
==Improving Processes==
==Improving Processes==
At the conclusion of a Sprint, the team holds a [[Engagement/MDN_Durable_Team/Agile_glossary#Retrospective|Retrospective]] to reflect on the team's processes and habits, in order to find ways to improve or strengthen them. This meeting is limited to core team members, to facilitate frank discussion.
At the conclusion of a Sprint, the team holds a [[Engagement/MDN_Durable_Team/Agile_glossary#Retrospective|Retrospective]] to reflect on the team's processes and habits, in order to find ways to improve or strengthen them. This meeting is limited to core team members, to facilitate frank discussion.
Marketing Durable Teams hold their Retrospectives on the third Wednesday of the sprint cycle, in most cases following the Sprint Review meeting. The MDN team holds theirs on that Wednesday, but ''prior'' to the Sprint Review, to accommodate the schedules of team members in Europe.


The MDN durable team uses a slightly different structure for the retrospective discussion:
The MDN durable team uses a slightly different structure for the retrospective discussion:
* General observations
* What worked well?
* What worked well?
* What didn't work?
* What didn't work?
* What steps will we take to improve?
* What steps will we take to improve?
* How did the adjustments we decided on in the last retrospective go?
Variations on this structure are possible, to avoid staleness. For some retrospectives, it may be helpful to focus on a specific aspect of the work, processes, or tooling used by the team.


If the team decides to change processes that are documented in this article, then this article will be updated to reflect the change.
If the team decides to change processes that are documented in this article, then this article will be updated to reflect the change.
canmove, Confirmed users
1,953

edits