Search

Agile Transformations are challenging processes for organizations that look to extend the benefits of Agile philosophy and methods beyond software engineering. Despite the impact of these transformations on organizations, they have not been extensively studied in academia. We conducted a study grounded in workshops and interviews with 99 participants from 30 organizations, including organizations undergoing transformations ("final organizations") and companies supporting these processes ("consultants"). The study aims to understand the motivations, objectives, and factors driving and challenging these transformations. Over 700 responses were collected to the question and categorized into 32 objectives. The findings show that organizations primarily aim to achieve customer centricity and adaptability, both with 8% of the mentions. Other primary important objectives, with above 4% of mentions, include alignment of goals, lean delivery, sustainable processes, and a flatter, more team-based organizational structure. We also detect discrepancies in perspectives between the objectives identified by the two kinds of organizations and the existing agile literature and models. This misalignment highlights the need for practitioners to understand with the practical realities the organizations face. [ABSTRACT FROM AUTHOR]

Agile methodologies, initially designed for the project level, face challenges when applied at enterprise levels where complex projects and diverse stakeholders are involved. To meet this challenge, several large-scale agile methodologies have been proposed. However, these approaches are not flexible enough or tailored to the needs of organizations, projects, and their teams. It is in this context that hybrid methodologies have emerged. This study aims to conduct a systematic literature review to trace the evolution of hybrid scaling of agile and characterize different approaches to implement it. This study starts by assessing 1509 studies through the use of the PRISMA 2020 framework and identifies 38 relevant studies in this field. The findings indicate that the majority of studies are from 2021 onwards and that qualitative methodologies supported by case studies predominate, making it possible to characterize tailoring processes in these organizations. Moreover, the implementation of hybrid scaling of agile is supported by the paradigm of ambidextrous strategy, a combination of agile with traditional project management methodologies, and continuous improvements. This study contributes insights into navigating the complexities of agile scaling, offering practical guidance for organizations seeking to optimize their project management practices. [ABSTRACT FROM AUTHOR]

The article discusses the importance of emerging technologies such as AI, big data, blockchain, and AR in software and systems development processes. It highlights how these technologies can revolutionize traditional development practices and improve efficiency, security, and reliability. The special issue of the Journal of Software: Evolution and Process features high-quality articles from the 17th International Conference on Software and System Processes (ICSSP) in 2023, showcasing innovative approaches to incorporating new technologies into software engineering practices. The articles emphasize the significance of technological innovation and human-centered approaches for advancing the field of software development. [Extracted from the article]

Auxiliary functions in software systems, often overlooked due to their perceived simplicity, play a crucial role in overall system reliability. This study focuses on the effectiveness of agile practices, specifically the pair programming and the test-first programming practices. Despite the importance of these functions, there exists a dearth of empirical evidence on the impact of agile practices on their development, raising questions about their potential to enhance correctness without affecting time-to-market. This paper aims to bridge this gap by comparing the application of agile practices with traditional approaches in the context of auxiliary function development. We conducted six experiments involving 122 participants (85 novices and 37 professionals) who used both traditional and agile methods to develop six auxiliary functions across three different domains. Our analysis of 244 implementations suggests the potential benefits of agile practices in auxiliary function development. Pair programming showed a tendency towards improved correctness, while test-first programming did not significantly extend the total development time, particularly among professionals. However, these findings should be interpreted cautiously as they do not conclusively establish that agile practices outperform traditional approaches universally. As indicated by our results, the potential benefits of agile practices may vary depending on factors such as the programmer's experience level and the nature of the functions being developed. Further research is needed to fully understand the contexts in which these practices can be most effectively applied and to address the potential limitations of our study. [ABSTRACT FROM AUTHOR]

Background: Research shows that emotional intelligence (EI) should be used alongside cognitive intelligence during requirements change (RC) handling in Software Engineering (SE), especially in agile settings. Objective: We wanted to study the role of EI in-depth during RC handling. Method: We conducted a mixed-methods study (an interview study followed by a survey study) with 124 software practitioners. Findings: We found the causal condition, intervening condition and causes lead to key direct consequences of regulating own emotions, managing relationships, and extended consequences of sustaining productivity, setting and sustaining team goals. We found several strategies of supporting EI during RC handling. Further, we found strong correlations between six strategies and one being aware of own emotions, regulating own emotions, sustaining team productivity, and setting and sustaining team goals. Conclusion: Empathising with others and tracking commitments and decisions as a team are key strategies that have strong correlations between managing emotions, between sustaining team productivity, and between setting and sustaining team goals. To the best of our knowledge, the framework we present in this paper is the first theoretical framework on EI in SE research. We provide recommendations for software practitioners to consider during RC handling. [ABSTRACT FROM AUTHOR]

Agile Software Development (ASD) confronts the challenge of effectively measurement and predicting the capabilities of software engineers and teams to improve individual performance, team efficiency, and project success. This study delves into exploring and identifying gaps and research prospects in assessing and predicting human capabilities within ASD. Thus, we conducted a Systematic Literature Review, building upon a prior review from 2001 to 2016 by different authors. To encompass primary studies published after 2016, we extended to 2022. Further, our study extends the scope of the previous SLR with a new research question to identify key attributes in publications focused on agile team formation. Our findings disclosed new attributes for evaluating and predicting the capabilities of professionals engaged in ASD, such as Openness to Creativity and Agile Adaptation. These attributes boost individual performance, contribute to ameliorated team productivity, and facilitate the precise composition of teams. Moreover, this study expands our prior study, providing more details on capability identification and research design, extends the analysis of attributes and prediction models, provides a more granular discussion of discoveries and comparisons with prior review, and more indepth discussion about practical implications and thoroughly examines study validity. We observed that technical metrics were more prevalent than social and innovative aspects. Also, the study identified the prediction of agile capabilities as an emerging research domain necessitating further scrutiny due to the scarcity of existing models. The majority of studies (78%) supplied detailed metric descriptions, facilitating the evolution of the capabilities repository and supporting future investigations in this domain. Ultimately, these findings can aid agile practitioners in formulating team composition decisions based on individuals’ and teams’ appraised and foreseen abilities.

One of the significant challenges in scaling agile software development is organizing software development teams to ensure effective communication among members while equipping them with the capabilities to deliver business value independently. A formal approach to address this challenge involves modeling it as an optimization problem: given a professional staff, how can they be organized to optimize the number of communication channels, considering both intra-team and inter-team channels? In this article, we propose applying a set of bio-inspired algorithms to solve this problem. We introduce an enhancement that incorporates ensemble learning into the resolution process to achieve nearly optimal results. Ensemble learning integrates multiple machine-learning strategies with diverse characteristics to boost optimizer performance. Furthermore, the studied metaheuristics offer an excellent opportunity to explore their linear convergence, contingent on the exploration and exploitation phases. The results produce more precise definitions for team sizes, aligning with industry standards. Our approach demonstrates superior performance compared to the traditional versions of these algorithms. [ABSTRACT FROM AUTHOR]

Enterprise architecture is a growing trend that aims to help deal with the complexity of socio‐technical systems such as human organizations, as well as their information technology and systems areas. Nevertheless, the contribution of enterprise architecture to the field of software engineering remains unclear. The purpose of this systematic literature review is to see how enterprise architecture is used in software development and maintenance practice. To this end, we first carried out a search in the SCOPUS database and then organized the papers according to the Software Engineering Body of Knowledge to determine what areas of software engineering are covered by each research study. To understand how enterprise architecture is used, we established a classification based on ISO 42010 and TOGAF. From the systematic literature review, we noticed that the early stages of development are the most impacted by the enterprise architecture. On the other hand, we observed that enterprise architecture is of assistance in the areas of engineering management, engineering processes, and engineering models and methods; these tasks are carried out by teams or managers using different, often agile, development methods or standards. In turn, we found that the most common categories are architecture descriptions; these are often used to facilitate communication and information‐sharing between different stakeholders, in addition to frameworks, which will help to establish common practices in the organization related to the joint use of enterprise architecture and software development. [ABSTRACT FROM AUTHOR]

One of the main obstacles in software development projects is requirement volatility (RV), which is defined as uncertainty or changes in software requirements during the development process. Therefore, this research tries to understand the underlying factors behind the RV and the best practices to reduce it. The methodology used for this research is based upon qualitative research using interviews with 12 participants with experience in agile software development projects. The participants hailed from Austria, Nigeria, the USA, the Philippines, Armenia, Sri Lanka, Germany, Egypt, Canada, and Turkey and held roles such as project managers, software developers, Scrum Masters, testers, business analysts, and product owners. Our findings based on our empirical data revealed six primary factors that cause RV and three main agile practices that help to mitigate it. Theoretically, this study contributes to the body of knowledge relating to RV management. Practically, this research is expected to aid software development teams in comprehending the reasons behind RV and the best practices to effectively minimize it. [ABSTRACT FROM AUTHOR]

Agile Software Development (ASD) confronts the challenge of effectively measurement and predicting the capabilities of software engineers and teams to improve individual performance, team efficiency, and project success. This study delves into exploring and identifying gaps and research prospects in assessing and predicting human capabilities within ASD. Thus, we conducted a Systematic Literature Review, building upon a prior review from 2001 to 2016 by different authors. To encompass primary studies published after 2016, we extended to 2022. Further, our study extends the scope of the previous SLR with a new research question to identify key attributes in publications focused on agile team formation. Our findings disclosed new attributes for evaluating and predicting the capabilities of professionals engaged in ASD, such as Openness to Creativity and Agile Adaptation. These attributes boost individual performance, contribute to ameliorated team productivity, and facilitate the precise composition of teams. Moreover, this study expands our prior study, providing more details on capability identification and research design, extends the analysis of attributes and prediction models, provides a more granular discussion of discoveries and comparisons with prior review, and more indepth discussion about practical implications and thoroughly examines study validity. We observed that technical metrics were more prevalent than social and innovative aspects. Also, the study identified the prediction of agile capabilities as an emerging research domain necessitating further scrutiny due to the scarcity of existing models. The majority of studies (78%) supplied detailed metric descriptions, facilitating the evolution of the capabilities repository and supporting future investigations in this domain. Ultimately, these findings can aid agile practitioners in formulating team composition decisions based on individuals’ and teams’ appraised and foreseen abilities. [ABSTRACT FROM AUTHOR]

Nowadays, with global software development, software process improvement models have again focused the scientific community's attention. The need to increase the probability of success in these projects appears as the main reason to use a software process improvement model. In this article, a quick literature review was conducted to find evidence of using traditional process improvement models in agile software development. A total of fifteen primary studies were meticulously selected, from which significant insights were extracted for this research. This work's main contribution is identifying the challenges of using a software process improvement model. In conclusion, despite the evidence on the use of models, there is still a need to facilitate their integration into agile models such as Scrum. [ABSTRACT FROM AUTHOR]

The Agile Manifesto (AM) provides principles guiding agile software development as an alternative to traditional software development processes. While attempts have been made to adapt processes to the agile context, representation of AM principles remains underdeveloped and subjective. The Semat (Software Engineering Method and Theory) Essence kernel offers a common ground for representing software development endeavors. In this paper, we represent some AM principles using the language provided by the Semat Essence kernel to establish a common ground. Additionally, we define constraints in OCL (Object Constraint Language) to enhance the Semat Essence kernel, enabling the introduction of time management in our representation. Such a representation will allow us for adapting and assessing different processes in an agile context. [ABSTRACT FROM AUTHOR]

Scaled agile development approaches are now used widely in modern software engineering, allowing businesses to improve teamwork, productivity, and product quality. The incorporation of artificial intelligence (AI) into scaled agile development methods (SADMs) has emerged as a potential strategy in response to the ongoing demand for simplified procedures and the increasing complexity of software projects. This paper explores the intersection of AI-driven assistants within the context of the scaled agile framework (SAFe) for large-scale software development, as it stands out as the most widely adopted framework. Our paper pursues three principal objectives: (1) an evaluation of the challenges and impediments encountered by organizations during the implementation of SADMs, (2) an assessment of the potential advantages stemming from the incorporation of AI in large-scale contexts, and (3) the compilation of aspects of SADMs that AI-driven assistants enhance. Through a comprehensive systematic literature review, we identified and described 18 distinct challenges that organizations confront. In the course of our research, we pinpointed seven benefits and five challenges associated with the implementation of AI in SADMs. These findings were systematically categorized based on their occurrence either within the development phase or the phases encompassing planning and control. Furthermore, we compiled a list of 15 different AI-driven assistants and tools, subjecting them to a more detailed examination, and employing them to address the challenges we uncovered during our research. One of the key takeaways from this paper is the exceptional versatility and effectiveness of AI-driven assistants, demonstrating their capability to tackle a broader spectrum of problems. In conclusion, this paper not only sheds light on the transformative potential of AI, but also provides invaluable insights for organizations aiming to enhance their agility and management capabilities. [ABSTRACT FROM AUTHOR]

Context: The recent research trend has highlighted that multiple stakeholders are involved during requirement gathering in agile software development. Hence, leading to an increased number of duplicate user stories in agile product backlog during requirement gathering. Objective: The objective of this paper is to evaluate the existing techniques employed in identifying and eliminating the duplicate user stories from agile product backlog and to overcome the existing gaps with the help of a newly proposed clustering algorithm. Method: An agile user story is expressed as a function of input and output parameters. That said multiple user stories having similar set of input parameters are most likely to be duplicate causing a redundancy. The newly proposed algorithm is used for clustering user stories having similar set of input parameters through various iterations and then removing the identified duplicate user stories from agile product backlog. This paper also introduces the concept of mass clustering which means clustering a number of user stories in single run. Results: Experimental results prove the proposed model is capable of handling small and large releases ranging between 100 to 1000 user stories with similar efficiency. The proposed clustering algorithm outperformed the clustering algorithms and resulted in 37% decrease in agile product backlog by eliminating duplicate user stories causing redundancy. The experimental results are obtained from the logs of the MATLAB tool. However, the provided algorithm is generic in nature and can be implemented using R, Python or SAS programming tools. The provided algorithms employs proven matrix operations. Conclusion: The proposed clustering algorithm overcomes the limitation of existing user story management methods and clearly out performs when compared with other clustering algorithms. Finally, this paper gives recommendations about the usage of the provided clustering algorithm during agile release planning for eliminating duplicate user stories from agile product backlog. [ABSTRACT FROM AUTHOR]

The term agile is frequently used in IT especially in the area of software engineering. The broad pervasiveness of the term agile is astonishing, because it is not well defined in the area of software engineering. The fuzziness of the term agile comes with the danger of ill‐founded decisions and ideological discussions. Both slow down the gain in knowledge in the domain of software engineering. The term agile should therefore not be used either in science nor in the industry. This article provides a critical discussion of the term agile. By using a three‐layered abstraction concept for software development processes, the use of the term agile can be avoided. [ABSTRACT FROM AUTHOR]

Summary: The importance of the team, its internal dynamics, and its performance are widely recognized within the software engineering community. While popular frameworks identify wholeness, stability over time, and smallness as important factors, they offer little guidance on how to form teams that achieve these three characteristics. The objective of this study is to investigate how these team characteristics interact in large‐scale software development contexts, particularly focusing on the impact of stable and dynamic teaming approaches. This was done through a multivocal study of literature, followed by individual semi‐structured interviews with 19 engineers from two companies and validation workshops with an additional two companies from unrelated industry segments. The study results show that the question of stable versus dynamic approaches to forming software engineering teams is largely unaddressed in industry, with stable teams representing a habitual default option. Meanwhile, both stable and dynamic teams clearly have respective strengths and weaknesses, calling for careful consideration of the most suitable approach in any given situation. To support such consideration, this paper presents a model of how team stability, wholeness, and smallness interact. This model is found relevant, accurate, generalizable, and useful by practitioners. [ABSTRACT FROM AUTHOR]

The software industry is increasingly facing the need for continuous deployment of systems. This leads to the adoption of continuous activities, including planning, integration, and deployment (a.k.a. Continuous Software Engineering (CSE)). At the same time, systems should exhibit high-quality architectures, which are often achieved through architecture evaluation methods. However, there is little insight of how such evaluation happens in the context of CSE. To cover this gap, we investigate in this work the state of the art of continuous evaluation of software architectures in CSE, including agile processes like SCRUM. For this, we systematically examine the literature to collect and summarize evidence. Our results show a diversity of means for evaluating architectures in continuous mode to support the continuous evolution of systems. We also found how such evaluation has been incorporated within continuous development processes and agile processes like SCRUM and Crystal. We finally derive the main trends and open issues in the area, aiming to support the community to better understand and further consolidate the field of continuous evaluation of software architectures. [ABSTRACT FROM AUTHOR]

Various approaches toward the development of sustainable software systems have been proposed by the requirements engineering community over the last decade. We conducted a systematic mapping study, analyzed 55 publications, and identified 29 approaches that have been published since the year 2000. We analyzed how the approaches evolved over time and how the publications and authors are influenced by each other. Furthermore, the approaches are analyzed in terms of their supported requirements engineering activities, along with the evidence provided in the publications. Additionally, we also analyzed which sustainability definitions have been used, if an iterative application of the approaches is discussed, and if the approaches also provide a tool-support for practitioners. We noticed an increase of publications on requirements engineering approaches toward sustainability in the last years, whereas a majority discuss sustainability based on the same multi-dimensional concept. Although different case studies have been already conducted, we noticed a lack of an industrial application. Our main findings concern the need of an evaluation on how the proposed requirements engineering approaches can also be applied in agile software development processes. Additionally, we also promote the development of supporting software tools to support practitioners in adapting the proposed approaches. [ABSTRACT FROM AUTHOR]

By adopting agile and lean practices, DevOps aims to achieve rapid value delivery by speeding up development and deployment cycles, which however lead to more security concerns that cannot be fully addressed by an isolated security role only in the final stage of development. DevSecOps promotes security as a shared responsibility integrated into the DevOps process that seamlessly intertwines development, operations, and security from the start throughout to the end of cycles. While some companies have already begun to embrace this new strategy, both industry and academia are still seeking a common understanding of the DevSecOps movement. The goal of this study is to report the state‐of‐the‐practice of DevSecOps, including the impact of DevOps on security, practitioners' understanding of DevSecOps, and the practices associated with DevSecOps as well as the challenges of implementing DevSecOps. The authors used a mixed‐methods approach for this research. The authors carried out a grey literature review on DevSecOps, and surveyed the practitioners of DevSecOps in industry of China. The status quo of DevSecOps in industry is summarized. Three major software security risks are identified with DevOps, where the establishment of DevOps pipeline provides opportunities for security‐related activities. The authors classify the interpretations of DevSecOps into three core aspects of DevSecOps capabilities, cultural enablers, and technological enablers. To materialise the interpretations into daily software production activities, the recommended DevSecOps practices from three perspectives—people, process, and technology. Although a preliminary consensus is that DevSecOps is regarded as an extension of DevOps, there is a debate on whether DevSecOps is a superfluous term. While DevSecOps is attracting an increasing attention by industry, it is still in its infancy and more effort needs to be invested to promote it in both research and industry communities. [ABSTRACT FROM AUTHOR]

Agile methods and software product line engineering (SPLE) are widely recognized as practical approaches for delivering high-quality software, adapting to evolving stakeholder needs, and tackling complex problems. This study proposes a hybrid agile software development and reuse approach called SPLE-Scrum based on the activities of software product line engineering and Scrum. Within the SPLE process, we incorporate requirement engineering and design practices to create a reference architecture with reusable components called core assets by introducing a product management meeting. The core assets are reused to build a series of applications with various product lines. The product increments are delivered in each Sprint with the review and retrospective meetings based on Scrum lifecycle and practices. We present a case study involving a blockchain online store to demonstrate the practical application of SPLE-Scrum, highlighting the benefits of integrating Scrum and software product line engineering. The research hypotheses of the proposed approach were validated through a study of structured interviews with 5 experts and 44 software practitioners, showing that the key factors of product management, project requirements, and product architecture in the SPLE-Scrum approach have a beneficial impact on project success. The SPLE-Scrum approach provides valuable insights and practical guidance for organizations seeking to optimize their software engineering practices while incorporating agile development and software reuse capabilities. [ABSTRACT FROM AUTHOR]

Copyright of Revista Educación en Ingeniería is the property of Asociacion Colombiana de Facultades de Ingenieria and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Agile software requirements engineering processes enable quick responses to reflect changes in the client's software requirements. However, there are challenges associated with agile requirements engineering processes, which hinder fast, sustainable software development. Research addressing the challenges with available solutions is patchy, diverse and inclusive. In this study, we use a systematic literature review coupled with thematic classification and gap mapping analysis to examine extant solutions against challenges; the typologies/classifications of challenges faced with agile software development in general and specifically in requirements engineering and how the solutions address the challenges. Our study covers the period from 2009 to 2023. Scopus—the largest database for credible academic publications was searched. Using the exclusion criteria to filter the articles, a total of 78 valid papers were selected and reviewed. Following our investigation, we develop a framework that takes a three-dimensional view of agile requirements engineering solutions and suggest an orchestrated approach balancing the focus between the business context, project management and agile techniques. This study contributes to the theoretical frontier of agile software requirement engineering approaches and guidelines for practice. [ABSTRACT FROM AUTHOR]

Metrics are key elements that can give us valuable information about the effectiveness of agile software development processes, particularly considering the Scrum environment. This study aims to learn about the metrics adopted to assess agile development processes and explore the impact of how the role performed by each member in Scrum contributed to increasing/reducing the perception of the importance of these metrics. The impact of years of experience in Scrum on this perception was also explored. To this end, a quantitative study was conducted with 191 Scrum professionals in companies based in Portugal. The results show that the Scrum role is not a determining factor, while individuals with more years of experience have a higher perception of the importance of metrics related to team performance. The same conclusion is observed for the business value metric of the product backlog and the percentage of test automation in the testing phase. The findings allow for extending the knowledge about Scrum project management processes and their teams, in addition to offering important insights into the implementation of metrics for software engineering companies that adopt Scrum. [ABSTRACT FROM AUTHOR]

Analyzing the software development process and estimating the effort required for its completion is an essential task. In the case of Agile methodology, the values of the parameters used for estimation vary frequently as the scope of the project changes with changes in the requirements of the clients. Hence, the estimation done at the initial phase will not be appropriate until the completion of the project. Therefore, to overcome this issue, a methodology is proposed to estimate the duration of a project by applying machine learning techniques. The use-case point method is used for estimating the duration. Information about the number of use cases and values for environmental and technical factors is stored in a repository. Few values may be uncertain, and to estimate the effort for a new project with few unknown or uncertain values, the machine learning algorithm Gaussian Process Regression (GPR) is used. The repository information is taken as the training dataset, and the new project data is taken as the test dataset. The estimated value shows the accurate duration for the new project. The result is validated with a popular dataset. [ABSTRACT FROM AUTHOR]

Scrum is a widely-used framework in industry, so many schools apply it to their software engineering courses, particularly capstone courses. Due to the differences between students and industrial professionals, changing Scrum is necessary to fit capstone projects. In this paper, we suggest a decision-making process to assist instructors in developing a strategy to adapt Scrum for their course. This framework considers critical differences, such as student’s workloads and course schedules, and keeps the Agile principles and Scrum events. To evaluate the adapted Scrum, we investigated student’s learning experiences, satisfaction, and performance by quantitatively analyzing user story points and source codes and qualitatively studying instructor’s evaluations, student’s feedback, and Sprint Retrospective notes. Our two case studies about adapted Scrum showed that having daily stand-up meetings in every class was not helpful, student’s satisfaction positively correlated to the difficulty of the task they tackled, and the project provided good learning experiences.

Mentoring and coaching have many forms and formats. Choosing the right one is often challenging because of cost, delays on program launch, concerns with adoption, participation and capacity, overall readiness of mentors, prioritization and how it fits the company's objectives and culture. As part of talent development, organizational solutions, productivity and automations teams, which aim to develop mentor-mentee (coach-coached) matching engine and overall business process automation of a mentorship program, we had to identify the key deliverables, main features, evaluate existing solutions and then design, develop and operate the system. In this paper we present the in-house development process of a mentoring program software solution, its architecture and operations in trivago from 2018 until 2020 [ABSTRACT FROM AUTHOR]

Despite the profusion of research about knowledge management within larger organizations, fewer studies tried to analyze knowledge management in small and medium enterprises. The study contributes to research by providing a more nuanced classification of knowledge management approaches and guides managers about the types of knowledge management approaches that should be adopted based on the size, geographical dispersion, and task nature of the organization. A purposive sample of 34 companies was selected for this study along with a survey that focused on the objective of investigating awareness and implementing strategies of knowledge management. The various phases and processes of knowledge management were accounted for. Organizations were bifurcated on the criteria like the core area of the company, the size of the company, the type of company, etc. Knowledge management implementation was judged through each dimension. Different statistical tests were carried out to test a set hypothesis. Having established that wide variation in overall adoption of knowledge management practices exists across the software engineering organizations, the different characteristics associated with knowledge management adoption were tested: organization size in terms of employee strength, the domain of the software engineering, team distribution, and type of organization. To a surprise, most of the organizational characteristics are not found in the significantly associated with knowledge management adoption except knowledge management adoption level in full and partial agile organizations and the relationship between the organization KM level and the number of software developers in organization for only product development companies is found significant. Opposite to the claims of many researchers, this study does not find any significant difference between knowledge management adoptions between distributed and co-located agile teams. [ABSTRACT FROM AUTHOR]

With years of frantic development, when release fast and release often was the mandatory rule for web technologies and services, the open source paradigm and online distribution repositories have imposed de facto standards for quality assessment in fast‐paced innovation processes. Nowadays, however, in pursuit of productivity, security, and user satisfaction, the industry is beginning, through the introduction of new standards such as ECMAScript 6 or web components, to consider software engineering mandates for web technologies. This article reports a quality model aligned with international standard ISO/IEC 25010, covering web components technology, which ultimately aims to improve adoption by the software engineering industry, traditionally wary of agile Internet practices, the open source paradigm, and public repositories. Our research also presents an experimentation platform on which end users have validated the quality properties, highlighting the implicit connection with the perceived quality. The key result of our research convinces us that user ratings are suitable as a testing mechanism for product quality and quality‐in‐use metrics in order to define an absolute scale of comparison for web component quality. [ABSTRACT FROM AUTHOR]

Different software development approaches (SDAs) are developed with broad portfolios of development processes. Each of the approaches has certain exclusive principles, practices, thinking, and values, which are informally represented, implemented, and improperly institutionalized. Ontologies are developed for the representation, assessment, and adaptation of SDAs separately without having a shared terminology which may lead to terminological conflict and confusion affecting the simultaneous representation and implementation in software development industry and academia. The software engineering approaches does not consider and support sustainability as priority concern. However, the approaches have capabilities of supporting sustainable software development in different sustainability aspects. This research article aims for the designing and development of an integrated ontology of software engineering approaches (i.e., agile, lean, and green) named OntoSuSD (ontology for sustainable software development) to support sustainable software development knowledge, awareness, and implementation. The goal of OntoSuSD is to propose, design and develop a formal, generic, consistent, and shared knowledge base containing semantic terminology and description of concepts and relationships generated around the representation and implementation of lean, agile, and green approaches in software development processes, which will facilitate their simultaneous implementation and assessment for sustainable software development. The OntoSuSD is developed using practical ontology engineering methodology by reusing relevant ontologies and explicit concepts and properties are defined to fulfill knowledge requirements and representations of the domain. The OntoSuSD is evaluated, and results infer OntoSuSD has high ontological design, good domain coverage, potential applications and achieves purpose of the ontology development. [ABSTRACT FROM AUTHOR]

Throughout the evolution of software systems, empirical methodologies have been used in their development process, even in the Internet of Things (IoT) paradigm, to develop IoT-based systems (IoTS). In this paper, we review the fundamentals included in the manifesto for agile software development, especially in the Scrum methodology, to determine its use and role in IoTS development. Initially, 4303 documents were retrieved, a number that was reduced to 186 after applying automatic filters and by the relevance of their titles. After analysing their contents, only 60 documents were considered. Of these, 38 documents present the development of an IoTS using some methodology, 8 present methodologies focused on the construction of IoTS software, and 14 present methodologies close to the systems life cycle (SLC). Finally, only one methodology can be considered SLC-compliant. Out of 38 papers presenting the development of some IoTS following a methodology for traditional information systems (ISs), 42.1% have used Scrum as the only methodology, while 10.5% have used Scrum combined with other methodologies, such as eXtreme Programming (XP), Kanban and Rapid Prototyping. In the analysis presented herein, the existing methodologies for developing IoTSs have been grouped according to the different approaches on which they are based, such as agile, modelling, and service oriented. This study also analyses whether the different proposals consider the standard stages of the development process or not: planning and requirements gathering, solution analysis, solution design, solution coding and unit testing (construction), integration and testing (implementation), and operation and maintenance. In addition, we include a review of the automated frameworks, platforms, and tools used in the methodologies analysed to improve the development of IoTSs and the design of their underlying architectures. To conclude, the main contribution of this work is a review for IoTS researchers and developers regarding existing methodologies, frameworks, platforms, tools, and guidelines for the development of IoTSs, with a deep analysis framed within international standards dictated for this purpose. [ABSTRACT FROM AUTHOR]

We present a solution based on blockchain technology and smart contracts for agile project management in light of the continuing transition in the software development industry. Due to the fact that these technologies are self-executing, customized, and impervious to tampering, they are considered to be crucial for the transition to a more efficient, transparent, and transactive payment gateway between major stakeholders. These major stakeholders will be able to communicate through smart contracts, which will act as a bridge between them. As part of their responsibility, they will make sure that all of the terms of the contract are met and acknowledged by all members of the team. As a result of our research, we propose a model in which payouts could be automatically enabled and penalties or grants could be introduced based on performance. If any changes were to be made to the contract in the future, all parties involved would be automatically notified. To maintain the development cycle, they should accept these changes as soon as possible. Because of this, the product owner and client are able to concentrate their resources on more profitable and productive tasks, without the need to monitor this aspect of agile project management. Our proposed model brings together different partners with the objective of successfully developing different IT projects by leveraging software engineering solutions such as smart contracts. [ABSTRACT FROM AUTHOR]

The Internet of Things (IoT) systems are inherently distributed with many concurrent behaviors. In order to apply behavior-driven development (BDD), a proven agile practice of software development that brings many benefits, we must ensure that the specification of sequential and concurrent behaviors is supported at the specification level and that tool support is in place to execute the specification. This study proposes a minimal semantic enhancement to the Gherkin language, the most popular specification language in BDD, to distinguish sequential and concurrent behaviors. At the same time, a tool called concurrentSpec is developed to support the correct execution of specifications written in the enhanced Gherkin language. With two IoT examples involving both sequential and concurrent behaviors, it is shown that the enhanced Gherkin with concurrentSpec can correctly specify and execute the specifications, while the original Gherkin with existing tools is unable to do so. Hence, the contribution of this study is to eliminate a technical impediment for the IoT development community to adopt BDD and receive its benefits. [ABSTRACT FROM AUTHOR]

The nine papers in this special section focus on new developments in agile software and reports on applications for its use. A key aspect for the extensive use of agile software is that it supports developers with coping with the growing uncertainty and turbulence in technological and market environments. Feedback and change are at the core of Agile for a dynamic, evolving, and organic, rather than static, predefined, and mechanistic development process advocated by waterfall management. To create timely, high-quality, cost-efficient, and innovative solutions, Agile developers organized in small, colocated, autonomous teams, build and test software in rapid iterative cycles, actively involving users to gather feedback, updating the project scope, and plan "on-the-fly," using face-to-face communication as opposed to documentation. These papers contribute to the state-of-the-art of agile research by offering a rich, up-todate account of the dynamics occurring when expanding Agile into "not-just-software" contexts of the key challenges and perils related to the scaling and of the possible solutions to them. [ABSTRACT FROM AUTHOR]

The competition in the software market demands that the time required for any software product to reach the market be reduced if the product is to survive competition from other developers. The pursuit of this goal has led to the adoption of agile software development methodologies. While other agile methodologies provide guidelines as to the software engineering (SE) practices to be used during the development lifecycle, Scrum does not. The purpose of this study is twofold: first, to identify the usage and level of importance of software engineering practices in the Scrum development environment; and second, to investigate how Scrum teams adopt an appropriate set of SE techniques and whether a hybrid Scrum/Extreme Programming (XP) methodology is an appropriate approach to take. This research was conducted by examining sample data from five organizations using the Scrum methodology. The sample included a range of industries including communications and embedded systems, financial asset management, software development houses and consulting firms in South Africa. The study employed a mixed method approach. A key finding was that, regardless of the fact that Scrum does not explicitly recommend engineering practices, there was extensive use of these practices by all of the participating organizations. The study also found that the lack of software engineering practices in Scrum does not constitute a barrier to a successful adoption of Scrum, provided the 'inspect and adapt' principle inherent in Scrum is properly followed. The study discusses the findings, explains the implications and suggests future research. [ABSTRACT FROM AUTHOR]

Copyright of Revista Facultad de Ingeniería - UPTC is the property of Universidad Pedagogica y Tecnologica de Colombia, Facultad de Ingenieria and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)