Context: Agile software development is widely-used by small teams and has benefits like increased transparency or faster feedback. However, companies want to benefit from Agile also in the development of big products, where multiple teams are involved. Many Scaling Agile Frameworks exist, but only few can be found in industry, especially SAFe, LeSS, and Nexus. Objective: The aim of this work is to identify commonalities of existing Scaling Agile Frameworks concerning their practices. Method: We extracted and consolidated the practices of twelve frameworks and compared the frameworks based on their practices using a visualization. Results: Frameworks prescribe scaling practices as well as practices on team level. There are practices common to most frameworks like the scaled Scrum events, e.g., a scaled planning meeting or retrospective. Conclusion: Practitioners are enabled to make informed decisions when choosing or tailoring their individual Scaling Agile Framework.
Context: Agile teams are small teams with 3 to 9 members. In complex development endeavors such as systems engineering, an agile team has many dependencies, since it is not possible to incorporate all specialist skills into one team. Frameworks like the Scaled Agile Framework (SAFe) describe how agile teams operate in a larger setting. Objective: The aim of this study is to analyze how agile teams collaborate with their organizational environment. Method: We analyzed SAFe to investigate how much guidance it provides concerning the collaboration between agile teams and their environment. Results: The results show that many different organizational parts exist with which agile teams have to collaborate. SAFe mentions concepts like shared services, system teams, or business teams, but there is no further guidance on collaboration with the agile team. Conclusion: We motivate future research into guidelines for efficient collaboration of agile teams with their organizational environment.