<aside> <img src="/icons/list-indent_gray.svg" alt="/icons/list-indent_gray.svg" width="40px" /> SIS Background
We loosely followed the process described by Roberto Verganti in “Overcrowded”.
It all started with a single person conceiving the Sync Event on a RyanAir flight from London Stansted to Katowice. Big orange stickies were affixed to the bright yellow headrest and to the dark blue back of the seat in front. At this stage the idea was just an ugly duckling, with far more holes than consistency. To grow the idea and ensure it would survive the harshest critics in engineering, another coach volunteered as sparring partner. Then the full coaching team got involved and the duckling became a passable imitation of a swan. Good enough for v1.0.
At the time we were all working on a silicon platform programme. It was hard work for many reasons: very ambitious, international and extremely cross-functional. We’ve just had a platform-wide communication and teamwork workshop that clearly indicated how everyone wanted more cross-team communication, so it has been relatively easy to propose v1.0 to the teams as an experiment to try out, especially given that it only took a couple of hours of their time.
The rest is history. Many more teams have used SIS, under several different names, and at the time of writing we are at v9.0. What a journey.
Next:
Stream Iteration Sync is licensed under CC BY 4.0