Authors : Oluwakoya John B.; Ogbonna Chibueze A.; Maitanmi Stephen O.

Volume/Issue : Volume 11 - 2026, Issue 2 - February

Google Scholar : https://tinyurl.com/mua5y97s

Scribd : https://tinyurl.com/222ww67w

DOI : https://doi.org/10.38124/ijisrt/26feb900

Note : A published paper may take 4-5 working days from the publication date to appear in PlumX Metrics, Semantic Scholar, and ResearchGate.

Abstract : The evaluation of project performance has become important due to the persistent failure of software projects. Agile metrics provide essential insights for optimizing delivery by guiding teams towards iterative success through adaptive practices and continuous improvement. Metrics such as sprint burndown, velocity, control charts, and cumulative flow diagrams help track progress, identify risks, and maintain predictable delivery cadences. These tools enable teams to forecast workloads, manage scope changes, and ensure consistent throughput. Control charts and cumulative flow diagrams further enhance efficiency by visualizing cycle times and work status across development stages, helping to detect bottlenecks and workflow irregularities. Quality metrics – including defect counts, deferred defects, and automated test coverage – ensure reliability and customer satisfaction by identifying issues early and reducing rework. Additionally, integrating quality metrics ensure teams maintain high standards across all phases of development. Metrics such as defect counts, deferred defects, and automated test coverage are crucial for maintaining product reliability and addressing potential issues before customer release. Effective quality measurement also supports continuous improvement, emphasizing customer satisfaction and reducing the need for rework through timely identification of flaws. By systematically applying Agile metrics, teams can refine workflows, mitigate risks, and adapt to evolving priorities. This fosters a framework of collaboration, innovation, and sustained progress, ultimately enabling delivery of high – value products with greater predictability and efficiency.

Keywords : Agile Metrics; Project Optimization; Sprint Burndown; Velocity; Quality Assurance; Cumulative Flow Diagram; System Development Life Cycle

References :

1. S. Balaji and M. S. Murugaiyan, “Waterfall vs. Agile: a comparative study on SDLC,” International Journal of Information Technology and Business Management, vol. 2, no. 1, pp. 26-30, 2012
2. H. Hajjdiab and A. S. Al Shaima Taleb, “Adopting agile software development: issues and challenges,” International Journal of Managing Value and Supply Chains, vol. 2, no. 3, pp. 1-10, 2011
3. H. Berger and P. Beynon-Davies, “The utility of rapid application development in large-scale, complex projects,” Information Systems Journal, vol. 19, no. 6, pp. 549 -570, 2009.
4. B. Hobbs and Y. Petit, “Agile methods on large projects in large organizations,” Project Management Journal, vol. 48, no. 3, pp. 3-19, 2017.
5. S. Alam, S. A. A. Shah, S. N. Bhatti, and A. M. Jadi, “Impact and challenges of requirement engineering in agile methodologies: A systematic review,” International Journal of Advanced Computer Science and Applications, vol. 8, 2017.
6. A. Moniruzzaman and D. S. A. Hossain, “Comparative study on agile software development methodologies,” 2013, http://arxiv.org/abs/13073356.
7. R. Knaster and D. Leffingwell, SAFe 4.0 Distilled: Applying the Scaled Agile Framework for Lean Software and Systems Engineering, Addison-Wesley Professional, 2017.
8. A. Putta, M. Paasivaara, and C. Lassenius, “Benefits and challenges of adopting the scaled agile framework (SAFe): preliminary results from a multivocal literature review,” in International Conference on Product-Focussed Software Process Improvement, pp. 334-351, Springer, Berlin, Germany, 2018.
9. T. Hafterson, “Incorporating agile methods into the development of large-scale systems,” In Proceedings of the UMM CSsci Senior Conference, Moris, MN, USA, July 2011.
10. K. Beck, M. Beedle, A. Van Bennekum et al. Manifesto for Agile Software Development, Agile Manifesto, 2001.
11. J. Highsmith and A. Cockburn, “Agile software development: the business of innovation,” Computer, vol. 34, no. 9, pp. 120 – 127, 2001.
12. M. U. Malik, N. M. Chaudhry, and K. S. Malik, “Evaluation of efficient requirement engineering techniques in agile software development,” International Journal of Computer Applications, vol. 83, no. 3, 2013.
13. T. Jokela and P. Abrahamsson, “Usability assessment of an extreme programming project: close co-operation with the customer does not equal to good usability,” in Product Focussed Software Process Improvement, pp. 393 – 407, Springer, Berlin, Germany, 2011.
14. T. Dingsoyr, T. E. Faegri, and J. Itkonen, “What is large in large-scale? A taxonomy of scale for agile software development,” in Proceedings of the International Conference on Product-Focussed Software Process Improvement, pp. 273 – 276, Springer, Rovaniemi, Finland, December 2014.
15. M. F. Abrar, M. S. Khan, S Ali et al., “Motivators for large-scale agile adoption from management perspective: a systematic literature review,” IEEE Access, vol. 7, pp. 22660 – 22674, 2019.
16. B. Kovitz, “Hidden skills that support phased and agile requirements engineering,” Requirements Engineering, vol. 8, no. 2, pp. 135 – 141, 2003.
17. L. Cao and B. Ramesh, “Agile requirements engineering practices: an empirical study,” IEEE Software, vol. 25, no. 1, pp. 60 – 67, 2008.
18. M. Amir, K. Khan, A. Khan, and M. Khan,” An appraisal of agile software development process,” International Journal of Advanced Science & Technology, vol. 58, no. 56, p. 20, 2013.
19. F. Paetsch, A. Eberlein, and F. Maurer, “Requirements engineering and agile software development,” in Proceedings of the Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, pp. 308 – 313, IEEE, Washington, DC, USA, June 2003
20. N. Ganesh and S. Thangasamy, “Issues identified in the software process due to barriers found during eliciting requirements on agile software projects: insights from India,” International Journal of Computer Applications, vol. 16, no. 5, pp. 7 – 12, 2011.
21. J. Cho, “Issues and Challenges of agile software development with SCRUM, “Issues in Information Systems, vol. 9, no. 2, pp. 188 – 195, 2008.
22. W. Helmy, A. Kamel, and O. Hegazy, “Requirements engineering methodology in agile environment,” International Journal of Computer Science Issues (IJCSI), vol. 9, no. 5, p. 293, 2012.
23. M. S. Rahim, A. E. Chowdhury, and S. Das, “Rize: a proposed requirements prioritization technique for agile development,” in Proceedings of the 2017 IEEE Region 10 Humanitarian Technology Conference (R10-HTC), pp. 634-637, IEEE, Bangladesh, Asia, December 2017.
24. D. Mishra and A. Mishra, “Complex software project development: agile methods adoption,” Journal of Software Maintenance and Evolution: Research and Practice, vol. 23, no. 8, pp. 549-564, 2011.
25. E. Bjarnason, K. Wnuk, and B. Regnell, “A case study on benefits and side effects of agile practices in large-scale requirements engineering,” in Proceedings of the 1^st Workshop on Agile Requirements Engineering, pp. 1-5, Lancaster, UK, June 2011.
26. G. Lee, W. DeLone, and J. A. Espinosa, “Ambidextrous coping strategies in globally distributed software development projects,” Communications of the ACM, vol. 49, no. 10, pp. 35-40, 2006.
27. N. A. Ernst, A. Borgida, I. J. Jureta, and J. Mylopoulos,” Agile requirements engineering via paraconsistent reasoning,” Information Systems, vol. 43, pp. 100-116, 2014.
28. T. Kamal, Q. Zhang, M. A. Akbar, M. Shafiq, A. Gumaei, and A. Alsanad, “Identification and prioritization of agile requirements change management success factors in the domain of global software development,” IEEE Access, vol. 8, pp. 44714-44726, 2020.
29. K. AbdElazim, R. Moawad, and E. Elfakharany, “A framework for requirements prioritization process in agile software development,” Journal of Physics, vol. 1454, 2020.
30. W. M. Farid and F. J. Mitropoulos, “Visualization and scheduling of non-functional requirements for agile processes,” in Proceedings of the 2013 IEEE Southeastcon, pp. 1-8, IEEE, Jacksonville, FL, USA, April 2013.
31. M. Kapyaho and M. Kauppinen, “Agile requirements engineering with prototyping: a case study,” in Proceedings of the 2015 IEEE 23rd International Requirements Engineering Conference (RE), pp. 334-343, IEEE, Ottawa, ON, USA, August 2015.
32. F. A. Mir and D. Rezania, “From interactive control to IT project performance: examining the mediating role of stakeholder analysis effectiveness,” Journal of Accounting & organizational Change, 2021. Doi:10.1108/JAOC-04-2021-0048
33. C. Snyder, Paper Prototyping: The Fast and Easy Way to Design and Refine User Interfaces, Morgan Kaufmann, Burlington, MA, USA, 2003.
34. R. McAdam, B. Mason, and J. McCrory, “Exploring the dichotomies within the tacit knowledge literature towards a process of tacit knowing in organizations,” Journal of Knowledge Management, 2007.
35. S. Ryan and R. V. O’Çonnor, “Acquiring and sharing tacit knowledge in software development teams: an empirical study,” Information and Software Technology, vol.55, no. 9, pp.1614-1624, 2013.
36. A. R. Asghar, S. N. Bhatti, A. Tabassum, and S. Shah, “The impact of analytical assessment of requirements prioritization models: an empirical study, “International Journal of Advanced Computer Science and Applications (IJACSA) vol. 8, no. 2, pp. 303-313, 2017.
37. D. Turk, R. France, and B. Rumpe, “Limitations of agile software processes,” 2014, http://arxiv.org/abs/14096600.
38. P. E. D. Love, G. D. Holt, and H. Li, “Stakeholder perspective measurement (SPM) framework for construction projects, “Construction Management and Economics, vol.18, no.3, pp. 321-331, 2002.
39. G. Sawarkar and D. Rajput, “Comparative Analysis of Various Software Development Life Cycle,” International Journal of Computer Science and Mobile Computing, vol. 11, no. 8, pp. 1-8, 2022. Doi: 10.47760/ijcsmc. 2022.v11i08.001
40. L. Zhang, C. Baron, P. Esteban, R. Xue, Q. Zhang and S. Yang, “Using leading Indicators to improve project performance measurement,” Journal of Systems Science and Systems Engineering, vol. 28, no. 5, pp. 529 – 554, 2019.
41. S. A. Devaux, “Managing Projects as Investments: Earned Value to Business Value,” CRC Press, 2014.
42. M. K. Sharma, “A study of SDLC to develop well engineered software,” International Journal of Advanced Research in Computer Science,2017. doi: 10.26483/IJARCS.V813.3045
43. A. Garg, R. K. Kaliyar and A. Goswami, “PDRSD- A systematic review on plan-driven SDLC models for Software Development,” 2022. Doi: 10.1109/ICACCS541555559.2022.9785261.
44. S. Gupta, J. Banga, S. Dabas and M. K. Bhatia, “A Comprehensive Study of Software Development Lifecycle Models,” International Journal for Science Technology and Engineering, 2022. Doi: 10.22214/ijraset.2022.47868.
45. A. A. Amaefule and F. N. Ogwueleka,” Criteria for choosing the Right Software Development Life Cycle Method for the Success of Software Projects,” IUP Journal of Information Technology, vol. 16, no. 2, pp. 40-65, 2020.
46. O. Gun, P. Y. Kumru and Z. Aladag,” Developing a model for Measuring Project Performance with Software Life Cycle Process Metrics and Calculating Project Success Score,” Sakarya University Journal of Science, vol. 24, no. 3, pp. 536-554, 2020.
47. P. J. Haried and C. C. Claybaugh,” Evaluating Information System Offshore Project Success: Can Success and Failure Co-exist,” Journal of Global Information Technology Management, vol. 20, no. 1, pp. 8 – 27, 2017.
48. J. Pereiva, J. Varajao and N. Takagi, “Evaluation of Information Systems Project Success – Insights from Practitioners, Information Systems Management, vol. 39, no. 2, pp. 138-155, 2022. doi: 10.1080/10580530.2021.1887982.
49. A. Al-Shaaby and A. Ahmed, “How Do We measure Project Success? A Survey, Journal of Information Technology & Software Engineering, vol. 8, no. 2, 2018. Doi: 10.4172/2175-7866.1000229
50. L. ITai and S. Avraham, “Measuring the Success of Lean and Agile Projects: Are cost, time, scope and quality equally important? Journal of Modern Project Management, vol. 7, no. 1, 2019. Doi: 10.19255/JMPM01908.
51. C. C. Villazon, L. S. Pinilla, J. R. O. Olaso, N. T. Gandaria and N. Lopez de Lacalle, “Identification of Key performance Indicators in Project-based Organization through Lean Approach, 2020
52. K. Chopra and M. Sachdeva, “Evaluation of Software Metrics for Software Projects, “ 2015 or 2018 doi: 10.1109/DSMP.2018.8478464
53. V. Ostakhov, N. Artykulna and V. Morozov, “Models of IT Projects KPIs and Metrics,” International Conference on Data Stream Mining & Processing, 2018
54. L. McLeod and S. G. MacDonell, “Factors that affect software systems development project outcomes: a survey of research, ACM Computing Surveys, vol. 43, no. 4, pp. 24-56, 2011. Doi: 10.1145/1978802.1978803.
55. S. Alsulamy, S. Wamuziri and M. Taylor, “Evaluation of key metrics for measurement of project performance In: Smith, S. D (Ed) Procs 28^th Annual ARCOM Conference, 3-5 September 2012, Edinburgh, UK, Association of Researchers in Contruction Management, 1101 – 1110.
56. H. Aminu and F. N. Ogwueleka, “A Comparative Study of System Development Life Cycle Models, Journal of Emerging Technologies and Innovative Research (JETIR), vol. 7, no. 8, 2020.