Oct 2026· Journal of Software: Evolution and Process· 0 citations· 43 references
TL;DR
The aim of this paper is to analyze the risks that remote or hybrid working can pose to software development and examine them from the perspective of the company, the project itself, and employees and find strategies with which to mitigate these challenges.
Abstract
One of the effects of COVID‐19 was that software engineers were forced to work remotely, in many cases without prior experience, which may have led to a number of challenges for projects and organizations, along with developers' well‐being. Several work styles were considered after the pandemic, because not only did teleworking persist but new forms of work emerged, for which neither organizations nor employees were prepared. These new modalities have led to challenges that have not yet been sufficiently addressed in the existing literature, mainly because they are relatively recent phenomena. The aim of this paper is to analyze the risks that remote or hybrid working can pose to software development and examine them from the perspective of the company, the project itself, and employees. Once the problems have been identified, it is important to analyze them from the point of view of a software engineer's personality and assess the likelihood of these challenges arising according to the working model used. It is also essential to find strategies with which to mitigate these challenges. These are the objectives of this paper, which aims to help project managers and developers carry out hybrid or remote software development efficiently and ensure their employees' well‐being. To achieve these objectives, a mixed‐methods approach comprising five stages was adopted: a systematic mapping review to identify and categorize the factors affecting software engineers, a survey of 184 practitioners to validate and refine these factors, a second survey examining the perceived impact of different work modalities on productivity and associated risks, and an evaluation of our framework (main contribution of this paper) through semi‐structured interviews with 10 practitioners.
The Humanization Model for Remote and Hybrid Teams (H‐MRHT), a structured framework for diagnosing and addressing early signs of dehumanization, is proposed and practical recommendations for human resources and engineering managers aimed at strengthening feelings of appreciation, support, and belonging among remote and...
Muhammet Tortumlu, Ahmet Tortumlu· Journal of Software: Evoluti...· 0 citations
Software maintenance occurs throughout the life cycle of the system and is relatively expensive. The Introduction of large language models is changing how software maintenance is conducted. The five areas this paper investigates for the practical applications of large language models in software maintenance are: mainte...
Wen-Qiang Zhang· Journal of Computer Science...· 0 citations
A focus group at the 31st European Conference on Pattern Languages of Programs, People, and Practices found broad consensus that architectural decision-making, accountability, and the authoring of architectural guardrails remain fundamentally human tasks.
U. van Heesch, Olaf Zimmermann, Christian Kohls· arXiv.org· 1 citation
Requirements Engineering (RE) is a critical sub-field of Software Engineering (SE), involving activities to identify, specify, model, analyze, and validate system needs and constraints. RE plays a fundamental role in the SE process. With the current advances in AI, new opportunities for RE arise to ensure the developme...
S. Abualhaija, Chetan Arora, Alessio Ferrari et al.· Software engineering notes· 0 citations
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.