In OpenSpace Agility, time is a very big deal. Time frames the experience for participants.
The reality is that OSA implements Agile in an Agile way: encouraging experimentation inside a time-box.
In OSA we contain the experience within this time-constraint. During the 100 days in between the two Open Space events, experimentation and learning are encouraged. While predictable and reliable delivery of working software is the ultimate end goal, the journey starts with experimentation, learning, and adaptation. All of this is bounded by time to produce a clearly-marked beginning, middle, and end for participants.
It is important to note that 100 days is the recommended period of time to allow between the two Open Space events. Less time can work just as well, provided that the entire experience is clearly framed for participants. As few as 60 days can work provided all of the elements are carefully managed.
The key element to manage is the communication about the next Open Space event. As the entire organization experiments with Agile practices, it is essential to communicate continuously that all of the experience inside the time-box is going to to be inspected carefully by the enterprise at the next Open Space event.
In practical terms, what this means is that everyone needs to know the exact date of the next Open Space event. This also means that formally authorized leaders (executives) need to communicate this date early and often.