Do Agile Scaling Approaches Make A Difference? An Empirical Comparison of Team Effectiveness Across Popular Scaling Approaches

<p>This bundle contains supplementary materials for an upcoming academic publication <em>Do Agile Scaling Approaches Make A Difference? An Empirical Comparison of Team Effectiveness Across Popular Scaling Approaches?</em>, by Christiaan Verwijs and Daniel Russo. Included in the bundle are the dataset and SPSS syntaxes. This replication package is made available by C. Verwijs under a &quot;Creative Commons Attribution Non-Commercial Share-Alike 4.0 International&quot;-license (CC-BY-NC-SA 4.0).</p> <p><strong>About the dataset</strong></p> <p>The dataset (SPSS) contains anonymized&nbsp;response data from 15,078 team members aggregated into 4,013 Agile teams that participated from <a href="https://scrumteamsurvey.org">scrumteamsurvey.org</a>. Stakeholder evaluations of 1,841 stakeholders were also collected for 529 of those teams. Data was gathered between&nbsp;September 2021, and September 2023. We cleaned the individual&nbsp;response&nbsp;data from careless responses and removed all data that could potentially identify teams, individuals, or their parent organizations. Because we wanted to analyze our measures at the team level, we calculated a team-level mean for each item in the survey. Such aggregation is only justified when at least 10% of the variance exists at the team level (Hair, 2019), which was the case (ICC = 35-50%). No data was missing at the team level.</p> <p>Question labels and option labels are provided separately in Questions.csv. To conform to the privacy statement of <a href="https://scrumteamsurvey.org">scrumteamsurvey.org</a>, the bundle does not include response data from before the team-level aggregation.</p> <p><strong>About the SPSS syntaxes</strong></p> <p>The bundle includes the syntaxes we used to prepare the dataset from the raw import, as well as the syntax we used to generate descriptives. This is mostly there for other researchers to verify our procedure.</p>