Dron Khanna
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Dron Khanna has a total of 52 co-authors. Here are the top co-authors by number of shared publications:
- Xiaofeng Wang
Free University of Bozen-Bolzano, Bolzano, Italy and Lappeenranta-Lahti University of Technology, Lahti, Finland
7 shared publications - Anh Nguyen-Duc
University of Transport Technology
5 shared publications - Emily Laue Christensen
IT University of Copenhagen, Denmark and LUT University, Finland
3 shared publications - Henry Edison
Blekinge Institute of Technology
3 shared publications Jorge Melegati
Free University of Bozen‐Bolzano Bolzano Italy
3 shared publications- Maria Paasivaara
LUT University
3 shared publications
Latest Publications
- Open Access
- 30 October 2026
- Published by Elsevier in Journal of Systems and Software
- Vol. 245
Revisiting hybrid work in agile software engineering: A systematic literature review
- 30 October 2026
- Published by Elsevier in Journal of Systems and Software
- Vol. 245
Open AccessRevisiting hybrid work in agile software engineering: A systematic literature review
- Open Access
- 30 October 2025
- Published by Springer Nature
- p. 53-67
Hybrid Work in Agile Software Engineering: Current Research and Future Directions
Hybrid work has become the new normal in post-pandemic software engineering. It is a timely topic that has attracted increasing attention among software engineering practitioners and researchers alike. In this paper, we summarize the findings from the third International Workshop on Global and Hybrid Work in Software Engineering (GoHyb) that was organized in conjunction with the XP 2025 conference. We present future research topics related to hybrid work in agile software engineering, which were brainstormed and collected during the workshop, supplemented with a systematic review of the literature on current and future research topics.
- 30 October 2025
- Published by Springer Nature
- p. 53-67
Open AccessHybrid Work in Agile Software Engineering: Current Research and Future Directions
Hybrid work has become the new normal in post-pandemic software engineering. It is a timely topic that has attracted increasing attention among software engineering practitioners and researchers alike. In this paper, we summarize the findings from the third International Workshop on Global and Hybrid Work in Software Engineering (GoHyb) that was organized in conjunction with the XP 2025 conference. We present future research topics related to hybrid work in agile software engineering, which were brainstormed and collected during the workshop, supplemented with a systematic review of the literature on current and future research topics.
- Top Cited Papers
- 29 July 2025
- Published by Wiley in Software: Practice and Experience
- Vol. 55 (11) , 1806-1843
Generative Artificial Intelligence for Software Engineering—A Research Agenda
Context: Generative artificial intelligence (GenAI) tools have become increasingly prevalent in software development, offering assistance to various managerial and technical project activities. Notable examples of these tools include OpenAI's ChatGPT, GitHub Copilot, and Amazon CodeWhisperer.Objective: Although many recent publications have explored and evaluated the application of GenAI, a comprehensive understanding of the current development, applications, limitations, and open challenges remains unclear to many. Particularly, we do not have an overall picture of the current state of GenAI technology in practical software engineering usage scenarios.Method: We conducted a literature review and focus groups for a duration of five months to develop a research agenda on GenAI for software engineering.Results: We identified 78 open research questions (RQs) in 11 areas of software engineering. Our results show that it is possible to explore the adoption of GenAI in partial automation and support decision‐making in all software development activities. While the current literature is skewed toward software implementation, quality assurance and software maintenance, other areas, such as requirements engineering, software design, and software engineering education, would need further research attention. Common considerations when implementing GenAI include industry‐level assessment, dependability and accuracy, data accessibility, transparency, and sustainability aspects associated with the technology.Conclusions: GenAI is bringing significant changes to the field of software engineering. Nevertheless, the state of research on the topic still remains immature. We believe that this research agenda holds significance and practical value for informing both researchers and practitioners about current applications and guiding future research.
- 29 July 2025
- Published by Wiley in Software: Practice and Experience
- Vol. 55 (11) , 1806-1843
Top Cited PapersGenerative Artificial Intelligence for Software Engineering—A Research Agenda
Context: Generative artificial intelligence (GenAI) tools have become increasingly prevalent in software development, offering assistance to various managerial and technical project activities. Notable examples of these tools include OpenAI's ChatGPT, GitHub Copilot, and Amazon CodeWhisperer.Objective: Although many recent publications have explored and evaluated the application of GenAI, a comprehensive understanding of the current development, applications, limitations, and open challenges remains unclear to many. Particularly, we do not have an overall picture of the current state of GenAI technology in practical software engineering usage scenarios.Method: We conducted a literature review and focus groups for a duration of five months to develop a research agenda on GenAI for software engineering.Results: We identified 78 open research questions (RQs) in 11 areas of software engineering. Our results show that it is possible to explore the adoption of GenAI in partial automation and support decision‐making in all software development activities. While the current literature is skewed toward software implementation, quality assurance and software maintenance, other areas, such as requirements engineering, software design, and software engineering education, would need further research attention. Common considerations when implementing GenAI include industry‐level assessment, dependability and accuracy, data accessibility, transparency, and sustainability aspects associated with the technology.Conclusions: GenAI is bringing significant changes to the field of software engineering. Nevertheless, the state of research on the topic still remains immature. We believe that this research agenda holds significance and practical value for informing both researchers and practitioners about current applications and guiding future research.
- Open Access
Software Companies Responses to Hybrid Working
COVID 19 pandemic has disrupted the global market and workplace landscape. As a response, hybrid work situations have become popular in the software business sector. This way of working has an impact on software companies. This study investigates software companies responses to hybrid working. We conducted a large scale survey to achieve our objective. Our results are based on a qualitative analysis of 124 valid responses. The main result of our study is a taxonomy of software companies impacts on hybrid working at individual, team and organisation levels. We found higher positive responses at individual and organisational levels than negative responses. At the team level, both positive and negative impacts obtained a uniform number of responses. The results indicate that hybrid working became credible with the wave of COVID 19, with 83 positive responses outweighing the 41 negative responses. Software company respondents witnessed better work-life balance, productivity, and efficiency in hybrid working.
Open AccessSoftware Companies Responses to Hybrid Working
COVID 19 pandemic has disrupted the global market and workplace landscape. As a response, hybrid work situations have become popular in the software business sector. This way of working has an impact on software companies. This study investigates software companies responses to hybrid working. We conducted a large scale survey to achieve our objective. Our results are based on a qualitative analysis of 124 valid responses. The main result of our study is a taxonomy of software companies impacts on hybrid working at individual, team and organisation levels. We found higher positive responses at individual and organisational levels than negative responses. At the team level, both positive and negative impacts obtained a uniform number of responses. The results indicate that hybrid working became credible with the wave of COVID 19, with 83 positive responses outweighing the 41 negative responses. Software company respondents witnessed better work-life balance, productivity, and efficiency in hybrid working.
- 1 June 2024
- Published by Springer Nature
- p. 257-273
Value-Based Adoption of ChatGPT in Agile Software Development: A Survey Study of Nordic Software Experts
- 1 June 2024
- Published by Springer Nature
- p. 257-273
Value-Based Adoption of ChatGPT in Agile Software Development: A Survey Study of Nordic Software Experts
- Open Access
- 14 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 57-67
Hybrid Work meets Agile Software Development: A Systematic Mapping Study
Hybrid work, a fusion of different work environments that allow employees to work in and outside their offices, represents a new frontier for agile researchers to explore. However, due to the nascent nature of the research phenomena, we are yet to achieve a good understanding of the research terrain formulated when hybrid work meets agile software development. This systematic mapping study, we aimed to provide a good understanding of this emerging research area. The systematic process we followed led to a collection of 12 primary studies, which is less than what we expected. All the papers are empirical studies, with most of them employing case studies as the research methodology. The people-centric nature of agile methods is yet to be adequately reflected in the studies in this area. Similarly, there is a lack of a richer understanding of hybrid work in terms of flexible work arrangements. Our mapping study identified various research opportunities that can be explored in future research.
- 14 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 57-67
Open AccessHybrid Work meets Agile Software Development: A Systematic Mapping Study
Hybrid work, a fusion of different work environments that allow employees to work in and outside their offices, represents a new frontier for agile researchers to explore. However, due to the nascent nature of the research phenomena, we are yet to achieve a good understanding of the research terrain formulated when hybrid work meets agile software development. This systematic mapping study, we aimed to provide a good understanding of this emerging research area. The systematic process we followed led to a collection of 12 primary studies, which is less than what we expected. All the papers are empirical studies, with most of them employing case studies as the research methodology. The people-centric nature of agile methods is yet to be adequately reflected in the studies in this area. Similarly, there is a lack of a richer understanding of hybrid work in terms of flexible work arrangements. Our mapping study identified various research opportunities that can be explored in future research.
- Open Access
- 9 February 2024
- Published by Springer Nature
- p. 416-424
Exploring Emotions in Online Team Meetings: Unpacking Agile Retrospective
Establishing a psychologically safe work environment is crucial for leading a positive and practical agile retrospective. Emotions are closely intertwined concepts that come under the roof of psychology. Capturing them at the right time helps to detect harmful or favourable online behaviours, hinder or facilitate the software development cycle, and moralize or demoralize the team in a software company. This study aims to identify emotions that appear during the online agile retrospective. Our study asks the research question: How often are different emotions repeated during the online agile retrospective? We conducted a multiple case study with two software companies. We analyzed three recorded online retrospective sessions to seize various emotions. Our findings show that eighteen emotions appear on the agile retrospective. Some of the highest repeated emotions are approval, realization, excitement, relief, disappointment, confusion, optimism, and disapproval.
- 9 February 2024
- Published by Springer Nature
- p. 416-424
Open AccessExploring Emotions in Online Team Meetings: Unpacking Agile Retrospective
Establishing a psychologically safe work environment is crucial for leading a positive and practical agile retrospective. Emotions are closely intertwined concepts that come under the roof of psychology. Capturing them at the right time helps to detect harmful or favourable online behaviours, hinder or facilitate the software development cycle, and moralize or demoralize the team in a software company. This study aims to identify emotions that appear during the online agile retrospective. Our study asks the research question: How often are different emotions repeated during the online agile retrospective? We conducted a multiple case study with two software companies. We analyzed three recorded online retrospective sessions to seize various emotions. Our findings show that eighteen emotions appear on the agile retrospective. Some of the highest repeated emotions are approval, realization, excitement, relief, disappointment, confusion, optimism, and disapproval.
- Open Access
- 28 December 2023
- Published by Springer Nature
- p. 87-96
The Know-How of Agile Retrospectives in Software Startups
Software startups are responsible for fast product delivery to the market. To aid this process, a retrospective inside a startup team can be very fruitful for software development. The traditional way of conducting agile retrospectives involves discussion based on what went well, what did not go well, and how to improve the software development cycle helps to save resources, get directed toward the startup vision, and overcome several challenges. To attain insights about the agile retrospective approach in startups, we studied the following question: How are software startups performing agile retrospectives? Hence, we conducted seven multiple case studies with 19 semi-structured interviews that lasted 30–65 min. The results outline that all software startups prefer a reflection through agile retrospectives but not in the traditional manner. Due to the startup’s casual and less restricted working environment, teams prefer informal agile retrospectives, which involve no confined boundaries of time, venue, and participants.
- 28 December 2023
- Published by Springer Nature
- p. 87-96
Open AccessThe Know-How of Agile Retrospectives in Software Startups
Software startups are responsible for fast product delivery to the market. To aid this process, a retrospective inside a startup team can be very fruitful for software development. The traditional way of conducting agile retrospectives involves discussion based on what went well, what did not go well, and how to improve the software development cycle helps to save resources, get directed toward the startup vision, and overcome several challenges. To attain insights about the agile retrospective approach in startups, we studied the following question: How are software startups performing agile retrospectives? Hence, we conducted seven multiple case studies with 19 semi-structured interviews that lasted 30–65 min. The results outline that all software startups prefer a reflection through agile retrospectives but not in the traditional manner. Due to the startup’s casual and less restricted working environment, teams prefer informal agile retrospectives, which involve no confined boundaries of time, venue, and participants.
- Open Access
- 27 December 2023
- Published by Wiley in Software: Practice and Experience
- Vol. 54 (5) , 896-926
Work‐from‐home impacts on software project: A global study on software development practices and stakeholder perceptions
Context: The COVID‐19 pandemic has had a disruptive impact on how people work and collaborate across all global economic sectors, including software business. While remote working is not new for software engineers, forced WFH situations come with both limitations and opportunities. As the ‘new normal’ for working might be based on the current state of Work‐from‐home (WFH), it is useful to understand what has happened and learn from that.Objective: This study aims to gain insights into how their WFH arrangement impacts project management and software engineering. We are also interested in exploring these impacts in different contexts, such as startups and established companies.Method: We conducted a global‐scale, cross‐sectional survey during the spring and summer 2021. Our results are based on quantitative and qualitative analysis of 297 valid responses.Results: We characterize the profile of WFH in both spatial and temporal aspects, together with a set of common collaborative tools and coordination and control mechanisms. We revealed some areas of project management that are relatively more challenging during WFH situations, such as coordination, communication and project planning. We also revealed a mixed picture of the perceived impact of WFH on different software engineering activities.Conclusion: WFH is a situational phenomenon which can have both negative and positive impact on software teams. For practitioners, we suggest a unified approach to consider the context of WFH, collaborative tools, associated coordination and control approaches and a process that resolve those aspects that are sensitive to physical interaction.
- 27 December 2023
- Published by Wiley in Software: Practice and Experience
- Vol. 54 (5) , 896-926
Open AccessWork‐from‐home impacts on software project: A global study on software development practices and stakeholder perceptions
Context: The COVID‐19 pandemic has had a disruptive impact on how people work and collaborate across all global economic sectors, including software business. While remote working is not new for software engineers, forced WFH situations come with both limitations and opportunities. As the ‘new normal’ for working might be based on the current state of Work‐from‐home (WFH), it is useful to understand what has happened and learn from that.Objective: This study aims to gain insights into how their WFH arrangement impacts project management and software engineering. We are also interested in exploring these impacts in different contexts, such as startups and established companies.Method: We conducted a global‐scale, cross‐sectional survey during the spring and summer 2021. Our results are based on quantitative and qualitative analysis of 297 valid responses.Results: We characterize the profile of WFH in both spatial and temporal aspects, together with a set of common collaborative tools and coordination and control mechanisms. We revealed some areas of project management that are relatively more challenging during WFH situations, such as coordination, communication and project planning. We also revealed a mixed picture of the perceived impact of WFH on different software engineering activities.Conclusion: WFH is a situational phenomenon which can have both negative and positive impact on software teams. For practitioners, we suggest a unified approach to consider the context of WFH, collaborative tools, associated coordination and control approaches and a process that resolve those aspects that are sensitive to physical interaction.
- Open Access
How Many Papers Should You Review? A Research Synthesis of Systematic Literature Reviews in Software Engineering
[Context] Systematic Literature Review (SLR) has been a major type of study published in Software Engineering (SE) venues for about two decades. However, there is a lack of understanding of whether an SLR is really needed in comparison to a more conventional literature review. Very often, SE researchers embark on an SLR with such doubts. We aspire to provide more understanding of when an SLR in SE should be conducted. [Objective] The first step of our investigation was focused on the dataset, i.e., the reviewed papers, in an SLR, which indicates the development of a research topic or area. The objective of this step is to provide a better understanding of the characteristics of the datasets of SLRs in SE. [Method] A research synthesis was conducted on a sample of 170 SLRs published in top-tier SE journals. We extracted and analysed the quantitative attributes of the datasets of these SLRs. [Results] The findings show that the median size of the datasets in our sample is 57 reviewed papers, and the median review period covered is 14 years. The number of reviewed papers and review period have a very weak and non-significant positive correlation. [Conclusions] The results of our study can be used by SE researchers as an indicator or benchmark to understand whether an SLR is conducted at a good time.
Open AccessHow Many Papers Should You Review? A Research Synthesis of Systematic Literature Reviews in Software Engineering
[Context] Systematic Literature Review (SLR) has been a major type of study published in Software Engineering (SE) venues for about two decades. However, there is a lack of understanding of whether an SLR is really needed in comparison to a more conventional literature review. Very often, SE researchers embark on an SLR with such doubts. We aspire to provide more understanding of when an SLR in SE should be conducted. [Objective] The first step of our investigation was focused on the dataset, i.e., the reviewed papers, in an SLR, which indicates the development of a research topic or area. The objective of this step is to provide a better understanding of the characteristics of the datasets of SLRs in SE. [Method] A research synthesis was conducted on a sample of 170 SLRs published in top-tier SE journals. We extracted and analysed the quantitative attributes of the datasets of these SLRs. [Results] The findings show that the median size of the datasets in our sample is 57 reviewed papers, and the median review period covered is 14 years. The number of reviewed papers and review period have a very weak and non-significant positive correlation. [Conclusions] The results of our study can be used by SE researchers as an indicator or benchmark to understand whether an SLR is conducted at a good time.