1. |
- Ahmad, Muhammad Ovais, Associate Professor/Lektor, et al.
(författare)
-
Early career software developers and work preferences in software engineering
- 2024
-
Ingår i: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 36:2
-
Tidskriftsartikel (refereegranskat)abstract
- Context: The software engineering researchers and practitioners echoed the needfor investigations to better understand the engineers developing software andservices. In light of current studies, there are significant associations between thepersonalities of software engineers and their work preferences. However, limitedstudies are using psychometric measurements in software engineering.Objective: We aim to evaluate attitudes of early-stage software engineers andinvestigate link between their personalities and work preferences.Method: We collected extensive psychometric data from 303 graduate-levelstudents in Computer Science programs at four Pakistani and one Swedish universityusing Five-Factor Model. The statistical analysis investigated associations betweenvarious personality traits and work preferences.Results: The data support the existence of two clusters of software engineers, one ofwhich is more highly rated across the board. Numerous correlations exist betweenpersonality qualities and the preferred types of employment for software developers.For instance, those who exhibit greater levels of emotional stability, agreeableness,extroversion, and conscientiousness like working on technical activities on a settimetable. Similar relationships between personalities and occupational choices arealso evident in the earlier studies. More neuroticism is reported in femalerespondents than in male respondents. Higher intelligence was demonstrated bythose who worked on the“entire development process”and“technical componentsof the project.”Conclusion: When assigning project tasks to software engineers, managers might usethe statistically significant relationships that emerged from the analysis of personalityattributes. It would be beneficial to construct effective teams by taking personalityfactors like extraversion and agreeableness into consideration. The study techniquesand analytical tools we use may identify subtle relationships and reflect distinctionsacross various groups and populations, making them valuable resources for bothfuture academic research and industrial practice.
|
|
2. |
- Ahmad, Muhammad Ovais, Associate Professor/Lektor
(författare)
-
5G Secure Solution Development and Security Master Role
- 2024
-
Ingår i: International Conference on Evaluation and Assessment in Software Engineering.
-
Konferensbidrag (refereegranskat)abstract
- This paper explores the relationship between self-organisation andtailored roles in large agile software development teams. The casestudy examines a Swedish IT company that has introduced the roleof “Security Master” in Scrum teams. The teams are developing avery large and secure 5G solution. Twenty semi-structuredinterviews were conducted and deductively analysed. The resultsshed light on the Security Master role, its need, responsibilities andimpact on secure coding. The paper concludes with a discussion oflessons learned and recommendations for future research in thecontext of large, security-sensitive projects.
|
|
3. |
- Ahmad, Muhammad Ovais, Associate Professor/Lektor
(författare)
-
5G Secure Solution Development and Security Master Role
- 2024
-
Ingår i: EASE '24: Proceedings of the 28th International Conference on Evaluation and Assessment in Software Engineering. - : Association for Computing Machinery (ACM). - 9798400717017 ; , s. 629-633
-
Konferensbidrag (refereegranskat)abstract
- This paper explores the relationship between self-organisation and tailored roles in large agile software development teams. The case study examines a Swedish IT company that has introduced the role of "Security Master"in Scrum teams. The teams are developing a very large and secure 5G solution. Twenty semi-structured interviews were conducted and deductively analysed. The results shed light on the Security Master role, its need, responsibilities and impact on secure coding. The paper concludes with a discussion of lessons learned and recommendations for future research in the context of large, security-sensitive projects.
|
|
4. |
- Ahmad, Muhammad Ovais, Associate Professor/Lektor
(författare)
-
A Deep Dive into Self-Regulated Learning : ReflectiveDiaries Role and Implementation Strategies
- 2024
-
Ingår i: Communications of the Association for Information Systems. - : Association for Information Systems. - 1529-3181. ; 54, s. 868-888
-
Tidskriftsartikel (refereegranskat)abstract
- Reflective learning diaries can help students develop self-regulated learning (SRL), a critical skill for success. Forteachers such learning diaries can be a valuable tool for formative evaluation of SRL. However, there is limitedresearch on the use of reflective diaries in software engineering and information systems education. To address thisgap, we conducted a case study in which reflective learning diaries were used in a course. The goal of this research isto investigate the potential of using reflective diaries to formatively evaluate three key features of SRL: conceptions ofknowledge, conceptions of learning, and strategies for monitoring and regulating learning. Our findings suggest thatreflective diaries is a valuable tool for formative evaluation of SRL in software engineering education. Reflection onlearning experiences helps students develop self-awareness of their SRL skills and identify areas for improvement.Instructors can use this information to provide students with targeted feedback and support. By using reflective diariesto promote dialogic feedback, instructors can help students to develop a deeper understanding of their own learningand to become more effective self-regulated learners. The study conclude with lesson learned that provide practicalrecommendations for educators who are swiftly moving towards online teaching.
|
|
5. |
- Ahmad, Muhammad Ovais, Associate Professor/Lektor, et al.
(författare)
-
Beyond Technical Debt Unravelling Organisational Debt Concept
- 2024
-
Ingår i: 39th ACM/SIGAPP Symposium On Applied Computing.
-
Konferensbidrag (refereegranskat)abstract
- The development of software and systems is a complex task that involves social, technical and organisational factors. Technical debt is a well-known concept that refers to the negative consequences of taking shortcuts in software development. However, organisational debt (OD) is a less well-known phenomenon that arises due to shortcuts in the organisational structure and processes of a software organisation. The lack of a clearly defined OD makes it difficult to identify and manage this type of debt. This study presents a multi-vocabulary literature review that consolidates an understanding of the nature of OD and its impact on software organisations. OD encompasses a set of attributes, precedents and outcomes. In addition, this study highlights the five causes and mitigation strategies of OD. The results of this study indicate that software companies are facing a major issue with OD. Future research should include empirical studies to validate techniques that can assist software professionals in managing OD to address this issue.
|
|
6. |
- Ahmad, Muhammad Ovais, Associate Professor/Lektor, et al.
(författare)
-
Beyond Technical Debt Unravelling Organisational Debt Concept
- 2024
-
Ingår i: SAC '24: Proceedings of the 39th ACM/SIGAPP Symposium on Applied Computing. - : Association for Computing Machinery (ACM). - 9798400702433 ; , s. 802-809
-
Konferensbidrag (refereegranskat)abstract
- The development of software and systems is a complex task that involves social, technical and organisational factors. Technical debt is a well-known concept that refers to the negative consequences of taking shortcuts in software development. However, organisational debt (OD) is a less well-known phenomenon that arises due to shortcuts in the organisational structure and processes of a software organisation. The lack of a clearly defined OD makes it difficult to identify and manage this type of debt. This study presents a multi-vocabulary literature review that consolidates an understanding of the nature of OD and its impact on software organisations. OD encompasses a set of attributes, precedents and outcomes. In addition, this study highlights the five causes and mitigation strategies of OD. The results of this study indicate that software companies are facing a major issue with OD. Future research should include empirical studies to validate techniques that can assist software professionals in managing OD to address this issue.
|
|
7. |
- Ahmad, Muhammad Ovais, Associate Professor/Lektor, et al.
(författare)
-
Nexus Between Psychological Safety and Non-Technical Debt in Large-Scale Agile Enterprise Resource Planning Systems Development
- 2024
-
Ingår i: Software, System, and Service Engineering. - : Springer. - 9783031510755 - 9783031510748 ; , s. 63-81
-
Konferensbidrag (refereegranskat)abstract
- Psychological safety, a pivotal factor in team dynamics, has been proposed as a crucial determinant of success in agile software development (ASD) teams and learning. However, the extent of its influence within the domain of large-scale agile (LSA) software development teams remains underexplored. This research investigates the multifaceted dimensions of psychological safety within LSA teams, examining both its precursors and outcomes. This study conducted semi-structured interviews with software professionals actively involved in LSA projects within a Swedish software consultancy company. The findings underscore the intricate nature of establishing a psychologically safe environment within LSA teams, revealing it as a multidimensional construct necessitating a proactive leadership approach, fostering open communication, and cultivating an ecosystem of constructive feedback. The study highlights the critical importance of intentionally shaping teams to facilitate continuous learning, ensuring remuneration safety, and implementing a comprehensive onboarding process for incoming team members. By fostering psychologically safe settings, LSA teams enhanced teamwork dynamics, heightened job satisfaction, and facilitation continuous learning and development. Notably, the absence of such an environment exacerbates the phenomenon of brain drain, exposing the tangible consequences of overlooking this fundamental aspect of organizational culture. This study proposes avenues for future research directions, aiming to further unravel the nuances of psychological safety and its cascading effects within the realm of contemporary LSA software development context.
|
|
8. |
- Ahmad, Muhammad Ovais, Associate Professor/Lektor, et al.
(författare)
-
The Pandora's box of social, process, and people debts in software engineering
- 2024
-
Ingår i: Journal of Software. - : John Wiley & Sons. - 2047-7473 .- 2047-7481. ; 36:2
-
Tidskriftsartikel (refereegranskat)abstract
- In software engineering, technical debt (TD) has been widely investigated, but debt regarding social issues, people, and processes has not been explored as much. It should be noted here that we use nontechnical debt (NTD) as an umbrella term to cover social, process, and people debts. Although the number of studies on NTD in software is increasing, the majority of them are descriptive rather than rigorous, and there is no systematic development of cumulative knowledge. As a result, identifying the fundamental causes of NTD and the associated mitigation techniques in software engineering is challenging. Therefore, this study investigates the scientific evidence regarding NTD till date by conducting a systematic mapping review of software engineering research between January 2000 and October 2021. The search strategy resulted in 175 studies, 17 of which were identified as unique and relevant primary papers. The primary studies show that NTD and TD are inextricably linked. In addition, this study also captured a plethora of causes and mitigation strategies for managing NTD and thus makes four important contributions: (i) highlighting state-of-the-art NTD research; (ii) identification of the reported causes and mitigation strategies in the primary papers; and (iii) determination of opportunities for future NTD research.
|
|
9. |
- Jarzębowicz, Aleksander, et al.
(författare)
-
Preface
- 2024
-
Ingår i: Conference proceedings-Software, System, and Service Engineering. - : Springer. - 9783031510748 - 9783031510755 ; , s. v-vi
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)
|
|
10. |
- Saeeda, Hina, et al.
(författare)
-
A Multivocal Literature Review on Non-Technical Debt in Software Development : An Insight into Process, Social, People, Organizational, and Culture Debt
- 2024
-
Ingår i: e-Informatica Software Engineering Journal. - : Technical University of Wroclaw. - 1897-7979 .- 2084-4840. ; 18:1
-
Forskningsöversikt (refereegranskat)abstract
- Software development encompasses various factors beyond technical considerations. Neglecting non-technical elements like individuals, processes, culture, and social and organizational aspects can lead to debt-like characteristics that demand attention. Therefore, we introduce the non-technical debt (NTD) concept to encompass and explore these aspects. This indicates the applicability of the debt analogy to non-technical facets of software development. Technical debt (TD) and NTD share similarities and often arise from risky decision-making processes, impacting both software development professionals and software quality. Overlooking either type of debt can lead to significant implications for software development success. The current study conducts a comprehensive multivocal literature review (MLR) to explore the most recent research on NTD, its causes, and potential mitigation strategies. For analysis, we carefully selected 40 primary studies among 110 records published until October 1, 2022. The study investigates the factors contributing to the accumulation of NTD in software development and proposes strategies to alleviate the adverse effects associated with it. This MLR offers a contemporary overview and identifies prospects for further investigation, making a valuable contribution to the field. The findings of this research highlight that NTD's impacts extend beyond monetary aspects, setting it apart from TD. Furthermore, the findings reveal that rectifying NTD is more challenging than addressing TD, and its consequences contribute to the accumulation of TD. To avert software project failures, a comprehensive approach that addresses NTD and TD concurrently is crucial. Effective communication and coordination play a vital role in mitigating NTD, and the study proposes utilizing the 3C model as a recommended framework to tackle NTD concerns.
|
|