{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,3,17]],"date-time":"2026-03-17T12:06:04Z","timestamp":1773749164983,"version":"3.50.1"},"reference-count":59,"publisher":"MDPI AG","issue":"3","license":[{"start":{"date-parts":[[2026,3,17]],"date-time":"2026-03-17T00:00:00Z","timestamp":1773705600000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/creativecommons.org\/licenses\/by\/4.0\/"}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":["Information"],"abstract":"<jats:p>A state of terminal stagnation is often reached by software projects despite the presence of advanced tools, and these occurrences are defined within this study as software engineering deadpoints, where the cost of system recovery is frequently found to be higher than the actual value of the software. While many factors are seen to lead toward project failure, it is suggested by the evidence that technical debts are the main cause of such failures. A significant number (23.5%) of these fatal issues is created during the early architectural phases of development, and it is noted that these problems often remain hidden until they become unrecoverable. The data collected during this research show that projects facing technical obstacles (Recovery Score: 4.24) are much harder to save than those suffering with process obstacles (Recovery Score: 5.38). It was also observed that a steady reluctance to refactor old logic and an excessive number of code revisions are seen as the most reliable signs that a project is approaching a point of no return. Because these warning signs are often overlooked by management, the eventual failure of the system is often viewed as an unexpected event rather than a predictable outcome of poor early choices. By defining these terminal states, this work provides those in leadership roles with a method to differentiate between minor delays and total failure, thereby assisting teams in avoiding the heavy economic losses associated with unproductive development paths.<\/jats:p>","DOI":"10.3390\/info17030291","type":"journal-article","created":{"date-parts":[[2026,3,17]],"date-time":"2026-03-17T09:35:57Z","timestamp":1773740157000},"page":"291","update-policy":"https:\/\/doi.org\/10.3390\/mdpi_crossmark_policy","source":"Crossref","is-referenced-by-count":0,"title":["Empirical Validation of Software Engineering Deadpoints: An Expert Practitioner Survey"],"prefix":"10.3390","volume":"17","author":[{"ORCID":"https:\/\/orcid.org\/0000-0002-5243-8800","authenticated-orcid":false,"given":"Abdullah A. H.","family":"Alzahrani","sequence":"first","affiliation":[{"name":"Computers Department, Engineering and Computers College\u2014Alqunfuda, Umm Al Qura University, Makkah 24382, Saudi Arabia"}]}],"member":"1968","published-online":{"date-parts":[[2026,3,17]]},"reference":[{"key":"ref_1","unstructured":"(2017). A Guide to the Project Management Body of Knowledge (PMBOK Guide), Project Management Institute. [6th ed.]. Available online: https:\/\/www.pmi.org\/pmbok-guide-standards\/foundational\/pmbok."},{"key":"ref_2","doi-asserted-by":"crossref","first-page":"e1","DOI":"10.1002\/pmj.21345","article-title":"A Guide to the Project Management Body of Knowledge (PMBOK Guide) Fifth Edition","volume":"44","author":"Rose","year":"2013","journal-title":"Proj. Manag. J."},{"key":"ref_3","doi-asserted-by":"crossref","first-page":"130","DOI":"10.1145\/1610252.1610286","article-title":"Why did your project fail?","volume":"52","author":"Cerpa","year":"2009","journal-title":"Commun. ACM"},{"key":"ref_4","doi-asserted-by":"crossref","first-page":"623","DOI":"10.1016\/j.infsof.2014.01.015","article-title":"Perceived causes of software project failures\u2013An analysis of their relationships","volume":"56","author":"Lehtinen","year":"2014","journal-title":"Inf. Softw. Technol."},{"key":"ref_5","doi-asserted-by":"crossref","first-page":"19","DOI":"10.1016\/0306-4573(84)90037-2","article-title":"Program evolution","volume":"20","author":"Lehman","year":"1984","journal-title":"Inf. Process. Manag."},{"key":"ref_6","doi-asserted-by":"crossref","first-page":"275","DOI":"10.1023\/A:1020557525901","article-title":"Software Evolution and Software Evolution Processes","volume":"14","author":"Lehman","year":"2022","journal-title":"Ann. Softw. Eng."},{"key":"ref_7","doi-asserted-by":"crossref","first-page":"33","DOI":"10.1016\/S0020-0190(03)00382-X","article-title":"Software evolution\u2014Background, theory, practice","volume":"88","author":"Lehman","year":"2003","journal-title":"Inf. Process. Lett."},{"key":"ref_8","unstructured":"Krasner, H. (2021). The Cost of Poor Software Quality in the US: A 2020 Report, Consortium for Information & Software Quality CISQ."},{"key":"ref_9","doi-asserted-by":"crossref","unstructured":"Ahmed, I., Brindescu, C., Mannan, U.A., Jensen, C., and Sarma, A. (2017). An Empirical Examination of the Relationship between Code Smells and Merge Conflicts. Proceedings of the 2017 ACM\/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM), IEEE.","DOI":"10.1109\/ESEM.2017.12"},{"key":"ref_10","first-page":"13","article-title":"Technical Debt of Software Projects Based on Merge Code Comments","volume":"13","author":"Costa","year":"2025","journal-title":"J. Softw. Eng. Res. Dev."},{"key":"ref_11","doi-asserted-by":"crossref","first-page":"e2160","DOI":"10.1002\/smr.2160","article-title":"Impact of requirements volatility on software architecture: How do software teams keep up with ever-changing requirements?","volume":"31","author":"Dasanayake","year":"2019","journal-title":"J. Softw. Evol. Process"},{"key":"ref_12","unstructured":"Ferreira, S. (2002). Measuring the Effects of Requirements Volatility on Software Development Projects. [Ph.D. Thesis, Arizona State University]. Available online: https:\/\/search.proquest.com\/openview\/272741b2a4a644fb0dd75186bbef7664\/1?pq-origsite=gscholar&cbl=18750&diss=y&casa_token=NbxDdWpNjzwAAAAA:xucLALZmpEpD-XUSiymJBDevvhFiX4dSrwi3lzxga27P04X7BgdKMWiOTMJ3Yu9t-vZvWTmdNX8."},{"key":"ref_13","doi-asserted-by":"crossref","first-page":"1568","DOI":"10.1016\/j.jss.2009.03.014","article-title":"Understanding the effects of requirements volatility in software engineering by using analytical modeling and software process simulation","volume":"82","author":"Ferreira","year":"2009","journal-title":"J. Syst. Softw."},{"key":"ref_14","doi-asserted-by":"crossref","unstructured":"Nurmuliani, N., Zowghi, D., and Powell, S. (2004). Analysis of requirements volatility during software development life cycle. 2004 Australian Software Engineering Conference. Proceedings, IEEE.","DOI":"10.1109\/ASWEC.2004.1290455"},{"key":"ref_15","unstructured":"Nurmuliani, N., Zowghi, D., and Williams, S. (2006). Requirements volatility & its impact on change effort: Evidence based research n software development projects. Verified OK, University of South Australia."},{"key":"ref_16","first-page":"123","article-title":"Managing Requirements Volatility in Software Quality Standards: Challenges and Best Practices","volume":"7","author":"Pasham","year":"2024","journal-title":"Int. J. Mod. Comput."},{"key":"ref_17","doi-asserted-by":"crossref","unstructured":"Zowghi, D., and Nurmuliani, N. (2002). A study of the impact of requirements volatility on software project performance. Ninth Asia-Pacific Software Engineering Conference, 2002, IEEE.","DOI":"10.1109\/APSEC.2002.1182970"},{"key":"ref_18","unstructured":"Gold-Veerkamp, C., Saray, N., Lavazza, L., Oberhauser, R., Herwig, M., and Kavi, K. (2020, January 18\u201322). A Systematic Literature Review on Misconceptions in Software Engineering. Proceedings of the Fifteenth International Conference on Software Engineering Advances (ICSEA), Porto, Portugal. Available online: https:\/\/www.researchgate.net\/profile\/Luigi-Lavazza\/publication\/346965175_ICSEA_2020_The_Fifteenth_International_Conference_on_Software_Engineering_Advances\/links\/5fd4d34045851553a0af3f64\/ICSEA-2020-The-Fifteenth-International-Conference-on-Software-Engineering-Advances.pdf#page=12."},{"key":"ref_19","doi-asserted-by":"crossref","unstructured":"Ewusi-Mensah, K. (2003). Software Development Failures, MIT Press.","DOI":"10.7551\/mitpress\/6322.001.0001"},{"key":"ref_20","unstructured":"Yourdon, E. (2004). Death March, Prentice Hall Professional."},{"key":"ref_21","first-page":"14","article-title":"Will Your Next Mistake Be Fatal? Avoiding the Chain of Mistakes that Can Destroy Your Organization","volume":"22","author":"Marshall","year":"2006","journal-title":"Financ. Exec."},{"key":"ref_22","unstructured":"Hunt, A., Thomas, D.D., and Yitbarek, S. (2020). The Pragmatic Programmer: Your Journey to Mastery, Addison-Wesley. Available online: https:\/\/www.pearson.com\/en-us\/subject-catalog\/p\/pragmatic-programmer-the-your-journey-to-mastery-20th-anniversary-edition\/P200000000337\/9780135956915."},{"key":"ref_23","unstructured":"Maidan, A. (2026, January 17). Software Project Rescue: Methods That Work. Software Project Rescue Methods Teams Can Rely on. Available online: https:\/\/andersenlab.com\/blueprint\/software-project-rescue-methods."},{"key":"ref_24","doi-asserted-by":"crossref","first-page":"34428","DOI":"10.1109\/ACCESS.2022.3162878","article-title":"Software Project Failure Process Definition","volume":"10","author":"Nizam","year":"2022","journal-title":"IEEE Access"},{"key":"ref_25","doi-asserted-by":"crossref","first-page":"950","DOI":"10.34218\/IJCET_15_04_082","article-title":"Machine Learning for Predicting Software Project Failure Risks","volume":"15","author":"Polu","year":"2024","journal-title":"Int. J. Comput. Eng. Technol."},{"key":"ref_26","first-page":"2","article-title":"A New Weighted Ensemble Model to Improve the Performance of Software Project Failure Prediction","volume":"15","author":"Ibraigheeth","year":"2024","journal-title":"Int. J. Adv. Comput. Sci. Appl."},{"key":"ref_27","first-page":"7","article-title":"Software project failure avoiding through risk analysis and management","volume":"2","author":"Ibraigheeth","year":"2024","journal-title":"J. Intell. Syst. Appl. Data Sci."},{"key":"ref_28","doi-asserted-by":"crossref","unstructured":"Ibraigheeth, M. (2024). Assessment Tool for Software Failure and Risk Mitigation in Project Management. 2024 IEEE International Conference on Data and Software Engineering (ICoDSE), IEEE.","DOI":"10.1109\/ICoDSE63307.2024.10829890"},{"key":"ref_29","first-page":"15008","article-title":"Analyzing the Influence of Stakeholder Misalignment on Software Project Failures","volume":"12","author":"Anjum","year":"2023","journal-title":"Int. J. Innov. Res. Sci. Eng. Technol. (IJIRSET)"},{"key":"ref_30","first-page":"1","article-title":"A Framework for Early Detection of Agile Software Development Project Failures","volume":"2","author":"Nanwin","year":"2025","journal-title":"Fac. Nat. Appl. Sci. J. Comput. Appl."},{"key":"ref_31","first-page":"940","article-title":"Understanding Failed Software Projects through Forensic Analysis","volume":"62","author":"Money","year":"2022","journal-title":"J. Comput. Inf. Syst."},{"key":"ref_32","first-page":"783","article-title":"Factors Affecting Success or Failure in Software Projects in the Kingdom of Saudi Arabia","volume":"6","author":"Alghamdi","year":"2024","journal-title":"Cah. Magellanes-NS"},{"key":"ref_33","first-page":"10","article-title":"Strategies for Early Identification of Failures in Agile Software Development Projects\u2013A Review","volume":"2","author":"Nanwin","year":"2025","journal-title":"Fac. Nat. Appl. Sci. J. Comput. Appl."},{"key":"ref_34","first-page":"65","article-title":"From Analysis to Action: Categorizing and Addressing IT Project Failures for Enhanced Success Rates","volume":"Volume 1501","author":"Jaiswal","year":"2026","journal-title":"Proceedings of International Conference on Computing Systems and Intelligent Applications"},{"key":"ref_35","first-page":"234","article-title":"Project management practices: The criteria for success or failure","volume":"1","author":"Attarzadeh","year":"2008","journal-title":"Commun. IBIMA"},{"key":"ref_36","doi-asserted-by":"crossref","first-page":"e2735","DOI":"10.1002\/smr.2735","article-title":"A Study of Factors That Influence the Software Project Success","volume":"37","author":"Monserrat","year":"2025","journal-title":"J. Softw. Evol. Process"},{"key":"ref_37","doi-asserted-by":"crossref","first-page":"165","DOI":"10.1007\/s42452-022-05051-7","article-title":"Prediction of failures in the project management knowledge areas using a machine learning approach for software companies","volume":"4","author":"Taye","year":"2022","journal-title":"SN Appl. Sci."},{"key":"ref_38","doi-asserted-by":"crossref","unstructured":"Zhang, M., Antwi-Afari, M.F., Wang, C., Sun, W., Mohandes, S.R., and Abdulai, S.F. (2025). Uncertainty in Software Development Projects: A Review of Causes, Types, Challenges, and Future Research Directions. Systems, 13.","DOI":"10.3390\/systems13080650"},{"key":"ref_39","doi-asserted-by":"crossref","unstructured":"Ockiya, T.F., and Lock, R. (2023). A Review of Human Factors in Remote Software Project Management: A Progressive Look at Human Based Issues in Remote Software Development Environments. Proceedings of the 2023 12th International Conference on Software and Information Engineering, ACM.","DOI":"10.1145\/3634848.3634858"},{"key":"ref_40","doi-asserted-by":"crossref","first-page":"1","DOI":"10.1145\/3504003","article-title":"How Do Successful and Failed Projects Differ? A Socio-Technical Analysis","volume":"31","author":"Joblin","year":"2022","journal-title":"ACM Trans. Softw. Eng. Methodol."},{"key":"ref_41","doi-asserted-by":"crossref","unstructured":"Shokrizadeh, J., and Shokrizadeh, Z. (2024). Identifying and Ranking Key Failure Factors in Software Projects (Case Study: Software Services of MMTE Company). SSRN J.","DOI":"10.2139\/ssrn.4783773"},{"key":"ref_42","unstructured":"Frank, J., and Jung, D. (2018). Why IT-Projects Fail: A Meta-Analysis of the Construct \u2018Escalating Commitment\u2019 in Information Systems Research, Karlsruhe Institute of Technology."},{"key":"ref_43","doi-asserted-by":"crossref","first-page":"100476","DOI":"10.1016\/j.array.2025.100476","article-title":"Impact of software quality on organizational performance","volume":"27","author":"Nabot","year":"2025","journal-title":"Array"},{"key":"ref_44","first-page":"32","article-title":"Software Quality Measurement: User-based assessment","volume":"2","author":"Elhetsh","year":"2025","journal-title":"Arraid J. Sci. Technol. AJST"},{"key":"ref_45","first-page":"37","article-title":"A Two-Step Approach to Boost Neural Network Generalizability in Predicting Defective Software","volume":"Volume 1445","author":"Latifi","year":"2023","journal-title":"ITNG 2023 20th International Conference on Information Technology-New Generations"},{"key":"ref_46","doi-asserted-by":"crossref","unstructured":"Borowa, K., Ratkowski, A., and Verdecchia, R. (2025). The Technical Debt Gamble: A Case Study on Technical Debt in a Large-Scale Industrial Microservice Architecture. arXiv.","DOI":"10.2139\/ssrn.4946579"},{"key":"ref_47","doi-asserted-by":"crossref","first-page":"110586","DOI":"10.1016\/j.jss.2020.110586","article-title":"The influence of Technical Debt on software developer morale","volume":"167","author":"Besker","year":"2020","journal-title":"J. Syst. Softw."},{"key":"ref_48","doi-asserted-by":"crossref","first-page":"781","DOI":"10.1007\/s12532-022-00225-1","article-title":"On technical debt in mathematical programming: An exploratory study","volume":"14","author":"Vidoni","year":"2022","journal-title":"Math. Program. Comput."},{"key":"ref_49","doi-asserted-by":"crossref","unstructured":"Aldaeej, A., and Seaman, C. (2022, January 18). The Negative Implications of Technical Debt on Software Startups: What They Are and When They Surface. Proceedings of the 5th International Workshop on Software-Intensive Business: Towards Sustainable Software Business, Pittsburgh, PA, USA.","DOI":"10.1145\/3524614.3528629"},{"key":"ref_50","doi-asserted-by":"crossref","unstructured":"Binamungu, L.P., Phiri, D.E., and Simba, F. (2022). An Empirical Study of the Extent and Causes of Technical Debt in Public Organizations Software Systems. SSRN J.","DOI":"10.2139\/ssrn.4040641"},{"key":"ref_51","doi-asserted-by":"crossref","first-page":"139","DOI":"10.1007\/s10664-022-10183-w","article-title":"Self-Admitted Technical Debt and comments\u2019 polarity: An empirical study","volume":"27","author":"Cassee","year":"2022","journal-title":"Empir. Softw. Eng."},{"key":"ref_52","doi-asserted-by":"crossref","unstructured":"Finke, M., Neff, T., and Reichl, T. (2023). How to introduce TD Management into a Software Development Process\u2014A Practical Approach. 2023 ACM\/IEEE International Conference on Technical Debt (TechDebt), IEEE.","DOI":"10.1109\/TechDebt59074.2023.00013"},{"key":"ref_53","doi-asserted-by":"crossref","first-page":"391","DOI":"10.1007\/s11219-023-09655-z","article-title":"Keyword-labeled self-admitted technical debt and static code analysis have significant relationship but limited overlap","volume":"32","author":"Rantala","year":"2024","journal-title":"Softw. Qual. J."},{"key":"ref_54","doi-asserted-by":"crossref","unstructured":"Gorripati, S.M.C., Altalbe, A., and Rangarajan, P.K. (JCCE, 2025). Advances in Managing Self-Admitted Technical Debt: A Review of NLP and Machine Learning Approaches, JCCE, online\u00a0first.","DOI":"10.47852\/bonviewJCCE52025975"},{"key":"ref_55","doi-asserted-by":"crossref","first-page":"63","DOI":"10.1007\/978-3-031-51075-5_3","article-title":"Nexus Between Psychological Safety and Non-Technical Debt in Large-Scale Agile Enterprise Resource Planning Systems Development","volume":"Volume 499","author":"Ahmad","year":"2024","journal-title":"Software, System, and Service Engineering"},{"key":"ref_56","doi-asserted-by":"crossref","first-page":"869","DOI":"10.1109\/TSE.2012.74","article-title":"What industry needs from architectural languages: A survey","volume":"39","author":"Malavolta","year":"2012","journal-title":"IEEE Trans. Softw. Eng."},{"key":"ref_57","doi-asserted-by":"crossref","first-page":"3692","DOI":"10.1109\/TSE.2023.3267848","article-title":"Javascript dead code identification, elimination, and empirical assessment","volume":"49","author":"Malavolta","year":"2023","journal-title":"IEEE Trans. Softw. Eng."},{"key":"ref_58","first-page":"306","article-title":"The role of requirements in the success or failure of software projects","volume":"6","author":"Hussain","year":"2016","journal-title":"Int. Rev. Manag. Mark."},{"key":"ref_59","doi-asserted-by":"crossref","first-page":"629","DOI":"10.1108\/K-12-2018-0699","article-title":"ERP issues and challenges: A research synthesis","volume":"49","author":"Mahmood","year":"2019","journal-title":"Kybernetes"}],"container-title":["Information"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/www.mdpi.com\/2078-2489\/17\/3\/291\/pdf","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2026,3,17]],"date-time":"2026-03-17T11:21:02Z","timestamp":1773746462000},"score":1,"resource":{"primary":{"URL":"https:\/\/www.mdpi.com\/2078-2489\/17\/3\/291"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2026,3,17]]},"references-count":59,"journal-issue":{"issue":"3","published-online":{"date-parts":[[2026,3]]}},"alternative-id":["info17030291"],"URL":"https:\/\/doi.org\/10.3390\/info17030291","relation":{},"ISSN":["2078-2489"],"issn-type":[{"value":"2078-2489","type":"electronic"}],"subject":[],"published":{"date-parts":[[2026,3,17]]}}}