As agile ways of working are implemented in larger settings,inter-team coordination becomes increasingly important. Somedependencies between teams can be identified in advance, butmuch of the dependencies in software development emerge as thesystem evolve. A way to identify, manage, assess, and evaluatethe status of dependencies is to visualize dependencies betweenteams. New artifacts and routines for visualizing dependencies aresuggested from the increasingly popular Scaled Agile Framework,SAFe. This multiple case study focuses on how inter-teamcoordination is visualized by providing a rich description of twoyears of implementation and tailoring of the boundary objectcalled the program board at the (anonymized) organizations AGovand B-Bank. A total of 183 hours of observations and 14interviews were used for triangulation purposes. The findingspresent the difficulties of keeping visualizations up to date. Byinventing and tailoring the routines of managing the ProgramBoard, the current situation of dependencies could be visualizedand kept track of. The findings also indicate the importance ofhow dependencies are defined.