Scrum and eXtreme programming, the first agile development frameworks, were designed with very few advice on coordination for work in larger scale were several teams cooperate toward a common goal. This lead to both wrong assumptions regarding the usefulness of agile ways of working in larger organizations as well as much individual tailoring with coordination practices in organizations. Now, the Scaled Agile Framework is gaining much attention in software development. This study contains an analysis of inter-team coordination practices prescribed in the framework and how they have been implemented in three organizations. Previous research on coordination has been criticized for having a static view on coordination with not enough focus on how to manage emerging dependency issues. The result of this study shows that the Scaled Agile Framework have four practices that cover both planning and emerging issues and three practices solely aimed at managing these emerging dependency issues.