Show simple item record

dc.contributor.authorAziz Butt, Shariqspa
dc.contributor.authorKhalid, Ayeshaspa
dc.contributor.authorErcan, Tuncayspa
dc.contributor.authorAriza Colpas, Paola Patriciaspa
dc.contributor.authorAcosta-Coll, Melisaspa
dc.contributor.authorPiñeres Espitia, Gabriel Dariospa
dc.contributor.authorDe-La-Hoz-Franco, Emirospa
dc.contributor.authorPiñeres Melo, Marlon Albertospa
dc.contributor.authorMorales Ortega, Robertospa
dc.date.accessioned2022-09-19T13:56:54Z
dc.date.available2024
dc.date.available2022-09-19T13:56:54Z
dc.date.issued2022
dc.identifier.citationShariq Aziz Butt, Ayesha Khalid, Tuncay Ercan, Paola Patricia Ariza-Colpas, Acosta-Coll Melisa, Gabriel Piñeres-Espitia, Emiro De-La-Hoz-Franco, Marlon Alberto Pineres Melo, Roberto Morales Ortega, A software-based cost estimation technique in scrum using a developer's expertise, Advances in Engineering Software, Volume 171, 2022, 103159, ISSN 0965-9978, https://doi.org/10.1016/j.advengsoft.2022.103159.spa
dc.identifier.issn0965-9978spa
dc.identifier.urihttps://hdl.handle.net/11323/9521spa
dc.description.abstractBackground: Scrum methodology is the most useful and adopted part of the agile methodology. Many organizations are adopting Scrum for the last decade to meet their software requirements. It is facilitating the software industries to develop software applications according to the user’s requirements. Objective: Scrum helps to fulfill the customer’s requirements by interacting with the client and developer. Instead of this, scrum still has some challenges that influence the cost of a scrum. These challenging factors include coordination, team size, change request, complexity, and issues in daily meeting sessions. Due to these factors mostly the cost and time exceed scrum-based projects. To overcome these issues from the accurate and precise estimation in the scrum project we have developed a web-based software system to estimate the effort of a user story as well as the budget. Methodology: There are some sophisticated cost estimation techniques for scrum-based projects. But all estimation techniques have some limitations that make them less useful for estimation and overcoming the effects of these factors in the scrum. We have surveyed the multiple software industries to get the static findings of the survey. We have designed the 30 hypotheses that main aim to reveal how much the proposed estimation technique is valuable for the accuracy of estimation. For the inclusion of participants, we have set the age criteria to get the opinions of the most experienced programmers. Results: The main aim of this paper is to provide knowledge about key challenging factors in Scrum that cause exceed in cost and time, and also briefly explain why existing scrum cost estimation techniques are not pertinent for projects. In the last, we propose a framework as a solution to manage these factors and control cost and time from exceeding. We also adopted this estimation technique in different case studies in software industries for findings and results. The technique calculates the efforts autonomously. We design a software-based estimation technique that collects inputs from team/s and estimates the cost and time of a project. Conclusion: In outcomes, we found that our cost estimation approach reduced the issues from scrum software project development and make it more proficient for estimation of projects. Our proposed estimation technique introduced the new concept of estimation that facilitate the client, software industry, and developers as well to meet the requirements of the client, fulfill the changes during the sprints/s development and deliver the project within the time and cost.eng
dc.format.extent17 páginasspa
dc.format.mimetypeapplication/pdfspa
dc.language.isoeng
dc.publisherElsevier Ltd.spa
dc.rightsAtribución-NoComercial-SinDerivadas 4.0 Internacional (CC BY-NC-ND 4.0)spa
dc.rights© 2022 Elsevier Ltd. All rights reserved.spa
dc.rights.urihttps://creativecommons.org/licenses/by-nc-nd/4.0/spa
dc.titleA software-based cost estimation technique in scrum using a developer's expertiseeng
dc.typeArtículo de revistaspa
dc.identifier.urlhttps://doi.org/10.1016/j.advengsoft.2022.103159spa
dc.source.urlhttps://www.sciencedirect.com/science/article/pii/S0965997822000709?via%3Dihubspa
dc.rights.accessrightsinfo:eu-repo/semantics/embargoedAccessspa
dc.identifier.doi10.1016/j.advengsoft.2022.103159spa
dc.identifier.eissn1873-5339spa
dc.identifier.instnameCorporación Universidad de la Costaspa
dc.identifier.reponameREDICUC - Repositorio CUCspa
dc.identifier.repourlhttps://repositorio.cuc.edu.co/spa
dc.publisher.placeUnited Kingdomspa
dc.relation.ispartofjournalAdvances in Engineering Softwarespa
dc.relation.references[1] Balaji S, Sundararajan Murugaiyan M. Waterfall vs V-model vs AGILE: life Cycle. Int J Inf Technol Bus Manag 2012;29. June.spa
dc.relation.references[2] Ruparelia NB. Software development lifecycle models. ACM SIGSOFT Softw Eng 2010. May.spa
dc.relation.references[3] Sutherland J. Scrum. a revolutionary approach to building teams, beating deadlines and boosting productivity. Random House Business Books; 2014.spa
dc.relation.references[4] Nuevo ED, Piattini M, Pino FJ. Scrum-based methodology for distributed software development. IEEE Computer Society; 2011.spa
dc.relation.references[5] Suliman SM, Kadoda G. Factors influence that effect the software project cost and schedule estimation. In: Proceedings of the Sudan conference on computer science and information technology (SCCSIT). IEEE; 2017.spa
dc.relation.references[6] Hossain E, Bannerman P, Jeffery R. Towards an understanding of tailoring scrum in global software development: a multi-case study. In: Proceedings of the international conference on software and systems process; 2011.spa
dc.relation.references[7] Moe NB, Dingsoyr T, Dyba T. A teamwork model for understanding an agile team: a case study of a Scrum project. Inf Softw Technol 2010. ELSEVIER.spa
dc.relation.references[8] Anwer F, Aftab S, Shah S, Shah M, Waheed U. Comparative analysis of two popular agile models: extreme programming and scrum. Int J Comput Sci Telecommun 2017;8(2). volumeissueMarch.spa
dc.relation.references[9] Lindsjorn Y, Sjoberg DIK, Dingsoyr T, Bergersen GunnarR, Dyba Tore. Teamwork quality and project success in software development: a survey of agile development teams. J Syst Softw 2016. ELSEVIER.spa
dc.relation.references[10] Stray V, Sjoberg DIK, Dyba T. The daily stand-up meeting: a grounded theory study. J Syst Softw 2016. ELSEVIER.spa
dc.relation.references[11] Kaisti M, Mujunen T, Tuomas M, Rantala V, Lehtonen T. Agile principles in the embedded system development. In: Proceedings of the international conference on agile software development. Springer Italy; 2014.spa
dc.relation.references[12] Miller. The Characteristics of agile software process” Granville together soft. In: Proceedings of the 39th International conference and exhibition on Technology of object-Oriented language and Systems. IEEE; 2001.spa
dc.relation.references[13] Singh Matharu G, Mishra A. Harmeet singh and Priyanka Upadhyay “empirical study of agile software development methodologies: a comparative analysis. In: Proceedings of the ACM SIGSOFT software engineering Notes page 1; 2015. January.spa
dc.relation.references[14] Streule T, Miserini N, Bartlome O, Klippel M, Soto BGD. Implementation of scrum in construction industry. In: Proceedings of the creative construction conference. Elseiver; 2016.spa
dc.relation.references[15] Schwaber K, Beedle M. Agile software development with scrum. Prentice-Hall: Upper Saddle River; 2002.spa
dc.relation.references[16] Sutherland J., Schwaber K., and Sutherl C.J., “The scrum papers: nuts, bolts, and origins of an agile process”, 2007.spa
dc.relation.references[17] Choudhari J., Suman U., “Story Points based effort estimation model for software maintenance”, ELSEVIER, 2011.spa
dc.relation.references[18] Rosa W, Madachy R, Clark B, Boehm B. Early phase cost models for agile software processes in US DoD. In: Proceedings of the ACM/IEEE international symposium on empirical software engineering and measurement (ESEM); 2017.spa
dc.relation.references[19] Ahmed AR, Tayyab M, Bhatti SNr, Alzahrani AJ, Baber MI. Impact of story point estimation on product using metrics in Scrum Development process. IJACSA Int J Adv Comput Sci Appl 2017.spa
dc.relation.references[20] Coelho E, Basu A. Effort estimation in agile software development using story points. Int J Appl Inf Syst IJAIS 2012.spa
dc.relation.references[21] Williams L, Nagappan N. Scrum + engineering practices: experience of three microsoft teams. Software Engineering, IEEE; 2011.spa
dc.relation.references[22] Caballero E., Calvo-Manzano J.A. and Feliu T.S., “Introducing Scrum in a very small enterprise: a productivity and quality analysis”, Springer, EuroSPI 2011, CCIS 172, pp. 215–224-2011.spa
dc.relation.references[23] Trendowicz A, Jeffery R. Software Project effort estimation. Springer, International Publishing Switzerland; 2014.spa
dc.relation.references[24] Zhang Z. The benefits and challenges of planning poker in software development: comparison between theory and practice. Auckland University of Technology; 2017. retrieved from, http://hdl.handle.net/10292/10557.spa
dc.relation.references[25] Lavazza L, Morasca S, Taibi D, Tosi D. Applying SCRUM in an OSS development process. In: Proceedings of the Springer, international conference on agile; 2010.spa
dc.relation.references[26] Desharnais JM, Buglione L, Kocaturk B. Using the COSMIC method to estimate agile user. In: Proceedings of the 12th international conference on product focused software development and process improvement; 2011. Pages 68-73.spa
dc.relation.references[27] Hayata T, Han J. A hybrid model for IT project with scrum. In: Proceedings of IEEE international conference on service operations, logistics and Informatics; 2011.spa
dc.relation.references[28] Popli R, Chauhan N. Cost and Effort estimation in agile software development. In: Proceedings of international conference on reliability optimization and information technology (ICROIT). IEEE; 2014.spa
dc.relation.references[29] Tayh Raslan A, Darwish NR, Ahmed Hefny H. Towards a Fuzzy based framework for effort estimation in agile software development. Int J Comput Sci Inf Secur (IJCSIS) 2015.spa
dc.relation.references[30] Torrecilla-Salinas CJ, Sedeno J, Escalona MJ, Mejias M. Estimating, planning and managing agile web development projects under a value-based perspective. J Syst Softw 2015. ELSEVIER.spa
dc.relation.references[31] Moharreri K, Vinayak Sapre A, Ramanathan J, Ramnath R. Cost-Effective supervised Learning models for software effort estimation in agile environment. In: Proceedings of the 40th annual computer software and applications conference (COMPSAC). IEEE; 2016.spa
dc.relation.references[32] Prakash B, Viswanathan V. A Survey on software estimation techniques in traditional and agile development models. Indones J Electr Eng Comput Sci 2017.spa
dc.relation.references[33] Bilgaiyan S, Sagnika S. Samaresh mishra and madhabananda, “a systematic review on software cost estimation in agile software development”. J Eng Sci Technol Rev 2017.spa
dc.relation.references[34] Vyas M, Bohra A, Lamba CS, Vyas A. A review on software cost and effort estimation techniques for agile development process. Int J Recent Res Aspects 2018;5(1):2349–7688. ISSNVol., Issue.spa
dc.relation.references[35] Yuliansyah H, Qudsiah SN, Zahrotun L, Arfiani I. Implementation of use case point as software effort estimation in Scrum framework. In: Proceedings of the 1st international conference on engineering and applied technology (ICEAT; 2017.spa
dc.relation.references[36] Lenarduzzi V, Lunesu I, Matta M, Taibi D. Functional size measures and effort estimation in agile development: a replicated study. Springer; 2015.spa
dc.relation.references[37] Strode DE, Huff SL, Hope B. Sebastian Link “Coordination in co-located agile software development projects. J Syst Softw 2012. ELSEVIER.spa
dc.relation.references[38] Brede Moe N, Dingsøyr T. Tore Dybå “a teamwork model for understanding an agile team: a case study of a Scrum project. Inf Softw Technol 2010. ELSEVIER.spa
dc.relation.references[39] Nguyen V., Deed-Rubin S., Tan T. and Bohem B., “A SLOC counting standard”, August 2007.spa
dc.relation.references[40] Bhatti K, Tarey V, Patel P. Analysis of source line of code (SLOC) metrics. Int J Emerg Technol Adv Technol 2012.spa
dc.relation.references[41] Olszewska M, Walden M. DevOps meets formal modelling in high-criticality complex systems. In: Proceedings of the 1st international workshop. ACM; 2015.spa
dc.relation.references[42] Ozkan N. Risks, challenges and issues in a possible scrum and COBIT marriage. In: Proceedings of the Asia-pacific software engineering conference. IEEE; 2015.spa
dc.relation.references[43] Samarawickrama SS, Perera I. A continuous Scrum: a framework to enhance Scrum with DevOps. In: Proceedings of the international conference on advances in ICT for emerging regions (ICTer); 2017.spa
dc.relation.references[44] Pohl C., Hof H.J., “Secure Scrum: development of secure software with scrum”, arXiv: 1507.02992v1, 2015.spa
dc.relation.references[45] Vithana VN. Scrum requirements engineering practices and challenges in offshore software development. Int J Comput Appl 2015.spa
dc.relation.references[46] Dingsoyr T, Nerur S, Balijepally V, Moe NB. A decade of agile methodologies: towards explaining agile software development. J Syst Softw 2012. ELSEVIER.spa
dc.relation.references[47] Oomen S, De Waal B, Albertin A, Ravesteyn P. How can Scrum be successful?. In: Proceedings of the cometences of the scrum product owner”, twenty-five European conference on information systems (ECIS); 2017.spa
dc.relation.references[48] Drury M, Conboy K, Power K. Obstacles to decision making in agile software development teams. J Syst Softw 2012. ELSEVIER.spa
dc.relation.references[49] Hoda R, Murugesan L,K. Multi-level agile project management challenges: a selforganizing team perspective. J Syst Softw 2016. ELSEVIER.spa
dc.relation.references[50] Singhto W, Denwattana N. An experience in blending the traditional and agile methodologies to assist in a small software development project. In: Proceedings of the international joint conference on computer science and software engineering; 2016. IEEE.spa
dc.relation.references[51] Vlietland J, Vliet H. Towards a governance framework for chains of Scrum teams. Inf Softw Technol 2015;57:52–65.spa
dc.relation.references[52] Moharreri K, et al. Cost-effective supervised learning models for software effort estimation in agile environments. In: Proceedings of the computer software and applications conference (COMPSAC), IEEE 40th Annual. 2. IEEE; 2016. Vol.spa
dc.relation.references[53] Stray V, Sjøberg DIK, Dybå T. The daily stand-up meeting: a grounded theory study. J Syst Softw 2016;114.spa
dc.relation.references[54] Ahmed AR, et al. Impact of story point estimation on product using metrics in scrum development process. Int J Adv Comput Sci Appl 2017;8(4):385–91.spa
dc.relation.references[55] Salmanoglu M, Hacaloglu T, Demirors O. Effort estimation for agile software development: comparative case studies using COSMIC functional size measurement and story points. In: Proceedings of the 27th international workshop on software measurement and 12th international conference on software process and product measurement. ACM; 2017.spa
dc.relation.references[56] Samarawickrama SS, Perera I. Continuous scrum: a framework to enhance scrum with DevOps. In: Proceedings of the advances in ICT for emerging regions (ICTer), seventeenth international conference on. IEEE; 2017.spa
dc.relation.references[57] Lindsjørn Y, et al. Teamwork quality and project success in software development: a survey of agile development teams. J Syst Softw 2016;122:274–86.spa
dc.relation.references[58] Vlietland J, Van Solingen R, van Vliet H. Aligning codependent Scrum teams to enable fast business value delivery: a governance framework and set of intervention actions. J Syst Softw 2016;113:418–29.spa
dc.relation.references[59] Cooper RG, Sommer AF. Agile–stage-gate for manufacturers: changing the way new products are developed integrating agile project management methods into a Stage-Gate system offers both opportunities and challenges. Res Technol Manag 2018;61(2):17–26.spa
dc.relation.references[60] Drury M, Conboy K, Power K. Obstacles to decision making in Agile software development teams. J Syst Softw 2012;85(6):1239–54.spa
dc.relation.references[61] Przybylek A, Zakrzewski M. Adopting Collaborative games into agile requirements engineering. In: Proceedings of the 13th international conference on evaluation of novel approaches to software engineering (ENASE’18); 2018. https://doi.org/10.5220/0006681900540064.spa
dc.relation.references[62] Bumbary KM. Using velocity, acceleration, and jerk to manage agile schedule risk. In: Proceedings of the international conference on information systems engineering (ICISE). IEEE; 2016 (pp. 73-80).spa
dc.relation.references[63] Mahnic V. A capstone course on agile software development using Scrum. IEEE Trans Educ 2012;55(1):99–106.spa
dc.relation.references[64] Dong, W. (2015). Exploring and theorizing velocity flux in agile development.spa
dc.relation.references[65] Hassanein EE, Hassanien SA. Cost efficient scrum process methodology to improve agile software development. Int J Comput Sci Inf Secur (IJCSIS) 2020;18(4).spa
dc.relation.references[66] Krishna VV. Agile methodology (SCRUM) approach for web application testing process to reduce time, cost and improve the quality. Turk J Comput Math Educ (TURCOMAT) 2021;12(11):5467–80.spa
dc.relation.references[67] Kom EAPS, Suryani E. Designing cost measurement system in a small scrum based software company using activity based costing model (Case Study: ABC company). In: Proceedings of the international conference on information and communications technology (ICOIACT). IEEE; 2019. pp. 943-947.spa
dc.relation.references[68] Przybylek A, Albecka M, Springer O, Kowalski W. Game-based Sprint retrospectives: multiple action research. Empir Softw Eng 2022;27. https://doi. org/10.1007/s10664-021-10043. vol.spa
dc.relation.references[69] Butt SA. Study of agile methodology with the cloud. Pac Sci Rev B Humanit Soc Sci 2016;2(1):22–8.spa
dc.relation.references[70] Butt SA, Abbas SA, Ahsan M. Software development life cycle & software quality measuring types. Asian J Math Comput Res 2016:112–22.spa
dc.relation.references[71] Khalil MA, Kotaiah B. Implementation of agile methodology based on SCRUM tool. In. In: Proceedings of the international conference on energy, communication, data analytics and soft computing (ICECDS). IEEE; 2017 (pp. 2351-2357).spa
dc.relation.references[72] Kom EAPS, Suryani E. Designing cost measurement system in a small scrum based software company using activity based costing model (case study: ABC company). In: Proceedings of the international conference on information and communications technology (ICOIACT). IEEE; 2019. pp. 943-947.spa
dc.relation.references[73] Butt SA. Analysis of unfair means cases in computer-based examination systems. Pac Sci Rev B Humanit Soc Sci 2016;2(2):75–9.spa
dc.relation.references[74] Periyasamy K, Chianelli J. A project tracking tool for scrum projects with machine learning support for cost estimation. EPiC Ser Comput 2021;76:86–94.spa
dc.relation.references[75] Alostad JM, Abdullah LR, Aali LS. A Fuzzy based model for effort estimation in scrum projects. Int J Adv Comput Sci Appl 2017;8(9):270–7.spa
dc.relation.references[76] Gandomani TJ, Faraji H, Radnejad M. Planning poker in cost estimation in agile methods: averaging vs. consensus. In: Proceedings of the 5th conference on knowledge based engineering and innovation (KBEI). IEEE; 2019. p. 066–71.spa
dc.relation.references[77] Arora M, Verma S, Chopra S. A systematic literature review of machine learning estimation approaches in scrum projects. Cogn Inf Soft Comput 2020:573–86.spa
dc.relation.references[78] Anwer F, Aftab S, Shah SM, Waheed U. Comparative analysis of two popular agile process models: extreme programming and scrum. Int J Comput Sci Telecommun 2017;8(2):1–7.spa
dc.relation.references[79] Chavarria RC, Madriz FL. ROI estimation in a scrum project: a case study. In. In: Proceedings of the 28th international conference. 64; 2019. p. 78–87 (Vol., pp.).spa
dc.relation.references[80] Aziz Butt S, Pineres-Espitia ˜ G, Ariza-Colpas P, Tariq MI. Project management issues while using agile methodology. In: Proceedings of the international conference on lean and agile software development. Cham: Springer; 2022. pp. 201-214.spa
dc.relation.references[81] Meyer B. Making sense of agile methods. IEEE Softw 2018;35(2):91–4.spa
dc.subject.proposalScrum projectseng
dc.subject.proposalCost estimation techniqueseng
dc.subject.proposalIssues in the scrumeng
dc.type.coarhttp://purl.org/coar/resource_type/c_2df8fbb1spa
dc.type.contentTextspa
dc.type.driverinfo:eu-repo/semantics/articlespa
dc.type.redcolhttp://purl.org/redcol/resource_type/ARTspa
dc.type.versioninfo:eu-repo/semantics/publishedVersionspa
dc.relation.citationendpage17spa
dc.relation.citationstartpage1spa
dc.relation.citationvolume171spa
dc.type.coarversionhttp://purl.org/coar/version/c_970fb48d4fbd8a85spa
dc.rights.coarhttp://purl.org/coar/access_right/c_f1cfspa


Files in this item

Thumbnail

This item appears in the following Collection(s)

  • Artículos científicos [2689]
    Artículos de investigación publicados por miembros de la comunidad universitaria.

Show simple item record

Atribución-NoComercial-SinDerivadas 4.0 Internacional (CC BY-NC-ND 4.0)
Except where otherwise noted, this item's license is described as Atribución-NoComercial-SinDerivadas 4.0 Internacional (CC BY-NC-ND 4.0)