<aside> <img src="/icons/list-indent_gray.svg" alt="/icons/list-indent_gray.svg" width="40px" /> The Sync Event

The whole value stream should be at the Sync Event along with all Research and Development (R&D) teams, all support functions, all stakeholders.

If this is not possible, the missing parts need to be formally represented by other participants.

Which teams are “presenting” teams needs to be decided. All R&D teams usually makes sense, but consider if shared enablement teams or functions should contribute their learnings and plans actively too.

Everyone else will participate by being available, questioning and interacting with the value stream.

Attendance

Be explicit with the participants if their presence is required or optional, depending on their role in the Sync Event.

If teams don’t buy-in, try making the most interactive components optional. Although not forcing anyone to participate, the fear of missing out will kick in and people will come anyway. They perceive their participation as voluntary with consequently greater engagement and returns.

Voluntary participation is also a better way to engage with a range of neurodiverse people. With time, every team member will find a way to participate which will work both for them and the rest of the value stream.

Next:

Sync Event: Components

Stream Iteration Sync is licensed under CC BY 4.0