Search results

This aims to explore the relationship between the agile methods barriers in large-scale contexts and the benefits for business, team and product and process, exploring the organizational readiness (OR) mediating role.

We propose a theoretical model through survey-based research, applying partial least square structural equation modelling.

We confirmed that OR mediating effect on the relationship between agile methods barriers and team benefits. We operationalized OR in a broader context that embeds the strategic alignment of large-scale agile implementation, considering variables such as organizational structure and culture.

The data are cross-sectional rather than longitudinal, which limits temporal interpretations of the associations between agile methods and organizational issues.

The findings offer a way forward for organizations already using or planning to implement agile management to understand the pathway towards achieving the expected benefits. Our study also unveils the importance of looking at OR when implementing such a complex change in management from traditional to large-scale contexts.

Our results show the significant and positive influence of agile method on all three benefit variables (team, business, product and processes). Furthermore, we identified the significant and positive mediating role of OR on the relationship between agile method and team benefits.

As the novel coronavirus 2019 (COVID-19) impacts the world, software practitioners are collaboratively working remotely from home. The pandemic has disrupted software practitioners’ productivity forcing changes to agile methodology adopted by software practitioners in software organizations. Therefore, this study aims to provide implication on the issues and recommendations for improving software practitioners’ productivity and also examine the impact of the COVID-19 pandemic on agile software development.

This paper adopts a narrative literature review to provide early assessment based on secondary data from the literature and available document reports from studies published from 2019 to 2022 to explore software practitioners’ productivity and agile software development during the working from home directive amidst the COVID-19 pandemic. A total of 60 sources which met the inclusion criteria were used to provide preliminary evidence grounded on secondary data from the literature. Descriptive analysis was used to provide qualitative findings from the literature.

Findings from this study present the significance of working from home directive on agile software development and software practitioners’ productivity. More importantly, findings from the secondary data shed light on software practitioners’ productivity adopting agile software development amidst the COVID-19 pandemic. Additionally, the findings present virtual collaborative platforms used by software practitioners, technical and social barriers of agile software development during the pandemic and recommendations for remote agile software development.

This study explores the significance of working from home directive on software practitioners’ productivity during COVID-19 pandemic and further investigates how are software practitioners’ productivity adopting agile software development practices amidst the COVID-19 pandemic. Besides, this study discusses the challenges software practitioners currently face and offers some strategies to bridge the gaps in agile software development to help software practitioners, system developers, software managers and software organizations adapt to the changes caused by the pandemic.

This chapter delves into sustainability-related competences in innovation management for further education as part of the European lifelong learning initiative. Despite extensive research in primary and secondary education, adult education often remains overlooked. Competence-based learning is a favored approach to integrating knowledge, skills, and attitudes across various domains. Through thematic analysis and deductive coding, the study examines 72 innovation management-related further education programs conducted in Baden-Württemberg, Germany, between June and December 2022. The findings unequivocally demonstrate the inclusion of sustainability competences in innovation-related further education. Notably, Strategic Competence emerges as the most prevalent, while Normative Competence appears least frequently. This research significantly advances the convergence of further education in innovation management, responsible management education, and competence-based learning, emphasizing the importance of sustainability competences in adult learning contexts. By shedding light on this underexplored domain, the study prompts further exploration and development of sustainable educational practices for lifelong learning.

Security in large-scale agile is a crucial aspect that should be carefully addressed to ensure the protection of sensitive data, systems and user privacy. This study aims to identify and characterize the security practices that can be applied in managing large-scale agile projects.

A qualitative study is carried out through 18 interviews with 6 software development companies based in Portugal. Professionals who play the roles of Product Owner, Scrum Master and Scrum Member were interviewed. A thematic analysis was applied to identify deductive and inductive security practices.

The findings identified a total of 15 security practices, of which 8 are deductive themes and 7 are inductive. Most common security practices in large-scale agile include penetration testing, sensitive data management, automated testing, threat modeling and the implementation of a DevSecOps approach.

The results of this study extend the knowledge about large-scale security practices and offer relevant practical contributions for organizations that are migrating to large-scale agile environments. By incorporating security practices at every stage of the agile development lifecycle and fostering a security-conscious culture, organizations can effectively address security challenges in large-scale agile environments.

When coping with uncertainties, three characteristics distinguish firms: agility, adaptability and alignment (triple-A). Based on significant field research, the triple-A highlights the significance of coordinating agility, adaptability and alignment. Start-ups are facing a lot of challenges in this turbulent environment. However, this sector is undergoing a major transformation. Agility, adaptability and alignment concepts have had a major influence on the supply chain, but their implementation in start-ups has been less visible. This paper aims to identify, analyze and categorize the enablers for agility, adaptability and alignment in start-ups using the total interpretive structural modeling (TISM) approach.

In addition to the scheduled interview, a closed-ended questionnaire was used to collect data. To identify how the factors interact, the TISM technique is used, and the Matriced’Impacts Croises-Multipication Applique’ and Classment method is used to rank and categorize the agility, adaptability and alignment enablers.

This study identified ten agility, adaptability and alignment factors for start-ups. It has been found that the key importance should be given to management involvement, conflict management, collaboration and information integration.

This study primarily focused on the agility, adaptability and alignment factors in start-ups.

This study will help academics and key stakeholders understand the aspects that lead to agility, adaptability and alignment in start-ups.

Agility, adaptability and alignment concepts have had a major influence on the supply chain, but their implementation in start-ups has been less visible. Therefore, this is a novel attempt in this industry’s agility, adaptability and alignment.

The purpose of this study is to investigate the factors facilitating and influencing the adoption of DevOps practices specifically tailored to mobile software development, with a focus on understanding the influence of mobile-specific requirements on DevOps integration.

The study employs a qualitative methodology, including a literature review, exploratory case research and partial quantitative assessments through DORA metrics and survey applications. This approach, guided by the Technology-Organization-Environment (TOE) framework, prioritizes in-depth insights into the adoption of DevOps practices and explores strategies for integrating DevOps in mobile software development.

The research identifies several key themes specific to Mobile DevOps adoption, including tool integration issues, testing complexities, deployment challenges and security concerns. These findings underscore the necessity for tailored DevOps solutions that can effectively address the unique demands of mobile software development. The study also proposes actionable strategies to overcome these challenges, thereby enhancing the efficiency, quality and security of mobile applications.

The insights gained from this study provide valuable guidance for practitioners in the mobile software development sector. By understanding and addressing the specific challenges of Mobile DevOps, organizations can improve their DevOps practices and achieve better outcomes in terms of project delivery speed, quality and security. For example, implementing robust testing strategies, investing in compatible tools and developing well-defined rollback procedures can significantly enhance Mobile DevOps effectiveness. Furthermore, incorporating continuous security measures and improving cross-functional collaboration can lead to more secure and efficient mobile application deployments.

This study offers valuable starting points for researching Mobile DevOps in real-world settings, based on insights from practical DevOps implementations in a single-case organization. Organizations can use this information to compare their own DevOps approaches with those of the studied organization, and can facilitate self-assessment and improvement.

This study contributes to the limited literature on Mobile DevOps adoption and proposing actionable strategies. By incorporating the TOE framework, it provides a comprehensive guide that enhances understanding and management of DevOps practices throughout the mobile application development lifecycle and offers significant value to practitioners and researchers alike.

Quality 4.0 is essential to the Industry 4.0 framework, notably in the electronics sector. It evaluates product quality in real-time using automatic process controls, quality tools and procedures. The implementation of Quality 4.0 criteria in the electronics industry is the subject of this study’s investigation and analysis. In this study, nine Customer Requirements (CRs) and 18 Design Requirements (DRs) have been defined to adopt Quality 4.0, aiming to increase yield while reducing defects. This study has developed a Quality 4.0 framework for effective implementation, incorporating the People, Process and Technology categories.

Many CRs and DRs of Quality 4.0 exhibit interdependencies. The Analytic Network Process (ANP) considers interdependencies among the criteria at various levels. Quality Function Deployment (QFD) can capture the customer’s voice, which is particularly important in Quality 4.0. Therefore, in this research, we use an integrated ANP-QFD methodology for prioritizing DRs based on the customers' needs and preferences, ultimately leading to better product and service development.

According to the research findings, the most critical consumer criteria for Quality 4.0 in the electronics sector are automatic systems, connectivity, compliance and leadership. The Intelligent Internet of Things (IIOTs) has emerged as the most significant design requirement that enables effective control in production. It is observed that robotics process automation and a workforce aligned with Quality 4.0 also play crucial roles.

Existing literature does not include studies on identifying CRs and DRs for implementing Quality 4.0 in the electronics industry. To address this gap, we propose a framework to integrate real-time quality measures into the Industry 4.0 context, thereby facilitating the implementation of Quality 4.0 in the electronics industry. This study can provide valuable insights for industry practitioners to implement Quality 4.0 effectively in their organizations.

This study investigated the interplay between business process management (BPM) and digitalization in organizations and developed principles for designing their interaction.

This study was explorative and used a questionnaire-based survey that involved experts in BPM and digitalization who were actively engaged in these two domains in their organizations to come up with the design principles. The survey and the design principles were based on Rosemann and vom Brocke's (2010) six core elements of BPM.

Digitalization was seen as influencing how BPM is practiced in organizations by strengthening organizations’ focus on BPM, and conversely, BPM was perceived as beneficial for digitalization and digitalization outcomes. In addition, based on Rosemann and vom Brocke’s six core elements of BPM, we proposed six principles for designing the interplay of BPM and digitalization in organizations.

Our empirical investigation was situated in a Norwegian context and included 104 respondents. While we have no reason to believe that our findings should not be valid and useful in other regions, this is a limitation in generalizing our findings, and a natural follow-up would be to investigate our research questions in other geographical areas. We are also aware of the potential response bias in our sample. Moreover, to outline the principles for designing the interactions of BPM and digitalization, we applied the six core elements of BPM by Rosemann and vom Brocke (2010) as our theoretical lens. We acknowledge that there are more issues related to the interplay of BPM and digitalization than we have dealt with in this study.

This study has several implications for organizations. First, managers may use our proposed design principles to decide how to integrate BPM and digitalization. Second, although this study showed that each discipline nurtures its own culture, building an organizational culture that combines values from each discipline can enable a process-oriented organization to innovate its operations and services with digital technology. Third, managers should align the responsibilities and tasks of process owners with the demands for the digitalization of business processes. Fourth, managers, when integrating BPM and digitalization, should take care not to impede the generative attributes of each discipline.

Processes and digital technologies play important roles in society at all levels. BPM seeks to understand how processes unfold and explores how new practices may better serve individuals, organizations and society (vom Brocke et al., 2021), while digitalization is concerned with how various kinds of modern digital technologies may trigger organizational and social changes (Markus and Rowe, 2023; Suri and Jack, 2016).

This study is one of the first studies to investigate the interplay between BPM and digitalization – how digitalization affects BPM practices in organizations and how BPM influences digitalization outcomes. In addition, this study offers novel principles for designing the interaction between BPM and digitalization.

This research demonstrates the theoretical merit of a reference architecture-based approach to life cycle cost (LCC) analysis system provision in the built environment. LCC insight is considered fundamental to sustainable decision making by asset managers; however, the current capabilities in practice do not align with the political ambition and the scale of competencies required to realise sectoral emissions–reduction targets.

In pursuing practical outcomes, the study employs a custom design science research-inspired methodology. Domain requirements are gathered via literature research as an initial top-down software reference architecture which is refined, bottom-up, through testing and implementation in a representative case study. A prototype IT system and reference architecture artefact are developed and used to evaluate the concept qualitatively through broad practitioner focus groups.

Sentiment analysis of the expert opinions is broadly positive and helps to substantiate the proposal’s theoretical suitability in addressing the scalability challenge. Additionally, constructive feedback provides guidance towards this trajectory, highlighting the importance of aligning with existing communities and standards, broadening future research scope to consider further scenarios and prioritisation of efforts to build trust around contracts and data quality.

The novelty of the work is the provision of the reusable LCC reference architecture development methodology.

The concept has the potential to provide LCC capabilities to industry at scale while the artefacts developed herein can be appended to existing LCC standards as implementation guidance to support IT system developers. Furthermore, the developed methodology can be employed in harmonisation efforts between policy and practice.