MEAC: An experience to keep the production line active in the software development process
Abstract
Software development is not an easy process. Proof of this is the existence of numerous methodological proposals that have proven to be practical and efficient in a large number of projects. However, these methodologies have also presented problems in aspects of their application. To such an extent that they often need to be adapted to the realities of each project or company in order to improve the results obtained in their application. The aim of this article is to tell a real experience in a small development company in which several methodologies have been applied over the years, highlighting Scrum as the one that has brought better results. However, by applying it specifically to small projects, with few resources, limited times and changing requirements, the need to also adapt to this methodology for this type of project was born. We have called this adaptation MEAC, acronym that refers to an Empirical Method of Continuous Support whose purpose is to avoid time cuts in the generation and development of the software product, as well as to maintain the active production line of the software team active.
Resumen: El desarrollo de software no es un proceso fácil. Prueba de ello, es la existencia de numerosas propuestas metodológicas que han demostrado ser prácticas y eficientes en un gran número de proyectos. No obstante, estas metodologías también han presentado problemas en aspectos de su aplicación. A tal punto que, muchas de las veces se necesitan adaptarlas a realidades propias de cada proyecto o empresa con el fin de mejorar los procesos de desarrollo de software y obtener un producto de calidad. El objetivo de este artículo es contar una experiencia real en una empresa pequeña de desarrollo en la cual se ha aplicado varias metodologías al largo de los años, destacándose Scrum como la que mejores resultados ha traído. Sin embargo, al aplicarla específicamente en proyectos pequeños, con pocos recursos, tiempos limitados y requisitos cambiantes, ha nacido la necesidad de también adaptar a esta metodología para este tipo de proyectos. A esta adaptación la hemos llamado MEAC, siglas que se refieren a un Método Empírico de Apoyo Continuo cuya finalidad es evitar cortes de tiempo en la generación y desarrollo del producto software, así como mantener activa la línea de producción activa del equipo de software.
References
[1] A. Bakhtouchi and R. Rahmouni, ``A Tree Decision Based Approach for Selecting Software Development Methodology,'' in 2018 International Conference on Smart Communications in Network Technologies (SaCoNeT), El Oued, 2018, pp. 211–216.
[2] N. Keshta and Y. Morgan, ``Comparison between traditional plan-based and agile software processes according to team size & project domain (A systematic literature review),'' in 2017 8th IEEE Annual Information Technology, Electronics and Mobile Communication Conference (IEMCON), Vancouver, BC, 2017, pp. 567–575.
[3] R. Bin-Hezam, A. Bin-Essa, and N. F. Abubacker, ``Is the Agile Development Method the Way to Go for Small to Medium Enterprises (SMEs) In Saudi Arabia?,'' in 2018 21st Saudi Computer Society National Computer Conference (NCC), Riyadh, 2018, pp. 1–6.
[4] B. M. Montero, H. V. Cevallos, and J. D. Cuesta, ``Agile methodologies against traditional methods in the software development process.,'' p. 10.
[5] J. P. Z. Gamboa and C. A. L. Arreaga, ``Evolución de las Metodologías y Modelos utilizados en el Desarrollo de Software. Evolution of the Methodologies and Models used in Software Development.,'' vol. 3, no. 10, p. 14, 2018.
[6] L. R. Vijayasarathy and C. W. Butler, ``Choice of Software Development Methodologies: Do Organizational, Project, and Team Characteristics Matter?,'' IEEE Softw., vol. 33, no. 5, pp. 86–94, Sep. 2016.
[7] K. Curcio, R. Santana, S. Reinehr, and A. Malucelli, ``Usability in agile software development: A tertiary study,'' Comput. Stand. Interfaces, vol. 64, pp. 61–77, May 2019.
[8] E. T. Mushashu and J. S. Mtebe, ``Investigating Software Development Methodologies and Practices in Software Industry in Tanzania,'' in 2019 IST-Africa Week Conference (IST-Africa), Nairobi, Kenya, 2019, pp. 1–11.
[9] H. Alahyari, R. Berntsson Svensson, and T. Gorschek, ``A study of value in agile software development organizations,'' J. Syst. Softw., vol. 125, pp. 271–288, Mar. 2017.
[10] L. N. M. Velandia and W. M. L. López, ``ESCOGER UNA METODOLOGÍA PARA DESARROLLAR SOFTWARE, DIFÍCIL DECISIÓN,'' Rev. Educ. En Ing., vol. 10, p. 12, 2015.
[11] K. Kaur and A. Jajoo, ``Applying Agile Methodologies in Industry Projects: Benefits and Challenges,'' in 2015 International Conference on Computing Communication Control and Automation, Pune, India, 2015, pp. 832–836.
[12] B. L. Romano and A. D. da Silva, ``Project Management Using the Scrum Agile Method: A Case Study within a Small Enterprise,'' in 2015 12th International Conference on Information Technology - New Generations, Las Vegas, NV, USA, 2015, pp. 774–776.
[13] A. Srivastava, S. Bhardwaj, and S. Saraswat, ``SCRUM model for agile methodology,'' in 2017 International Conference on Computing, Communication and Automation (ICCCA), Greater Noida, 2017, pp. 864–869.
[14] J. D. Y. González and S. G. Gómez, ``Revisión sistemática acerca de la implementación de metodologías ágiles y otros modelos en micro, pequeñas y medianas empresas de software,'' p. 16.
[15] T. Miles-Board, ``Poster: An Empirical Study of the Product Owner Role in Scrum,'' p. 2.
[16] A. M. G. Rodríguez, Y. T. Casañola, and A. P. Vergara, ``Optimización de estados en la mejora de procesos de software,'' p. 20.
[17] ``Establecimiento del estado del arte sobre el aligeramiento de procesos de software,'' RISTI - Rev. Ibérica Sist. E Tecnol. Informação, no. 17, Mar. 2016.
[18] A. N. Cadavid, ``Revisión de metodologías ágiles para el desarrollo de software,'' Prospectiva, vol. 11, no. 2, p. 30, Sep. 2013.
[19] G. P. Tomaselli, C. J. Acuña, M. Estayno, and C. Lenkovich, ``SCRUM: Una revisión de la literatura,'' p. 11.
[20] C. Rodríguez and R. Dorado, ``¿Por qué implementar Scrum?,'' Rev. Ontare, vol. 3, no. 1, p. 125, Oct. 2015.
[21] G. Matturro, F. Cordovés, and M. Solari, ``An exploratory study of the role of Product Owner in industrial practice,'' p. 12.
[22] V. P. Díaz-Narváez V.P. and A. Calzadilla-Núñez A., ``Artículos científicos, tipos de investigación y productividad científica en las Ciencias de la Salud,'' Cienc. Salud, vol. 14, no. 1, pp. 115–121, Feb. 2016.
[23] M. P. Polo, ``Ceremonial y protocolo: métodos y técnicas de investigación científica,'' p. 21, 2015.
[24] J. Vlietland and H. van Vliet, ``Towards a governance framework for chains of Scrum teams,'' Inf. Softw. Technol., vol. 57, pp. 52–65, Jan. 2015.
[25] D. Méndez Fernández and J.-H. Passoth, ``Empirical software engineering: From discipline to interdiscipline,'' J. Syst. Softw., vol. 148, pp. 170–179, Feb. 2019.
[26] ``Industria de Software,'' p. 45.