Factors Models of Scrum Adoption in the Software Development Process: A Systematic Literature Review - Modelos de Factores en la Adopción de Scrum in el Proceso de Desarrollo de Software. Una Revisión Sistemática de la Literatura
DOI:
https://doi.org/10.32870/recibe.v7i1.97Keywords:
Software Process Model, Process Adoption, Agile Software Development, Systematic Literature ReviewAbstract
(Background) The adoption of Agile Software Development (ASD), in particular Scrum, has grown significantly since its introduction in 2001. However, in Lima, many ASDs implementations have been not suitable (uncompleted or inconsistent), thus losing benefits obtainable by this approach and the critical success factors in this context are unknown. (Objective) To analyze factors models used in the evaluation of the adoption of ASDs, as these factors models can contribute to explaining the success or failure of these adoptions. (Method) In this study we used a systematic literature review. (Result) Ten models have been identified; their similarities and differences are presented. (Conclusion) Each model identified consider different factors, however some of them are shared by five of these models, such as team member attributes, engaging customer, customer collaboration, experience and work environment Resumen: (Antecedentes).La adopción del Desarrollo de Software Agile (DSA), en particular Scrum, ha crecido significativamente desde su introducción en 2001. Sin embargo, en Lima, muchas implementaciones de DSA no han sido adecuadas (incompletas o inconsistentes), perdiendo así los beneficios que se pueden obtener con este enfoque y los factores de éxito críticos en este contexto son desconocidos. (Objetivo) Analizar los modelos de factores utilizados en la evaluación de la adopción de ASD, ya que estos modelos de factores pueden contribuir a explicar el éxito o el fracaso de estas adopciones. (Método) En este estudio, utilizamos una revisión sistemática de la literatura. (Resultado) Diez modelos han sido identificados; sus similitudes y diferencias son presentadas. (Conclusión) Cada modelo identificado considera diferentes factores, sin embargo, algunos de ellos son compartidos por cinco de estos modelos, tales como los atributos del miembro del equipo, el compromiso del cliente, la colaboración del cliente, la experiencia y el entorno laboral. Palabras Clave: Modelo de Proceso Software, Adopción de Proceso, Desarrollo de Software Agile, Revisión Sistemática de la Literatura.References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2002). Agile Software development methods. Review and analysis. Finland: VTT Publications.
Agile Alliance. (06 de 04 de 2016). What is Agile Software Development? Obtenido de https://www.agilealliance.org/agile101/what-is-agile/
Agile Manifesto. (2001). Recuperado el 8 de Aug de 2015, de http://agilemanifesto.org
Ahimbisibwe, A., Cavana, R. Y., & Daellenbach, U. (2015). A contingency fit model of critical success factors for software development projects: A comparison of agile and traditional plan-based methodologies. Journal of Enterprise Information Management, 28(1), 7 - 33.
Azevedo Santos, M. d. (2011). Agile Practices: An Assessment of Perception of Value of Professionals on the Quality Criteria in Performance of Projects. Journal of Software Engineering and Applications - Scientific Research, 4(12), 700-709.
Baddoo, N., & Hall, T. (Apr de 2003). De-motivators for Software Process Improvement: An Analysis of Practitioners’ Views. The Journal of Systems and Software, 66(1), 23–33.
Bohem, B. (Jan de 2002). Get ready for agile methods, with care. Computer, 35(1), 64-69.
Cao, L., Mohan, K., Xu, P., & Ramesh, B. (August de 2009). A framework for adapting agile development methodologies. European Journal of Information Systems, 18(4), 332–343.
Chan, K., & Thong, J. (2007). An Integrated Frame-work of Individual Acceptance of Agile Methodologies. Pacific Asia Conference on Information Systems (PACIS) (pág. Paper 154). Auckland, New Zealand: AISEL.
Chow, T., & Cao, D.-B. (Jun de 2008). A survey study of critical success factors in agile software projects. Journal of Systems and Software, 81(6), 961-971.
Conboy, K., & Fitzgerald, B. (June de 2010). Method and developer characteristics for effective agile method tailoring: A study of XP expert opinion. ACM Trans. Softw. Eng. Methodol, 20(1), Paper 2, 30p.
Daghfous, A., & White, G. R. (1994). Information and innovation: a comprehensive representation. Research Policy, 23(3), 267-280.
Dieste, O., Grimán, A., & Juristo, N. (2009). Developing search strategies for detecting relevant experiments. Empirical Software Engineering, 14(5), 513-539.
Dingsøyr, T., Nerur, S., Balijepally, V., & Brede Moe, N. (Jun de 2012). A decade of agile methodolo-gies: Towards explaining agile software development. Journal of Systems and Software, Elsevier, 85(6), 1213–1221.
Dubakow, M. (10 de 2010). 10 Most Common Mistakes in Agile Adoption. Recuperado el 06 de 04 de 2016, de Targetprocess Inc: https://www.targetprocess.com/blog/2010/10/10-most-common-mistakes-in-agile-adoption-part-i/
Dyba, T. (Set-Oct de 2000). Improvisation in Small Software Organizations. IEEE Software, 17(5), 82–87.
Dyba, T. (May de 2005). An empirical investigation of the key factors for success in software process improvement. IEEE Transactions on Software Engineering, 31, 410-424.
El Emam, K., Goldenson, D., McCurley, J., & Herbsleb, J. (1998). Success or Failure? Modeling the Likelihood of Software Process Improvement. International Software Engineering Research Network, ISERN-98-15. ISERN-98.
Elberzhager, F., Münch, J., & Vi, T. (Jan de 2012). A systematic mapping study on the combination of static and dynamic quality assurance techniques. Information and Software Technology, 54(1), 1-15.
Fichman, R. G., & Kemerer, C. F. (1999). The Illusory Diffusion of Innovations: An Examination of Assimilation Gaps. Information Systems Research, 10(3), 255 - 275.
Goodman, P. (1996). The Practical Implementation of Process Improvement Initiatives. En N. Fenton, R. Whitty, & Y. Lizuka (Edits.), Software Quality Assurance and Measurement: A Worldwide Perspective (pág. 315). International Thomson Computer Press.
Hajjdiab, H., & Taleb, A. (Sep de 2011). Adopting Agile Software Development: Issues and Challenges. International Journal of Managing Value and Supply Chains (IJMVSC), 2(3).
Hass, K. B. (10 de March de 2009). The Blending of Traditional and
Agile Project Management. Recuperado el 06 de September de 2015, de PM Times for Projects Managers: https://www.projecttimes.com/articles/the-blending-of-traditional-and-agile-project-management.html.
Highsmith, J., & Cockburn, A. (Sep de 2001). Agile software development: the business of innovation. Computer, 34(9), 120-127.
Imreh, R., & Raisinghani, M. S. (Oct de 2011). Impact of Agile Software Development on Quality within Information Technology Organizations. Journal of Emerging Trends in Computing and Information Sciences, 2(10).
Kanane, A. (2014). Challenges related to the adoption of Scrum. Case study of a financial IT company. UMEA University, Department of informatics. IT management master program. UMEA University.
Kasse , T., & McQuaid, P. A. (Aug de 2000). Factors Affecting Process Improvement Initiatives. Crosstalk: the Journal of De-fense Software Engineering, 13(8), 4-8.
Kitchenham, B. (2007). Guidelines for performing Systematic Literature Reviews in Software Engineering. EBSE Technical Report. EBSE-2007-01, Keele University , School of Computer Science and Mathematics.
Kumar, G., & Kumar Bhatia, P. (2012). Impact of Agile Methodology on
Software Development Process. International Journal of Computer Technology and Electronics Engineering (IJCTEE), 2(4), 46-50.
Lee, R. (2012). The Success Factors of Running Scrum: a Qualitative Perspective. Journal of Software Engineering and Applications, 5(6), 367-374.
Mann, C., & Maurer, F. (2005). A Case Study on the Impact of Scrum on Overtime and Customer Satisfaction. Agile Development Conference (ADC‘05), (págs. 70-79).
Mark, P. (2011). On empirical research into scrum. Institute for Software Research Carnegie Mellon University, Pittsburgh. Obtenido de http://www.cs.cmu.edu/~mcp/agile/oersa.pdf
Melo, C., Cruzes, D. S., Kon, F., & Conradi, R. (Feb de 2013). Interpretative case studies on agile team productivity and management. Information and Software Technology, 55(2), 412–427.
Mishra, D., & Mishra, A. (Jan de 2011). Complex software project development: agile methods adoption. Journal of Softwrae Maintenance and Evolution: Research and Practice, 549–564.
Misra, S. C., Kumar, V., & Kumar, U. (Nov. de 2009). Identifying some important success factors in adopting agile software development practices. Journal of Systems and Software, 82(11), 1869-1890.
Niazi, M., Wilson, D., & Zowghi, D. (2006). Critical Success Factors for Software Process Improvement Implementation: An Empirical Study. Software Process: Improvement and Practice, 11(2), 193-211.
Overhage, S., Sebastian, S., Birkmeier, D., & Miller, J. (2011). What Makes IT Personnel Adopt Scrum? A Framework of Drivers and Inhibitors to Developer Acceptance. 44th Hawaii International Conference on System Sciences (HICSS), (págs. 1-10). Kauai.
Oyeyipo, E. (2011). An empirical study of requirements management in an agile-Scrum development enviroment. Thesis Master of Sciemce, Universidad San Marcos, Department of Computer Science, Texas.
Pagrut, D. (2008). The Impact of an Agile Scrum on Software Testing: A Case Study of Tech Mahindra Limited. 5th International Conference On Software Testing. STeP-IN SUMMIT.
Powell, T. C. (1995). Total Quality Management as Competitive Advantage: A Review and Empirical Study. Strategic Management Journal, 16, 15-37.
Repenning, N. P., & Sterman, J. D. (Summer de 2001). Nobody Ever Gets Credit for Fixing Problems that Never Happened: Creating and Sustaining Process Improvement. California Management Review, 43(4), 64-88.
Rogers, E. M. (2003). Diffusion of Innovations (Fifth Edition ed.). New York: The Fnree Press.
Rousseau, D. M., & McCarthy, S. (Mar de 2007). Educating Managers From an Evidence-Based Perspective. Academy of Management Learning & Education, 6(1), 84-101.
Santos, C., Pimenta, C., & Nobre, M. (2007). A estratégia PICO para a construção da pergunta de pesquisa e busca de evidências. Revista Latino-Americana de Enfermagem, 15(3), 508-511.
Shahane, D., Jamsandekar, P., & Shahane, D. (2014). Factors influencing the agile methods in practice - Literature survey & review. International Conference on Computing for Sustainable Global Development (INDIACom), (págs. 556-560). New Delhi.
Srinivasan, J., Dobrin, R., & Lundqvist, K. (2009). 'State of the Art' in Using Agile Methods for Embedded Systems Development. 33rd IEEE International Annual Conference on Computer Software and Applications, (págs. 522-527). Seattle.
Stankovic, D., Nikolic, V., Djordjevic, M., & Cao, D.-B. (June de 2013). A survey study of critical success factors in agile software projects in former Yugoslavia IT companies. Journal of Systems and Software, 86(6), 1663-1678.
Stettina, C., & Heijstek, W. (2011). Five Agile Factors: Helping Self-management to Self-reflect. 18th European Conference on Systems, Software and Service Process Improvement, EuroSPI 2011, (págs. 84-96). Roskilde: EuroSPI .
Sulayman, M., & Mendes, E. (2009). A Systematic Literature Review of Software Process Improvement in Small and Medium Web Companies. International Conference on Advanced Software Engineering and Its Applications, ASEA. 59, págs. 1-8. Jeju Island: Springer.
Zhang, X., Hu, T., Dai, H., & Li, X. (2010). Software Development Methodologies, Trends, and Implications. Southern Association for Information Systems Conference (pág. Paper 31). SAIS.
