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

• Duration

• Participants

• Components

• 1toAll components

• The Open Space

• Pre and post-event

• Organising team

• Logistics - in person

• Logistics - Remote

• Example agenda </aside>

If you have not run an open space before, this is a good description.

The logistics pages have more detail about how things can be laid out for an in-person or remote event, but in general you’ll need:

• A space for everyone to listen in at the same time
• Locations that each team can own for the duration of the open space and where they can show and edit their delivery board to a small audience
  • Supporting functions may fully participate as separate teams as well
• All useful information shown somewhere in the space

Base Open Space

The default rules of engagement during a SIS Open Space are:

• Each team location has team representation at all times
• Everyone can move anywhere to discuss plans or anything else
• By the end of the open space, all dependencies on all delivery boards must have an owner (team or individual)

That’s it. It’s a massively parallel component of the sync event.

Hot Topics

The open space can also have organised discussion spaces for any kind of cross-anything discussion. These are in addition to the team spaces and it’s helpful to have bookable slots people can advertise. We have called these “Hot Topics” once and the name stuck.

The Hot Topics are different to organising a standard meeting: they are useful when you are unsure about who would be interested in discussing the specific topic. As such, there in no point in organising a long hot topic: you can use a follow-up.

Some examples of valuable hot topics:

• Any topic potentially interesting multiple teams
• Controversial topics
• Retrospective or futurespective
• An architectural discussion
• A strategic option
• A product demonstration
• Technical deep dive