Data annotation, the systematic labeling of raw data (e.g., images, text) [1] , is foundational to the training of machine learning (ML) models, particularly in supervised learning. While data’s importance is clear, the specific processes and requirements for how this data should be annotated, appear inconsistently defined or informal within existing ML software system (MLS) development methodologies [2] . The effective specification of data annotation requirements, the challenges involved, and the traceability from system requirements to annotation activities represent critical considerations in the ML development lifecycle. Understanding these aspects is pertinent for AI/ML engineers and data scientists, requirements engineers, and organizations developing AI solutions.

Process debt (PD) in agile software development represents inefficiencies that undermine team performance and job satisfaction. This study investigates the quantitative impact of PD on job satisfaction within agile teams, surveying 191 participants from two software development organizations. Our research examines five PD types: Process Unsuitability, Roles Debt, Synchronization Debt, Documentation Debt, and Infrastructure Debt. Using multiple regression analysis, our model explains approximately 33.8 % of the variance in job satisfaction. Among the five PD types, Process Unsuitability and Roles Debt emerged as statistically significant predictors of reduced job satisfaction. These findings indicate that certain forms of PD have a measurable negative impact on developers' perceptions of their work environment. By identifying which PD types most strongly influence job satisfaction, this research offers empirically grounded insights that can inform targeted interventions. Understanding and addressing the most impactful PD categories may help organizations refine agile processes, thereby mitigating the detrimental effects of process inefficiencies on job satisfaction.

Background: Agile methodologies emphasise iterative development, customer collaboration, and flexibility in software development. However, challenges arise when agile practices are adopted in larger projects. Process inefficiencies and redundancies, known as process debt, result from the compounded complexities of expanding agile processes and workflows. However, strategies to understand and tackle it remain markedly inadequate.

Abstract Agile methodologies have emerged as transformative paradigms in the ever-evolving software development landscape, emphasizing iterative development, customer collaboration, and adaptability. As the scope and complexity of projects and organizations expand, applying agile principles within the context of Large-Scale Agile Development (LSAD) encounters distinctive challenges. The majority of challenges encountered in LSAD, technical and non-technical, are attributed to the accrual of social debt. However, a conspicuous gap remains in understanding and addressing social debt in LSAD. This study aims to fill this void by investigating social debt in LSAD through an in-depth industrial case study with a leading Nordic company specializing in telecommunications software and services and focusing on producing secure 5G network solutions. The study investigates the causes of LSAD’s social debt and examines its impacts on secure 5G telecom software development. By addressing these objectives, this research sheds light on a critical aspect of LSAD’s social debt, caused by 3C challenges(communication, coordination and collaboration), social confines challenges, community smells challenges, and organisational social challenges in the telecom sector that have been underrepresented in the existing literature.

This research paper examines the implementation and impact of customised roles in large-scale agile software development teams, specifically within the Scrum framework. This is a single case study based on 15 practitioners' interviews from a Swedish software company to review the dynamics of role customisation. The two customised roles of Product Guardians and Security Masters are crucial for addressing complex secure software development, maintaining product quality and security, and fostering team self-organisation. The study also uncovers challenges associated with role customisation, such as the potential overburdening of individuals and disruption of selforganisation. The findings contribute to the discourse on agile methods' adaptability and provide practical insights for organisations considering similar role customisations. Furthermore, the research opens the door for future exploration of organization-wide roles that promote selforganisation.

Abstract Software requirement engineering (SRE) is the initial stage of the software engineering process and entails several challenges relating to the identification, implementation, evolution, and management of requirements for the development of software systems that meet the desired functionality quality standards. Agile software development (ASD) is a well‐known software development process that follows a lightweight and adaptive methodology to support the incremental development of software systems. Since the ASD follows an adaptive procedure (ie, a flexible, nanostructured, and dynamic approach) of software development, it becomes challenging to perform SRE that follows a structured approach for managing software requirements throughout the life cycle of software development. The primary challenges for SRE, while pursuing an ASD, include, but are not limited to, identification of incomplete requirements, implementation of vague requirements, prioritization of secondary functional requirements, and compromise on users' involvement that negatively impacts the software system's functionality and quality. To overcome these challenges, some of the recent research efforts have focused on managing different phases of SRE during software development using the ASD. However, there is a lack of solutions that provide software engineers/practitioners with a solution. Besides, frameworks to effectively manage all the phases of SRE as per the needs of the ASD are needed. We propose a framework that unifies joint requirements document (JRD) and SCRUM to incrementally (a) identify, (b) implement, (c) evolve, and (d) manage system requirements throughout the software development cycle. We have used the action research method to qualitatively validate the proposed framework based on data and user requirements collected from a product‐focused (multinational) Norway‐based software company. The results of the validation are based on statistical analysis that reflects the usefulness of the proposed framework for SRE in ASD‐based software engineering and development. Future research is the possible application of a machine learning approach (es) in the intended context for agile requirements elicitations.