Quantitative Analysis of the Scrum Framework

Scrum provides many benefits to organizations requiring a project management framework for complex adaptive problems. Some of these benefits include improved teamwork, improved time to market, and a noticeable decrease in software defects. The primary objective of this paper is to test nineteen research hypotheses that require a quantitative analysis of the Scrum framework. In order to test these hypotheses, the findings of a survey questionnaire was used to gather response data from Scrum practitioners on their perceptions of factors affecting Scrum adoption. Exploratory factor analysis and Cronbach’s alpha analysis confirmed the validity and reliability of the measuring instrument. Following these analyses, a correlation matrix was used to test the relationship strength among the different factors. The Spearman correlation analysis revealed statistically significant correlations. Multiple linear regression statistical models were developed to examine the existence of factors and constructs impacting Scrum adoption. Our findings indicate that four of the nineteen hypotheses are statistically significant. The factors Change Resistance, Sprint Management, Relative Advantage, and Complexity are shown to have a significant linear relationship to Scrum as perceived by Scrum Practitioners working within South African organizations. Future research could incorporate a larger population sample to improve the generalizability of the findings.

[1]  K. Sheehan Online Research Methodology* , 2002 .

[2]  B. Gillham Developing a Questionnaire , 2000 .

[3]  John H. Bishop,et al.  The Recognition and Reward of Employee Performance , 1987, Journal of Labor Economics.

[4]  Tor Erlend Fægri Adoption of Team Estimation in a Specialist Organizational Environment , 2010, XP.

[5]  Maureen Tanner,et al.  Software quality assurance in Scrum: The need for concrete guidance on SQA strategies in meeting user expectations , 2013, 2013 International Conference on Adaptive Science and Technology.

[6]  Dean Leffingwell,et al.  Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise , 2011 .

[7]  James Y. L. Thong,et al.  Acceptance of Agile Methodologies: A Critical Review and Conceptual Framework , 2009, Decis. Support Syst..

[8]  L. Chan,et al.  The adoption of new technology: the case of object-oriented computing in software companies , 2000, IEEE Trans. Engineering Management.

[9]  Scott Millett,et al.  Pro Agile .NET Development with SCRUM , 2011 .

[10]  James Y. L. Thong,et al.  An Integrated Framework of Individual Acceptance of Agile Methodologies , 2007, PACIS.

[11]  Casper Lassenius,et al.  ScrumBut, But Does it Matter? A Mixed-Method Study of the Planning Process of a Multi-team Scrum Organization , 2013, 2013 ACM / IEEE International Symposium on Empirical Software Engineering and Measurement.

[12]  Rajiv Kishore,et al.  Reconceptualizing Innovation Compatibility as Organizational Alignment in Secondary IT Adoption Contexts: An Investigation of Software Reuse Infusion , 2007, IEEE Transactions on Engineering Management.

[13]  James Noble,et al.  Supporting Self-organizing Agile Teams - What's Senior Management Got to Do with It? , 2011, XP.

[14]  Jeff Sutherland,et al.  The Scrum Guide , 2012 .

[15]  Tore Dybå,et al.  Developing Software with Scrum in a Small Cross-Organizational Project , 2006, EuroSPI.

[16]  Sven Overhage,et al.  What Makes IT Personnel Adopt Scrum? A Framework of Drivers and Inhibitors to Developer Acceptance , 2011, 2011 44th Hawaii International Conference on System Sciences.

[17]  Alan S. Koch,et al.  Agile Software Development: Evaluating the Methods for Your Organization , 2004 .

[18]  Maureen Tanner,et al.  Understanding the structured processes followed by organisations prior to engaging in agile processes: a South African perspective , 2012, South Afr. Comput. J..

[19]  Steve R. Palmer,et al.  A Practical Guide to Feature-Driven Development , 2002 .

[20]  E. Rogers,et al.  Diffusion of Innovations, 5th Edition , 2003 .

[21]  Fred D. Davis,et al.  Investigating Determinants of Software Developers' Intentions to Follow Methodologies , 2003, J. Manag. Inf. Syst..

[22]  Ernest Mnkandla,et al.  Serum Adoption Challenges Detection Model: SACDM , 2018, 2018 Federated Conference on Computer Science and Information Systems (FedCSIS).

[23]  E. Rogers,et al.  Diffusion of innovations , 1964, Encyclopedia of Sport Management.

[24]  Felix Flentge,et al.  Agile Technical Management of Industrial Contracts: Scrum Development of Ground Segment Software at the European Space Agency , 2011, XP.

[25]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[26]  Tore Dybå,et al.  Escalation of Commitment: A Longitudinal Case Study of Daily Meetings , 2012, XP.

[27]  Gareth R. Jones,et al.  Understanding and Managing Organizational Behavior , 1995 .

[28]  Ernest Mnkandla,et al.  Factors that contribute significantly to Scrum adoption , 2019, 2019 Federated Conference on Computer Science and Information Systems (FedCSIS).

[29]  Ruven E. Brooks,et al.  Studying programmer behavior experimentally: the problems of proper methodology , 1980, CACM.

[30]  Celestina Bianco Agile and SPICE Capability Levels , 2011, SPICE.

[31]  Frederik Ahlemann,et al.  Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature , 2013, Int. J. Inf. Manag..

[32]  Fowler,et al.  Survey research methods, 2nd ed. , 2009 .