Search

Industry 4.0 (I4.0) systems are often designed without sufficiently considering the needs of stakeholders and the organizational processes to be supported, leading to solutions that are socially and organizationally unsustainable. In this study, the notions of social and organizational sustainability were viewed from a micro-level perspective, referring to the ability of technology to sustain the concerns of people and work organization within the socio-technical system, as opposed to a macro-level perspective related to concerns outside the system. Through a literature review, this study shows that social and organizational sustainability is covered by principles originally proposed in agile software engineering. A set of core requirements for model-based design approaches were then derived from the agile principles, based on insights from design research and model theory. The requirements include (1) the coverage of function and behavior, (2) simplicity, (3) executability and (4) modularity. They were then used to evaluate an existing modeling approach—subject-oriented process modeling (S-BPM)—to demonstrate their applicability and usefulness. [ABSTRACT FROM AUTHOR]

Although a large body of literature exists to support the execution of Information and Communication Technologies for Development (ICT4D) initiatives, many such initiatives fail to deliver the intended results. By following a Design Science Research (DSR) methodology, this article presents an artifact (a framework) whose purpose is to integrate activities/processes noted in the literature to support the successful development of ICT4D initiatives. The result of the study is an evaluated process framework which serves as a tool to guide developers in identifying activities/processes that can support the success of ICT4D initiatives. [ABSTRACT FROM AUTHOR]

The traditional combat system-of-systems (SoS) has a long development process of capability requirements, a weak rapid response capabilities to the dynamic changes in the battlefield situation, single source of requirements and lack of feedback adjustment mechanism. In view of the above problems, the agile development method of combat SoS capability requirements based on system engineering "V" model and user stories is proposed. The development framework of combat SoS capability requirements is redesigned. The combat SoS capability requirements model is built based on the user stories. And a complete set of combat SoS capability requirements development process is proposed. Finally, the development process of combat SoS capability requirements is demonstrated with the example of "minefield cleaning" combat task. The example research results indicate that the proposed method provides a new technical path for solving the bidirectional source contradiction problem of combat SoS capability requirements, and can effectively improve the efficiency of developing combat SoS capability requirements. [ABSTRACT FROM AUTHOR]

Copyright of Revista Foco (Interdisciplinary Studies Journal) is the property of Revista Foco 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.)

In software projects that use the Agile methodology, the focus is on development in small iterations to allow both frequent changes and client involvement. This methodology affects the risks that may happen in Agile software projects. Hence, these projects need a clear risk management process to reduce risks and address the problems before they arise. Most software production methodologies must use a framework for risk management, but currently, there is no such framework for the Agile methodology. Therefore, we present a risk management framework for projects that use the Agile methodology to help the software development process and increase the likelihood of the project's success. The proposed framework states the necessary measures for risk management according to the ISO31000 standard at each stage of the Agile methodology. We evaluated the proposed framework in two running software projects with an Agile methodology by a number of expert experts. The results show that using our proposed framework increases the average positive risk reaction score by 49%. [ABSTRACT FROM AUTHOR]

Historical education is essential in forming human character because it is the basis for forming a sense of nationalism. Along with the development of technology, learning models are also affected. Learning can be facilitated through learning sources other than educators, thereby changing the role of educators in learning and adapting learning to current developments. One of the learning resources is game technology. Game applications can be a learning medium because of their visual and interactive nature. Packing history learning into an educational game application might be an alternative source of learning that is interesting and not monotonous. The purpose of this research is developing education media as an Android-based historical learning tool by packaging the historical learning of the story of Sunan Kalijaga in the form of a game application. The results of the black box, white box trials that went well, and the feasibility test that was carried out on 15 respondents, 93% stated that the material presented was appropriate so that it can be concluded that the game application is suitable for use as an alternative media for mobile learning by teachers and students with an assessment feature using an Android smartphone. Abstrak Pendidikan sejarah sangat penting dalam proses pembentukan karakter manusia karena merupakan dasar dari pembentukkan rasa nasionalisme. Seiring dengan berkembangnya teknologi, Pembelajaran pun ikut terpengaruhi. Pembelajaran dapat dipermudah melalui sumber pembelajaran selain pendidik, sehingga menggubah peran pendidik dalam pembelajaran dan menyesuaikan pembelajaran dengan perkembangan zaman saat ini. Salah satu sumber pembelajaran itu adalah teknologi game. Aplikasi game dapat menjadi media pembelajaran karena sifatnya yang visual dan interaktif. Mengemas pembelajaran sejarah kedalam sebuah aplikasi game edukasi mungkin bisa menjadi salah satu alternatif sumber pembelajaran yang menarik dan tidak monoton. Tujuan dari penelitian ini adalah membuat aplikasi game “Lokajaya Sang Kalijaga” sebagai sarana pembelajaran sejarah berbasis Andoid dengan mengemas pembelajaran sejarah kisah Sunan Kalijaga ke dalam bentuk aplikasi game. Hasil dari uji coba black box, white box yang berjalan baik serta uji kelayakan yang telah dilakukan pada 15 responden, 93% menyatakan materi yang dibawakan telah sesuai sehingga dapat disimpulkan aplikasi game layak dipergunakan sebagai media alternatif pembelajaran secara mobile oleh guru dan murid dengan fitur penilaian menggunakan smartphone Android.

Featured Application: In the field of medicine, daily high-stake decision-making scenarios arise. To enhance these decision-making processes, the utilization of modern machine learning techniques and their infusion with expert knowledge in a seamless manner while adhering to agile principles enables swift action and facilitates an understanding of the obtained knowledge, fostering trust in the decision-making process. Over the past few decades, machine learning has emerged as a valuable tool in the field of medicine, driven by the accumulation of vast amounts of medical data and the imperative to harness this data for the betterment of humanity. However, many of the prevailing machine learning algorithms in use today are characterized as black-box models, lacking transparency in their decision-making processes and are often devoid of clear visualization capabilities. The transparency of these machine learning models impedes medical experts from effectively leveraging them due to the high-stakes nature of their decisions. Consequently, the need for explainable artificial intelligence (XAI) that aims to address the demand for transparency in the decision-making mechanisms of black-box algorithms has arisen. Alternatively, employing white-box algorithms can empower medical experts by allowing them to contribute their knowledge to the decision-making process and obtain a clear and transparent output. This approach offers an opportunity to personalize machine learning models through an agile process. A novel white-box machine learning algorithm known as Data canyons was employed as a transparent and robust foundation for the proposed solution. By providing medical experts with a web framework where their expertise is transferred to a machine learning model and enabling the utilization of this process in an agile manner, a symbiotic relationship is fostered between the domains of medical expertise and machine learning. The flexibility to manipulate the output machine learning model and visually validate it, even without expertise in machine learning, establishes a crucial link between these two expert domains. [ABSTRACT FROM AUTHOR]

A growing number of articles describe the challenges of adopting DevOps for DoD software development. A recent paper in this journal discussed DevOps adoption challenges within the acquisition programs of the Navy. For embedded software, these challenges have been overwhelming to date. However, for standalone applications, the story is different, even though the lingering impact of DoD Instruction 5000 and other DoD cultural practices remains problematic. The HPCMP CREATE™ program, or simply CREATE in this paper, is part of the portfolio of the DoD High Performance Computing Modernization Program (HPCMP). It has successfully adapted DevOps concepts and agile software development practices to develop a family of software applications that enable system-scale virtual prototyping and testing analysis for major DoD acquisition programs. This study describes the main enabling practices that made this possible. [ABSTRACT FROM AUTHOR]

Agile hardware development methodology has been widely adopted over the past decade. Despite the research progress, the industry still doubts its applicability, especially for the functional verification of complicated processor chips. Functional verification commonly employs a simulation-based method of co-simulating the design under test with a reference model and checking the consistency of their outcomes given the same input stimuli. We observe limited collaboration and information exchange through the design and verification processes, dramatically leading to inefficiencies when applying the conventional functional verification workflow to agile development. In this paper, we propose workflow integration with collaborative task delegation and dynamic information exchange as the design principles to effectively address the challenges on functional verification under the agile development model. Based on workflow integration, we enhance the functional verification workflows with a series of novel methodologies and toolchains. The diff-rule based agile verification methodology (DRAV) reduces the overhead of building reference models with runtime execution information from designs under test. We present the RISC-V implementation for DRAV, DiffTest, which adopts information probes to extract internal design behaviors for co-simulation and debugging. It further integrates two plugins, namely XFUZZ for effective test generation guided by design coverage metrics and LightSSS for efficient fault analysis triggered by co-simulation mismatches. We present the integrated workflows for agile hardware development and demonstrate their effectiveness in designing and verifying RISC-V processors with 33 functional bugs found in NutShell. We also illustrate the efficiency of the proposed toolchains with a case study on a functional bug in the L2 cache of XiangShan. [ABSTRACT FROM AUTHOR]

This article searches for correlations between the practices of usability professionals from software development teams and the resulting usability of the system they are working on. After reviewing the literature of the past decade, we can conclude that most researchers try to achieve better usability with process proposals, but measurements focus on perceived usability. The level of involvement of users in the requirements capture phase is unclear. There is a trend to reduce costs of usability engineering, either by choosing more lightweight and informal methods or by trying to substitute user involvement. Looking at decade's worth of 452 articles about "agile AND usability" in Scopus, we selected 133 which deal with the integration of usability, UX and User Centred Design practices and Agile development. [ABSTRACT FROM AUTHOR]

Business process management (BPM) has been the main driver behind company optimization and operational efficiency. However, the digitization era we live in necessitates that organizations be agile and adaptable. Delivering unprecedented rates of automation-fueled agility is necessary to be a part of this digital revolution. On the other hand, BPM automation cannot be done only by concentrating on procedure space and traditional planning methodologies. With the introduction of BPM, where the deployment of BPM with cloud computing has undergone enormous development lately, cloud computing has been considered a particularly active topic of study. Cloud computing points to the provision of dependable computing environments based on improved infrastructure availability and service quality without imposing a significant cost load. This research aims to discover the relationship between technical factors, financial factors, environmental factors, security of the cloud-based information systems, and the agile development of industrial BPM (IBPM). The present study aims to fill this gap and show how partial least squares structural equation modeling (SEM) can be employed in this field. Importance–performance map analysis (IPMA) evaluated the importance and performance of factors in the SEM. IPMA enables the identification of factors with relatively low performance but relatively high importance in shaping dependent variables. The empirical findings showed that four key factors (technical, financial, environmental, and security) positively influence the agile development of IBPM. [ABSTRACT FROM AUTHOR]

Educational games are increasingly used to teach Agile development approaches to practitioners. Most of these training modules simplify the development environment, for example, by using LEGO bricks or playing cards. This oversimplification has been shown to result in limited transferability of learning to industrial practice. Furthermore, there is a lack of teaching modules that specifically address the challenges of applying Agile to physical products. In this paper, we present an open‐source educational game that realistically simulates a hardware development project to teach Agile principles. Over 2 days, participants design, manufacture, and test modifications for a physical wire bending machine within an authentic engineering and production setting. The training mimics the typical roles, processes, and tools of industrial engineering teams to reflect the challenges of Agile hardware development. The module was evaluated with 44 industry professionals regarding perceived learning and user reaction. A combination of quantitative and qualitative methods was used for the experimental evaluation. The results showed a positive learning effect as the participants' average agreement with Agile principles increased through the training. Concerning user reaction, respondents reported a high degree of relevance, interaction, and confidence, indicating that the realistic simulation of the hardware development appropriately balanced the degree of realism with simplicity. The study showcases the opportunities of properly aligning game components to provoke learning situations targeted by the instructors. It contributes to the extant literature by providing a design framework (product, process, setting, and instruction) and open‐source access to the tools used for implementation. [ABSTRACT FROM AUTHOR]

The main question proposed in this research is whether different types of organizational approaches could help in shortening the response time needed to analyze advanced design solutions in accordance with the changed circumstances. Approaches that we are considering have been adapted from rapidly changing disciplines—such as the IT industry, and software engineering. This paradigm allows for architectural programming to obtain different positions in the timeline of project planning and realization. We proposed a novel methodology of architectural design and project management as an instrument inspired by the Agile Manifesto and some of its instantiations, most notably by the Scrum framework. This research shows that application of the proposed framework significantly shortens the design process and facilitates the involvement of a larger number of authors within the same project team. This study focused on the specific case of architectural competitions. However, the results showed that the same framework could be applied in a broader design context, details of which have been left for future considerations. [ABSTRACT FROM AUTHOR]

As various estimation methods are available to predict the completion time of requirements at earlier phase of software development. Function point analysis used to estimate the efforts required to develop the traditional project on time. Now industries are moving to the agile technology to develop the project with involvement of customer. team member and tester as well. To advancement in the agile development the requirements are framed in the form of user stories. In today IT industries. essential view of agile is estimation methods are required to measure the user stories. Need of estimation method of agile through the implement of function point analysis for prediction. To improve the organization success. project completion needs to done on time. There is requirement of approach to find out the actual effort estimation of user story. In this paper. assignment of function point to user story is done and find out the effort estimation required to implement the user stories on the basis of different complexity weights. Initially. extract the "I want" section and obtain the number of transaction types (external inputs. external outputs and external inquires) on the basis of operational keywords appearance This proposed work computed UFR TDL VAR adjusted FP and efforts in hours on the basis of weights such as low, average. and high of IFPUG and the average by release 5 of ISBSG. The average complexity weight of the IFPUG and the average of release 5 of the 1SBSG are the key parameters for the comparison perspective. The outcome of the proposed work provides the adjusted FP and effort estimation in hours. In order to predict effort required. the interpolated values of effort estimation is calculated using Lagrange's interpolation. Both outcomes give the usage of FPA through IFPUG and ISBSG to estimate the effort so that the completion of project on time. Function point analysis on agile user story is used to improve the organization success. [ABSTRACT FROM AUTHOR]

Copyright of Aero Weaponry is the property of Aero Weaponry Editorial Office 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 development processes based on user stories often face issues such as incomplete, inconsistent, and inaccurate user requirements, which increase the workload of agile development teams and reduce the efficiency of product function development, ultimately resulting in the inability to respond quickly to user requirements. This paper proposes a user requirement quality assessment method based on user stories to address these problems. This method relies on the agile development process, constructs a user requirement quality assessment framework, defines a user story model and a user requirement quality model, develops seven user requirement quality assessment criteria, and designs a user requirement quality assessment process. A data experiment exploring the development of smartphone requirements is used to validate the feasibility and effectiveness of the method. The experimental results demonstrate that the method improves user requirement quality to some extent, providing an automated solution for agile development teams to enhance user requirement quality. [ABSTRACT FROM AUTHOR]

The success of agile development methods in software development has raised interest in System-on-Chip (SoC) design, which involves high architectural and development process complexity under time and project management pressure. This article discovers the current state of agile hardware development with the questions (1) how well literature covers the SoC development process, (2) what agile methods and practices are applied or (3) what proposals are made to increase the agility, and (4) what is the impact for the SoC community. To answer the questions, a mapping study and literature review were performed. Seven hundred thirty papers were first studied, and eventually, after a rigorous filtering process, 25 papers were thoroughly analyzed. The results show that the popular agile SW development methods are applied in 5 cases, ideas adapted from the agile Hardware manifesto in 9 cases, and 11 cases do not define the Agile HW development method. Most of the papers address shorter development time by better methodologies and tools that indirectly shape the SoC development toward agility. The focus of agile hardware development is mostly on the SoC artifacts and methodological improvements have not been quantified. However, the literature indicates a significant impact on many academic chip prototypes. The challenges are better understood and the interest in agile methods is clearly increasing. The methodological gaps in the prevalent situation encourage further research and more accurate reporting of the development in addition to the SoC artifacts. [ABSTRACT FROM AUTHOR]

Background: Several methodologies have been proposed since the first days of software development, from what is now named traditional/heavy methodologies, and later their counterpart, the agile methodologies. The whole idea behind agile methodologies is to produce software at a faster pace than what was considered with plan-based methodologies, which had a greater focus on documenting all tasks and activities before starting the proper software development. Problem: One issue here is that strict agilists are often against fully documenting the software architecture in the first phases of a software process development. However, architectural documentation cannot be neglected, given the well-known importance of software architecture to the success of a software project. Proposed Solution: In this article, we describe the past and current situation of agile methodologies and their relation to architecture description, as well as guidelines for future Agile Methodologies and Architecture Reconciliation. Method: We propose a literature review to understand how agile methodologies and architecture reconciliation can help in providing trends towards the success of a software project and supporting software development at a faster pace. This work was grounded in General Systems Theory as we describe the past, present, and future trends for rapid systems development through the integration of organizations, stakeholders, processes, and systems for software development. Summary of results: As extensively discussed in the literature, we found that there is a false dichotomy between agility and software architecture, and then we describe guidelines for future trends in agile methodologies and reconciliation of architecture to document agile architectures with both architectural decisions and agile processes for any system, as well as future trends to support organizations, stakeholders, processes, and systems. [ABSTRACT FROM AUTHOR]

Different activities, artifacts, and roles can be found in the literature on the agile engineering of secure software (AESS). The purpose of this paper is to consolidate them and thus identify key activities, artifacts, and roles that can be employed in AESS. To gain initial sets of activities, artifacts, and roles, the literature was first extensively reviewed. Activities, artifacts, and roles were then cross-evaluated with similarity matrices. Finally, similarity matrices were converted into distance matrices, enabling the use of Ward's hierarchical clustering method for consolidating activities, artifacts, and roles into clusters. Clusters of activities, artifacts, and roles were then named as key activities, artifacts, and roles. We identified seven key activities (i.e., security auditing, security analysis and testing, security training, security prioritization and monitoring, risk management, security planning and threat modeling; and security requirements engineering), five key artifacts (i.e., security requirement artifacts, security repositories, security reports, security tags, and security policies), and four key roles (i.e., security guru, security developer, penetration tester, and security team) in AESS. The identified key activities, artifacts, and roles can be used by software development teams to improve their software engineering processes in terms of software security. [ABSTRACT FROM AUTHOR]

In the armed forces, successful digitalization is crucial to ensure effective operations. Much of the existing literature on project factors during the planning and execution phases of public IT projects do not focus specifically on military sector projects. Therefore, the paper aims to provide empirical insights into the characteristics of successful military IT projects. Data from such projects in NATO countries and agencies were collected through interviews and project documents. The findings relating to the main variable of interest, "delivery of client benefit," supported previous findings on IT project performance. Medium-sized projects performed better than small and large projects, and the agile development method delivered more client benefit than traditional methods. Client involvement apparently had a positive effect on project success. Clearly specified objectives had a statistically significant effect on project success in terms of clients' benefits. The paper contributes to the gap in research on military IT projects and broadens the project management literature's focus on time and cost to include delivery of client benefit as a success variable. The use of cross-country data provided unique insights for academics and practitioners regarding which project characteristics affect the successful development and adoption of new software by the armed forces. [ABSTRACT FROM AUTHOR]

The Lean Startup approach allows innovators (including innovative educators) to rapidly identify and refine promising ideas into models that actually work. Our aim is to outline key principles of Lean Startup, apply these to health professions education, and illustrate these using personal experience. All innovations are grounded in numerous assumptions; these assumptions should be explicitly identified, prioritized, and empirically tested ('validated learning'). To identify and test assumptions, innovators need to get out of the office and interact with customers (learners, teachers, administrators, etc). Assumptions are tested using multiple quick cycles of Build (a 'minimal viable product' [MVP]), Measure (using metrics that relate meaningfully to the assumption), and Learn (interpret data and decide to persevere with further refinements, or pivot to a new direction). The MVP is a product version that allows testing of one or more key assumptions with the least effort. We describe a novel 'Lean Education Canvas' that synopsizes an innovation and its business model on one page, to help identify assumptions and monitor progress. We illustrate these principles using three cases from health professions education. Lean Startup has tremendous potential for rapid, robust innovation and evaluation in education. Practice points The Lean Startup approach allows innovators (including innovative educators) to rapidly identify and refine promising ideas into models that actually work. All innovations are grounded in numerous assumptions; these assumptions should be explicitly identified, prioritized, and empirically tested ('validated learning'). To identify and test assumptions, innovators need to get out of the office and interact with customers (learners, teachers, administrators). Assumptions are tested using multiple fast, iterative cycles of Build (a minimal viable product), Measure (using metrics that relate meaningfully to the assumption), and Learn (interpret data and decide to persevere with further refinements, or pivot to a new direction). The 'minimal viable product' (MVP) is a version of the product that allows innovators to test one or more key assumptions with the least effort. [ABSTRACT FROM AUTHOR]

Agile project management (APM) can be defined as an iterative approach that promotes satisfying customer requirements, adjusts to change, and develops a working product in rapidly changing environments. Managers usually apply agile management as the project management approach in projects requiring extraordinary speed and flexibility in their processes. Earned value management (EVM) is a fundamental part of project management to establish practical measures. Often, managers use a task board to visually represent the work on a project and the path to completion. Still, managing an agile project can be a challenging endeavor. In this paper, we propose an agent-based model describing the management of tasks within a project using earned value assessment and a task board. Our model illustrates how EVM yields an efficient method to measure a project's performance by comparing actual progress against planned activities, thus facilitating the formulation of more accurate predicted estimations. As proof of concept, we leverage our implementation to calculate EVM performance indexes according to a performance measurement baseline (PMB) in a task board fashion. [ABSTRACT FROM AUTHOR]

Copyright of Computer Measurement & Control is the property of Magazine Agency of Computer Measurement & Control 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.)

In the armed forces, successful digitalization is crucial to ensure effective operations. Much of the existing literature on project factors during the planning and execution phases of public IT projects do not focus specifically on military sector projects. Therefore, the paper aims to provide empirical insights into the characteristics of successful military IT projects. Data from such projects in NATO countries and agencies were collected through interviews and project documents. The findings relating to the main variable of interest, “delivery of client benefit,” supported previous findings on IT project performance. Medium-sized projects performed better than small and large projects, and the agile development method delivered more client benefit than traditional methods. Client involvement apparently had a positive effect on project success. Clearly specified objectives had a statistically significant effect on project success in terms of clients’ benefits. The paper contributes to the gap in research on military IT projects and broadens the project management literature’s focus on time and cost to include delivery of client benefit as a success variable. The use of cross-country data provided unique insights for academics and practitioners regarding which project characteristics affect the successful development and adoption of new software by the armed forces.

This paper discusses the “Get Real Get Better” (GRGB) approach to implementing agile program management in the U.S. Navy, supported by advanced data analytics and artificial intelligence (AI). GRGB was designed as a set of foundational principles to advance Navy culture and support its core values. This article identifies a need for a more informed and efficient approach to program management by highlighting the benefits of implementing comprehensive data analytics that leverage recent advances in cloud computing and machine learning. The Jupiter enclave within Advana implemented by the U.S. Navy, is also discussed. The presented approach represents a practical framework that cultivates a “Get Real Get Better” mindset for implementing agile program management in the U.S. Navy.

The market for electric bicycles has grown extremely and developed rapidly in recent years. To enter such a market with a new product, the development process has to be fast, and throughout the process, feedback from future potential customer(s) should be sought in order to achieve the best possible market acceptance. The article presents the design process of a pedelec e-bike central drive system. The authors were members of the development team and the designers of the mechanical transmission, and therefore had a good overview of the whole project. The development process and the set-up of production require a certain amount of time, during which design changes are inevitable due to changes in customer expectations and demands. The development team should respond to these changes and take them into account during development. Only the ability to react to changes and constant communication with the customer will ultimately lead to a product that can be commercially successful. Based on a critical review of the successfully completed project, general guidelines were established for the development of mechatronic products that consider the principles of Agile methodology. Particular attention was paid to the development of polymer gears, as these were the most demanding components in the system. The presented guidelines were based on an overview of the e-bike R&D process presented, but they can be generalized and used in the development process of any technical physical product. Agile methods were developed in the field of software development and therefore cannot be directly transferred to the field of physical product development. The article highlights and discusses individual special features that distinguish agile development of physical products from software development. [ABSTRACT FROM AUTHOR]

Copyright of Revista de Ciências da Computação is the property of Universidade Aberta 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.)

Purpose: The objective of the study is to analyze the impact of the adoption of the Agile Mindset on the productivity of Agile software development teams in IT enterprises during COVID-19. Design/methodology/approach: A web-based survey is performed with voluntary participants working with the Agile software development professionals with a specific focus on IT enterprises around Pune, India. For this the initial exploratory literature review was performed, to explore the team's behaviors and their response to the crises like the Covid-19 pandemic. Data is collected from the targeted population using the random sampling method. A questionnaire is designed with the help of a five-point Likert scale. All the respondents were analyzed based on their behaviors shown and how adopting to Agile mindset has impacted their productivity during the pandemic. Collected data would be then analyzed using the Smart PLS-SEM methodology. Findings: Findings of the study show that Agile software development teams adopting to Agile mindset are better at responding to crisis and quick to adapt to change as teams adopting the Agile mindset is likely to sustain or even improve their productivity during the crises like Covid-19 pandemic. Adapting to an Agile mindset is important for Agile software development teams during a crisis as a response to changes in the working as well as environmental conditions. This study also shows that by adopting an Agile mindset, development teams are better at responding to the crisis eventually improving productivity. Research limitations/implications: Research limitations for this study-scope of the study could be extended to the larger population across geographies to have improved insights Productivity Factors like- Efforts Efficiency, Backlog-management Index (BMI), and Weighted Average Productivity (VWP) for team members can be included. More behavioral factors for Agile Mindset can be considered. Practical implications: Agile software development teams are characterized by collaboration and responsibility. Recent enforcement of pandemic precautionary measures has enforced Agile software development teams to work remotely and maintain social distancing while in the office. It was challenging for most of the working people to adjust to the new working conditions (Yang et al., 2021) However, in IT organizations, adopting the Agile mindset has ensured continuous software deliveries, took ownership, and quickly adapted to the volatile situations, ultimately resulting into the growth in the productivity unlike to that of other sectors of the economy. Social implications: In this study, we have analyzed the hypotheses with statistical significance in association with constructs that are in sync with the available literature. Adopting the Agile mindset values has positively impacted the team's behavior resulting in productivity improvement even in the distributed working locations in pandemic situations. Originality/value: The study highlights that adopting to Agile mindset has positively impacted an Agile software development team's productivity during the Covid-19 pandemic. As environmental conditions during Covid-19 were uncertain and ambiguous and teams were working in distributed and disconnected ways, many researchers have believed that it would have affected the overall productivity. This was turned true for most of the sectors of the economy, however, Agile software development teams have shown positive trends in their productivity, as they have adopted the Agile mindset values and principles, during crises. [ABSTRACT FROM AUTHOR]

How can we make software services evolve safely and be long-lived? By designing on the premise of microservices, the services become loosely coupled, which can localise the changes in the system and accelerate the changes. However, from a medium- to long-term perspective, it is not easy to respond to changes in technology trends, business changes including legal revisions, and changes in user requirements among the changing project members. We propose DevFemOps as a way to enhance maintainability and achieve continuous quality improvement, coining the term DevFemOps to place Formal Engineering Methods at the center of the DevOps cycle. We also define the DevFemOps QA engineer as a new role within the agile development squad that is responsible for the quality of the product. In this paper, we will describe how the DevOps cycle, with QA engineers at the center, can bring us closer to the goal of DevFemOps. [ABSTRACT FROM AUTHOR]