<aside>
<img src="/icons/list-indent_gray.svg" alt="/icons/list-indent_gray.svg" width="40px" /> The Sync Event
The event needs to be carefully and lovingly designed to suit the needs of the teams. These elements have been found useful:
-
Training Recommended 👍
- Everyone needs to know what to expect at the Sync Event and how to prepare for it. Even once it is routine, still organise training before the Sync Event for new starters and provide everyone with information about changes from the last event.
-
Introduction Mandatory 👍👍👍
- To remind everyone the purpose of the Sync Event and how to approach it, an introduction on the day is essential.
-
Context Optional
- The context must be communicated before planning and the Sync Event. However any last minute important update could be done as a 1toAll on the day.
-
Learnings Mandatory 👍👍👍
- Each team presents their learnings from the last iteration which support or challenge their assumptions and intentions.
-
Achievements Recommended 👍
- Celebrating achievements is good for morale and part of learning. There could be demonstrations.
-
Intentions Mandatory 👍👍👍
- Each team presents their high-level intentions for the upcoming iteration. Detailed intentions and plans can be discussed at the open space.
-
Open space Mandatory 👍👍👍
- This is the space for dialogue and serendipitous discovery.
-
Leadership check-in Optional
- At some point, leadership may meet to review the planning progress so far and sort out any issues. This can be with closed doors or as a fishbowl.
- The check-in can also be after the event, with any feedback loop done asynchronously.
-
Review of changes Recommended 👍
- Time to communicate any important changes and discoveries which happened during the sync event to everyone.
-
Closing Recommended 👍
- Short time to tell everyone how amazing they have been and infuse some energy in the upcoming iteration!
Next:
1toAll Components
Stream Iteration Sync is licensed under CC BY 4.0