<aside> <img src="/icons/list-indent_gray.svg" alt="/icons/list-indent_gray.svg" width="40px" /> SIS Background
We have thought about and used many names for SIS, and in the end we think that Stream Iteration Sync captures the flexibility of the approach.
SIS is not part of any framework, but could be used together with most of the ones we can think about. Part of the Sync Event inspiration came from PI planning in SAFe, but of course SAFe does not adhere to the Minimum Viable Process principle. Other ideas are more compatible with Nexus, or LeSS, or Disciplined Agile. We were amazed to see how much our philosophy has in common with UnFix, or better its very first version. And we could not think about a new SIS design without having applied Team Topologies first. So, as usual, what you choose to do will depend on your context and skill. We hope that our SIS description can give you useful ideas.
It’s important to note that the authors do not give a monkey about the waterfall, agile, lean labels. Every practitioner must be fluent in all, and be conscious of their inevitable bias towards one or the other. Depending on your bias, you can label SIS in multiple ways, and we like that.
Contents:
Stream Iteration Sync is licensed under CC BY 4.0