ABSTRACT
Agile project management models are notorious in current software development. However, distributed teams pose management challenges, such as the need for effective communication and collaboration tools and the difficulty of monitoring progress and work quality. This paper presents the Agile Management Model for Distributed Software Development Teams (AgiTeD), a Scrum-inspired framework grounded on transparency, inspection, adaptation, and quality. AgiTeD defines four roles, six events within the development cycle, and seven artifacts. We applied the proposed model to a distributed team and surveyed 23 developers working remotely on eight different projects of an organization. The developers highlighted some positive facets of AgiTeD for better supporting the work of distributed software development teams, emphasizing the Agile Leader role to ensure the full implementation of the model, the proposed cycle and its events, and the Repository and Communication Rules artifact to organize the teamwork.
- Kent Beck 2001. Manifesto for Agile Software Development. https://agilemanifesto.org/Google Scholar
- Kushal Bundhun and Roopesh Kevin Sungkur. 2022. Formulation and development of a novel framework to overcome communication challenges in agile distributed teams. International Journal of Information Systems and Change Management 13, 1 (2022), 45–72. https://doi.org/10.1504/ijiscm.2022.127060Google ScholarDigital Library
- Mike Cohn. 2006. Agile estimating and planning. Addison-Wesley/Pearson Education, Inc., USA.Google ScholarDigital Library
- Ronnie E. de Souza Santos and Paul Ralph. 2022. A grounded theory of coordination in remote-first and hybrid software teams. In Proceedings of the 44th International Conference on Software Engineering. ACM, USA, 25–35. https://doi.org/10.1145/3510003.3510105Google ScholarDigital Library
- Victor Temitayo Faniran, Abdulbaqi Badru, and Nurudeen Ajayi. 2017. Adopting Scrum as an agile approach in distributed software development: A review of literature. In Proceedings of the 1st International Conference on Next Generation Computing Applications. IEEE, USA, 36–40. https://doi.org/10.1109/NEXTCOMP.2017.8016173Google ScholarCross Ref
- Cristiano P. Godoy, Andre F. Cruz, Elisangela P. Silva, Lanier M. Santos, Rafael S. Zerbini, and Cícero A. L. Pahins. 2019. Blueprint Model: A new approach to Scrum agile methodology. In Proceedings of the ACM/IEEE 14th International Conference on Global Software Engineering (ICGSE). IEEE, USA, 95–99. https://doi.org/10.1109/ICGSE.2019.00014Google ScholarDigital Library
- Michal Hron and Nikolaus Obwegeser. 2022. Why and how is Scrum being adapted in practice: A systematic review. Journal of Systems and Software 183 (2022). https://doi.org/10.1016/j.jss.2021.111110Google ScholarCross Ref
- Youry Khmelevsky, Xitong Li, and Stuart Madnick. 2017. Software development using agile and Scrum in distributed teams. In Proceedings of the 2017 Annual IEEE International Systems Conference. IEEE, USA. https://doi.org/10.1109/SYSCON.2017.7934766Google ScholarCross Ref
- Johan Linåker, Sardar Muhammad Sulaman, Rafael Maiani de Mello, and Martin Höst. 2015. Guidelines for conducting surveys in Software Engineering. Technical Report. Department of Computer Science, Lund University, Sweden.Google Scholar
- Pernille Lous, Marco Kuhrmann, and Paolo Tell. 2017. Is Scrum fit for Global Software Engineering?. In Proceedings of the IEEE 12th International Conference on Global Software Engineering. IEEE, USA. https://doi.org/10.1109/ICGSE.2017.13Google ScholarDigital Library
- Pernille Lous, Paolo Tell, Christian Bo Michelsen, Yvonne Dittrich, and Allan Ebdrup. 2018. From Scrum to Agile: A journey to tackle the challenges of distributed development in an agile team. In Proceedings of the 2018 International Conference on Software and System Process. ACM, USA, 11–20. https://doi.org/10.1145/3202710.3203149Google ScholarDigital Library
- Jefferson Seide Molléri, Kai Petersen, and Emilia Mendes. 2016. Survey guidelines in Software Engineering: An annotated review. ACM, USA. https://doi.org/10.1145/2961111.2962619Google ScholarDigital Library
- Lene Pries-Heje and Jan Pries-Heje. 2011. Why Scrum works: A case study from an agile distributed project in Denmark and India. In Proceedings of the 2011 Agile Conference. IEEE, USA, 20–28. https://doi.org/10.1109/AGILE.2011.34Google ScholarDigital Library
- Project Management Institute. 2021. A Guide to the Project Management Body of Knowledge and the Standard for Project Management (7th ed.). PMI, USA.Google Scholar
- Ken Schwaber and Jeff Sutherland. 2020. The Scrum Guide. ScrumGuides.org. https://scrumguides.orgGoogle Scholar
- Basit Shahzad, Wardah Naeem Awan, Fazal e Amin, Ahsanullah Abro, Muhammad Shoaib, and Sultan Alyahya. 2023. Framework for effective utilization of distributed Scrum in software projects. Computer Systems Science and Engineering 44, 1 (2023), 407–422. https://doi.org/10.32604/csse.2023.022601Google ScholarCross Ref
- Jeff Sutherland, Anton Viktorov andJack Blount, and Nikolai Puntikov. 2007. Distributed Scrum: Agile project management with outsourced development teams. In Prioceedings of the 40th Annual Hawaii International Conference on System Sciences. IEEE, USA. https://doi.org/10.1109/HICSS.2007.180Google ScholarDigital Library
- Sulabh Tyagi, Ritu Sibal, and Bharti Suri. 2022. Empirically developed framework for building trust in distributed agile teams. Information and Software Technology 145 (2022). https://doi.org/10.1016/j.infsof.2022.106828Google ScholarDigital Library
Index Terms
- An Agile Management Model for Distributed Software Development Teams
Recommendations
Adopting to Agile Software Development
Abstract Agile software development can be made successful, but there is no well-defined way how to achieve this. The problem is that the successful adoption of agile methods and practices is a complex process and this process should be customizable for ...
An agile v-model for medical device software development to overcome the challenges with plan-driven software development lifecycles
SEHC '13: Proceedings of the 5th International Workshop on Software Engineering in Health CareThrough the use of semi structured interviews with medical device software organizations it emerged that medical device software organizations are experiencing difficulties when following plan driven Software Development Life Cycles (SDLC), particularly ...
Agile vs. structured distributed software development: A case study
In globally distributed software development, does it matter being agile rather than structured? To answer this question, this paper presents an extensive case study that compares agile (Scrum, XP, etc.) vs. structured (RUP, waterfall) processes to ...
Comments