Research synthesis · Sustainable software engineering

Sustainable software engineering: ESG in software projects, software quality and reliable IT project delivery

Vajjhala and colleagues address sustainability in software engineering in two senses — whether software projects can be assessed against ESG criteria, and whether software and IT projects are built to last through defect prediction, sound programming education and evidence on why IT projects fail.

A short narrative review of research by Narasimha Rao Vajjhala and co-authors in this area. Every claim carries an APA citation that links to the publication’s own page (abstract, key findings, DOI); the full references are listed at the end. Updated .

Synthesis

Narasimha Rao Vajjhala’s work bears on sustainable software engineering in two senses: whether software projects can be assessed against environmental, social and governance criteria, and whether software and the IT projects that deliver it are built to last.

On the first, Strang and Vajjhala (2026a) treated one financial firm’s project evaluation practice as a socio-technical system and applied an open-source data science workflow to 207 software engineering project records. Stakeholder-rated social and governance factors tracked the overall project score almost perfectly (r = +0.995 and +0.966), but the environmental factor was unrelated to it, and machine learning classifiers performed weakly (kNN AUC = 0.497; SVM accuracy 61.8%). The authors concluded that ESG measurement in software projects is shaped by human rating practice and organizational templates as much as by algorithms. A companion study showed that project-level ESG compliance can be measured with a validated seven-item instrument covering ESG planning and ESG monitoring and controlling (Strang & Vajjhala, 2026c), and an edited volume set out how Internet of Things solutions can be designed to minimise environmental impact across industries (Thandekkattu & Vajjhala, 2024).

On the second, the group has studied software quality and the people who build software. Saheed et al. (2021) showed that a boosted and bagged ensemble, led by CatBoost, predicted software defects on NASA datasets with outstanding performance when judged on AUC, F-measure and the Matthews correlation coefficient rather than accuracy alone. Fonkam and Vajjhala (2026) reviewed 28 empirical studies and found that functional programming taught with Haskell brings consistent benefits for mathematical reasoning and abstract thinking, with integrated approaches outperforming purely functional ones and selective transfer to mainstream object-oriented languages.

Finally, sustainable delivery depends on IT projects that do not fail. Mining about 17,430 US government IT projects, Strang and Vajjhala (2023a) identified project manager experience, project budget and outsourced versus in-house project management as significant failure predictors. Controlled experiments showed that a bonus incentive made experienced project managers less likely to cancel a failing military software project, with risk competency as the protective factor (Strang & Vajjhala, 2022a; Strang & Vajjhala, 2022b), and in Fintech projects team members’ willingness to disclose past performance nearly doubled the explained variance in project success, from 9.6% to 18.8% (Strang & Vajjhala, 2025a).

The resulting view of sustainable software engineering joins measurable ESG criteria with software quality, sound programming education and evidence-based project governance.

Key claims with sources

  1. In financial software engineering projects, social and governance ratings tracked the overall project score almost perfectly while the environmental factor was unrelated to it (Strang & Vajjhala, 2026a).
  2. An ensemble CatBoost model gave outstanding software defect prediction performance when judged on AUC, F-measure and MCC rather than accuracy alone (Saheed et al., 2021).
  3. Project manager experience, budget and in-house versus outsourced management predict IT project failure (Strang & Vajjhala, 2023a).

References

How to cite this synthesis

Please cite the original publications above for specific findings. To cite this overview itself:

Vajjhala, N. R. (2026, September 25). Sustainable software engineering: ESG in software projects, software quality and reliable IT project delivery. Narasimha Rao Vajjhala. https://www.narasimharao.net/research/focus-areas/sustainable-software-engineering/

Markdown version