Conflict in the agile development: perspective from the SCRUM
Keywords:
SCRUM, conflict, work teams, agile methodologiesAbstract
The present article seeks to raise a discussion about the importance of conflict asa tool for continuous improvement within teams that work under the softwaredevelopment methodology known as SCRUM. It consists of a research study ofqualitative type, which presents the results of a documentary research, besides aseries of interviews carried out among thirteen people who carry a Role of ScrumMaster within one of the most important software development companies inColombia. The most important conclusion is the interviewees’ assessment of theconflict as a dynamic that encourages maturation and continuous improvementin work teams using agile development methodologies.
References
Agile Alliance (2001a). History: The Agile Manifesto. Obtenido de http://agilemanifesto.org/history.html
Agile Alliance (2001b). Principios del Manifiesto Ágil. Obtenido de http://agilemanifesto.org/iso/es/principles.html
Beck, K., Beedle, M., Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M. y otros (2001). Manifiesto por el Desarrollo Ágil de Software. Obtenido de http://agilemanifesto.org/iso/es/manifesto.html
Bell, T. E. & Thayer, T. A. (13 de 10 de 1976). Software requirements: Are they really a problem? ICSE ‘76 Proceedings of the 2nd international conference on Software engineering, 61-68.
Boehm, B. W. (1988). A Spiral Model of Software Development and Enhancement. Computer, 21 (5), 61-72.
Beynon-Davies, P., Carne, C., Mackay, H., & Tudhope, D. (1999). Rapid application development (RAD): an empirical review. European Journal of Information Systems, 8 (3), 211-223.
Crock, P. (2008). Best Practices for Software Projects - JAD Sessions.
Deemer, P., Benefield, G., Larman, C., & Vodde, B. (2012). Scrum Primer: Una introducción básica a la teoría y práctica de Scrum. Recuperado el 25 de 10 de 2016, de Scrum Primer: http://scrumprimer.org/scrumprimer20.pdf
Fowler, M. & Highsmith, J. (2011). The Agile Manifesto. Software Develpment Magazine , 9, 28-35.
Gacitúa Bustos, R. A. (2003). Métodos de desarrollo de software: El desafío pendiente de la estandarización. Theoria, 12, 23-42.
Gonzáles, D. y López, F. (2012). Poder y conflicto en la organización: Una aproximación desde el tratamiento funcionalista de los libros de texto. En: S. Arcand, R. Muñoz, J. Facal, J. Dupuis u F. E. EAFIT (Ed.), Sociología de la empresa. Del marco histórico a las dinámicas internas. Bogota: Siglo del Hombre.
Grupo ISSI (2003). Metodologías Ágiles en el Desarrollo de Software. VIII Jornadas de Ingeniería del Software y Bases de Datos/
Jian, Z. (2005). Why IT Projects Fail. Computerworld, 39 (6), 31-31
Kinnander, M. (2011). Conflict Management How to manage functional conflicts within project teams. Unpublished dissertation, Nurthumbria University, Sweden
Martínez-Corts, I., Boz, M., Medina, F. J., Benítez, M. y Munduate, L. (2011. Afrontamiento de conflicto interpersonal en el trabajo en pequeñas empresas: el papel moderador del apoyo del supervisor y del compañero. Revista de Psicología del Trabajo y de las Organizaciones, vol.27 no.2 Madrid ago. 2011. Pp.117-129.
Standish Group. (2015). 2015 CHAOS Report. Recuperado de https://www.standishgroup.com/store/services/chaos-report- 2015-blue-pm2gomembership.html.
Royce, W. W. (1970). Managing the development of large software systems. En: Proceedings of IEEE WESCON, 26 (8), 328-338.
Rational Unified Process. (2001). Best practices for software development teams. A Rational Software Corporation White Paper. Recuperado de: https://www.ibm.com/developerworks/rational/library/content/03July/1000/1251/1251_bestpractices_TP026B.pdf
VersionOne. (2016). 10th Annual State of Agile Report. Obtenido de https://versionone.com/pdf/VersionOne-10th-Annual-State-of-Agile-Report.pdf
Paetsch, F., Eberlein, A. & Maurer, F. (2003). Requirements Engineering and Agile Software Development. Proceedings of Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises (WETICE). Linz, Austria.
Riehle , D. (2001). A comparison of the value systems of adaptive software development and extreme programming: how methodologies may learn from each other. En: G. Succi & M. Marchesi, Extreme programming examined. Boston, MA, USA: Addison-Wesley Longman Publishing Co.
Scrum.Org. (2014). The Scrum Guide. Recuperado de https://www.scrumalliance.org/why-scrum/scrum-guide
Schwaber, K., & Sutherland, J. (2016). The Definitive Guide to Scrum: The Rules of the Game. Berna, Suiza: Scrum.org.
Nazareno, R., Leone, H. y Gonnet, S. (2013). Trazabilidad de Procesos Ágiles: un Modelo para la Trazabilidad de Procesos
Scrum. XVIII Congreso Argentino de Ciencias de la Computación. Universidad Nacional de La Rioja, La Rioja, Argentina 2013 Scrum.org. (2016). Scrum Framework. Recuperado de https://www.scrum.org/Portals/0/Documents/Collateral/ScrumFramework_17x11.pdf
Michael, J., Maurer, F. & Tessem, B. (2005). Human and social factors of software engineering: workshop summary. ACM SIGSOFT Software Engineering Notes, 30 (4), 1-6. Crawford, B., Soto, R., Leon de la Barra, C.,
Crawford, K., & Olguin, E. (2014). Agile software teams can use conflict to create a better product. Communications in Computer and Information Science, 434, 24-29.
Karn, J. (2008). An ethnographic study of conflict in software engineering teams. Journal of Information, Information Technology & Organizations, 3, 106-133.
Jehn, K. & Mannix, E. (2001). The dynamic nature of conflict: a longitudinal study of intragroup conflict and group performance. Academy Of Management Journal, 44 (2), 238-251.
West, M. & Anderson, N. (1996). Innovation in top management teams. Journal Of Applied Psychology , 81(6), 680-694.
Jehn, K., Northcraft, G. & Neale, M. (1999). Why Differences Make a Difference: A Field Study of Diversity, Conflict, and Performance in Workgroups. Administrative Science Quarterly , 44(4), 741-76.
Turner, M. & Pratkanis, A. (1994). Social identity maintenance prescriptions for preventing groupthink reducing identity protection and enhancing intelectual conflict. International Journal Of Conflict Management , 5(3), 254-270.
