<aside> <img src="/icons/list-indent_gray.svg" alt="/icons/list-indent_gray.svg" width="40px" /> Introduction to SIS
SIS iterates over sync iterations. The Sync Event marks the end of the previous iteration and the start of the new one; the heartbeat of the value stream.
The Sync event could happen during the current or next iteration
Throughout the iteration, shared synchronisation models are maintained. They are updated for the future iteration before the sync event, then discussed and perfected at the event.
Shorter, leaner events can be held more often. This shortens the feedback cycle to a point where participants remember more about the previous event and accelerates the improvement of the event.
In our experience, events held every 3 months take 5-6 cycles to get to a “good” effectiveness.
Events held every 6 weeks took only 3-4 cycles to be at the same level of maturity. This translates to 6 months versus 18 to get to an effective process (!).
We like a six-week cadence for several reasons:
<aside> ℹ️ The cadence can and should be adapted to consider holidays. A Sync Event should follow any long holiday periods. This helps recall information from the last iteration and refreshes plans for the future. When considering a 6 week sync iteration, adding 1 or 2 weeks for holiday periods at the end of the iteration makes sense. For example in western countries, the iteration including Christmas could be 8 weeks long and the Easter iteration could be 7 weeks long. The effective effort spent in the iteration will be roughly constant and the cadence will roughly align to quarters.
</aside>
Next:
Stream Iteration Sync is licensed under CC BY 4.0