The Effect of Team Size and Dynamics on Agile Estimation
Agile estimation
DOI:
https://doi.org/10.36676/irt.v9.i5.1478Keywords:
team size, Agile estimation, team dynamics, software development, Planning Poker, story points, psychological safety, velocityAbstract
This paper presents the impact of team size and dynamics on agile estimation accuracy and strategies for improving estimation in diversified teams. We employed a mixed-method approach with online surveys, interviews, and case studies. The data received and analyzed in this research came from 150 agile teams representing different industries. Our results show that strong interdependency exists between team size and the dispersion of estimations. The best estimation accuracy was when the team had 5-9 members. Team dynamics, particularly cohesion and psychological safety, emerged as important in the estimation outcome. Based on these insights, we propose a framework for improving estimation practice within agile teams, including tailoring and continuous improvement.
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Albrecht, A. J. (1979). Measuring application development productivity. In Proceedings of the Joint SHARE/GUIDE/IBM Application Development Symposium (Vol. 10, pp. 83-92).
Beck, K., Beedle, M., Van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., ... & Thomas, D. (2001). Manifesto for agile software development.
Boehm, B. W. (1981). Software engineering economics. Prentice-hall Englewood Cliffs (NJ), 197.
Brooks Jr, F. P. (1995). The mythical man-month (anniversary ed.). Addison-Wesley Longman Publishing Co., Inc.
Cohn, M. (2005). Agile estimating and planning. Pearson Education.
Dikert, K., Paasivaara, M., & Lassenius, C. (2016). Challenges and success factors for large-scale agile transformations: A systematic literature review. Journal of Systems and Software, 119, 87-108.
Drury, M., Conboy, K., & Power, K. (2012). Obstacles to decision making in Agile software development teams. Journal of Systems and Software, 85(6), 1239-1254.
Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative science quarterly, 44(2), 350-383.
Grenning, J. (2002). Planning poker or how to avoid analysis paralysis while release planning. Hawthorn Woods: Renaissance Software Consulting, 3, 22-23.
Jørgensen, M., & Shepperd, M. (2007). A systematic review of software development cost estimation studies. IEEE Transactions on software engineering, 33(1), 33-53.
Melo, C. O., Cruzes, D. S., Kon, F., & Conradi, R. (2013). Interpretative case studies on agile team productivity and management. Information and Software Technology, 55(2), 412-427.
Molokken-Ostvold, K., & Haugen, N. C. (2007). Combining estimates with planning poker—an empirical study. In 2007 Australian Software Engineering Conference (ASWEC'07) (pp. 349-358). IEEE.
Schwaber, K., & Sutherland, J. (2020). The scrum guide. Scrum Alliance.
Usman, M., Mendes, E., Weidt, F., & Britto, R. (2014). Effort estimation in agile software development: a systematic literature review. In Proceedings of the 10th International Conference on Predictive Models in Software Engineering (pp. 82-91).
VersionOne. (2020). 14th annual State of Agile report. Digital.ai.
Yin, R. K. (2018). Case study research and applications: Design and methods. Sage publications.
Swamy, H. (2020). Unsupervised machine learning for feedback loop processing in cognitive DevOps settings. Yingyong Jichu yu Gongcheng Kexue Xuebao/Journal of Basic Science and Engineering, 17(1), 168-183. https://www.researchgate.net/publication/382654014
Downloads
Published
How to Cite
Issue
Section
License
Copyright (c) 2023 Innovative Research Thoughts
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.
