Search results

The purpose of this study is to apply the concept of organizational ambidexterity as a conceptual lens to increase the understanding of tensions between exploitation (continuity) and exploration (change) in Agile software development (ASD) project teams, and particularly the balancing (ambidextrous) strategies utilized.

A conceptual framework was constructed from interdisciplinary sources on ambidexterity. A literature review of publications on ambidexterity in ASD was then performed, and the results from the selected publications were classified according to an extension of the conceptual framework.

Contextual ambidexterity in ASD is affected by the four basic coherent concepts: time, task, team and transition. The study found that most ambidextrous factors and strategies were task and team-related. In addition, a mixture of hard (performance) strategies and soft (social) strategies is needed in order for people/teams to (be able to) become ambidextrous.

To provide a better understanding of ASD, it is important to identify a broader set of ambidextrous factors and strategies that can impact ASD project teams. The expanded conceptual framework can serve as a basis for future empirical research and provide insights to practitioners on how to strengthen ambidexterity in ASD projects.

The contribution is of great importance for ASD research and practice, as ASD methods are a popular method for managing projects within ASD and in other nonsoftware organizations. In addition, as more and more organizations struggle to deal with rapidly changing environments, interest in the phenomena of paradoxical tensions and the strategy (ambidexterity) to deal with these tensions increase.

Agile methods are increasingly being applied in the contexts of innovation beyond traditional information technology (IT) and physical product development projects, such as when process improvements are being implemented. Nevertheless, this phenomenon is still recent and little addressed in the literature, with few descriptions of empirical cases. This study aims to address this gap.

This multiple case study aims to present and discuss the application of Agile practices embedded in large companies’ innovation value chains, focusing on improvements of business processes. The following research question is pursued: How are large companies applying elements of Agile methods to their innovation processes when implementing incremental improvements in their operational processes? Based on the idea that the Agile-Stage-Gate model is an alternative to this challenge, this study investigates the application of this hybrid model in two large Brazilian companies by presenting their idiosyncrasies, lessons learned, adaptations, challenges and benefits.

Overall, it was observed that the experience with the application of the Agile-Stage-Gate model is positive for these companies, with better customer engagement, easier project control and increased productivity of the project team.

For those aiming to implement the Agile-Stage-Gate model, this paper identifies the main adaptations made in order to combine the purist approaches and critical success factors for its implementation.

This study aims to create a better understanding of how practitioners implement and work Agile while balancing the tensions arising between stability and change.

A grounded theory approach was used to explore what happens in practice when software development teams implement and work Agile. The empirical data consists of twenty semi-structured interviews with practitioners working in fourteen different organizations and in six different Agile roles.

As a result, a substantive theory was presented of continuously balancing between stability and change in Agile teams. In addition, the study also proposes three guidelines that can help organizations about to change their way of working to Agile.

The inherent limitation of a grounded theory study is that a substantial theory can only explain the specific contexts explored in that study. Thus, this study's contribution is a substantial theory that needs to be further developed and improved.

The proposed guidelines can help organizations about to change their way of working to Agile. They can also assist organizations in switching from “doing Agile” to “being Agile”, thus becoming more successful.

The new perspective that this study contributes is the fact that our discovered categories show that several inherent processes are ongoing at the same time in order to balance the need to have both stability and change.

This paper aims to contribute to the multinational company (MNC) literature by studying the diffusion of a management idea within an MNC and its interaction with the MNC’s corporate immune system (CIS).

The qualitative single case study draws on evidence of how a management idea augments within an MNC and changes its development practice.

The study identifies four phases of the diffusion process and presents the interaction between the management idea and the CIS in each phase.

The more subsidiaries within an MNC that take the initiative to adopt a management idea, the harder will it become for the headquarters (HQ) to reject it. Thus, to ensure that changes in management practices are based on informed and, ideally, deliberate decisions, managers should critically evaluate management ideas immediately at inception.

The study breaks new ground by explaining how the CIS reacts to the diffusion of management ideas in MNCs.

Digitalising cities requires new urban governance processes that account for rapidly changing environments and technological advances. In this context, agile development methods have become valuable, if not necessary. However, agile development contradicts public administration practices of risk aversion and long-term planning. The purpose of this study is to discuss practical avenues for navigating these two contradictions by adapting agile development to the needs of public sector organisations.

The authors review the collaborative elaboration of Dresden’s smart city strategy as a critical case study. Dresden’s smart city strategy was developed using agile development and quadruple-helix innovation. The year-long co-creation process involved stakeholders from various groups to conceive an integrated and sustainable vision for digitalisation-based urban development.

Despite the apparent contradictions, this study finds that key aspects of agile development are feasible for public sector innovation. Firstly, risks can be strategically managed and distributed among administration and non-administration stakeholders. Secondly, while delivering value through short iterative loops, adherence to formal processes remains possible. Informal feedback cycles can be harmoniously combined with official statements, allowing iterative progress.

The empirical material is based on a single case study and thus risks overemphasising the general applicability of the proposed methods.

This paper outlines practical steps to greater agility for public administration engaged in digitalising cities. The paper conceptualises a forward and lateral momentum for the agile development of a smart city strategy that aims to reconcile formal policymaking processes with short-term loops and risk aversion with experimental value creation. This approach balanced risks, created value and enhanced the strategy‘s alignment with strategic frameworks, ultimately promoting innovation in the public sector.

This paper proposes a novel, empirically grounded conceptualisation of implementing agile methods that explicitly recognises the peculiarities of public administrations. It conceptualises the orchestrated and pragmatic use of specific agile development methods to advance the digitalisation of cities.

This paper aims to analyze the degree of contribution of the entrepreneurial orientation (EO) of organizations in the use of agile methods (AM) in project management.

A quantitative approach with the application of a survey with project professionals resulted in 206 valid answers. The data were analyzed using structural equation modeling and the method of partial least squares (PLS).

The results present empirical evidence of the significant contribution of EO in the use of AM in project management, confirming the main hypothesis of this study. This effect was not influenced by the control variables tested.

This study contributes to the development of research on AM and minimizes the literature gap on the connection between entrepreneurship and AM. The results are limited to the sample. Studies with broader samples and different segments are suggested, as well as the contribution of each dimension of the EO to AM.

Innovativeness, risk-taking, proactiveness, autonomy and competitive aggressiveness (EO dimensions) can contribute to the use of AM and guide actions to develop these behaviors, pursuing better adherence to agile values and the use of AM in project management.

The originality of this study regarding the connection between EO and AM lies on the presentation of a theoretical model of this relationship and reduces the gap in this research field. Given the degree of EO contribution in AM (19.7%), there are other factors that affect the use of AM in project management that should be investigated.

Literature reveals ongoing debates around the role of business analysts in agile software development (ASD) teams. This can be attributed, in part, to a knowledge gap concerning how business analysts contribute to overall team capabilities, particularly those which are essential in enabling teams to respond to fast-paced environmental changes. The purpose of this study was to address this gap by investigating how business analysts (BAs) contribute to the dynamic capabilities of ASD teams.

Through a deductive approach, this study adapted and applied a research model based on the team dynamic capabilities (DC) theory to explore the contributions of BAs in agile teams. The study was executed using a qualitative, single case study research strategy directed at an ASD team in the financial services industry. Moreover, data were collected through face-to-face, semi-structured interviews; a focus group; non-participant observation and physical artefacts review. The thematic analysis technique was used to analyse the data.

The study contributes to teams DC theory through four theoretical propositions centred on the role of BAs. The proposition highlights how BAs relationship management, tacit knowledge sharing, task mental models and transactive memory are key contributors of ASD teams' DC. The study also found that BAs contribute to ASD teams' ability to embrace agile principles 2, 4, 6 and 12. This study can inform the design of capacity development programmes for individual team members and BAs and thus help managers curate teams that will best promote DC.

This study can inform the design of capacity development programmes for individual team members and BAs and thus help managers curate teams that will best promote DC.

This study builds on the relatively few studies which focus on DC within software development (SD) teams and ASD project teams. Moreover, the study explores how an individual (i.e. a BA) can contribute to the DC of a team.

This paper seeks to examine how expectations from business analytics (BA) by members of agile information systems development (ISD) teams affect their perceptions and continuous use of BA in ISD projects.

Data was collected from 153 respondents working in agile ISD projects and analysed using partial least squares structural equation modelling techniques (PLS-SEM).

Perceived usefulness and technological compatibility are the most salient factors that affect BA continuance intention in agile ISD projects. The proposed model explains 48.4% of the variance for BA continuance intention, 50.6% of the variance in satisfaction, 36.7% of the variance in perceived usefulness and 31.9% of the variance in technological compatibility.

First, this study advances understanding of the factors that affect the continuous use of BA in agile ISD projects; second, it contextualizes the expectation-confirmation model by integrating technological compatibility in the context of agile ISD projects.

This is the first study to investigate BA continuance intention from an employee perspective in the context of agile ISD projects.

This study aims to understand how practitioners use their insights in software development models to share experiences within and between organizations.

This is a qualitative study of practitioners in software development projects, in large-, medium- or small-size businesses. It analyzes interview material in three-step iterations to understand reflexive practice when using software development models.

The study shows how work processes are based on team members’ experiences and common views. This study highlights the challenges of organizational learning in system development projects. Current practice is unreflective, habitual and lacks systematic ways to address recurring problems and share information within and between organizations. Learning is episodic and sporadic. Knowledge from previous experience is individual not organizational.

Software development teams and organizations tend to learn about, and adopt, software development models episodically. This research expands understanding of how organizational learning takes place within and between organizations with practitioners who participate in teams. Learnings show the potential for further research to determine how new curriculums might be formed for teaching software development model improvements.

Today’s software engineers often work in teams to develop complex software systems. Therefore, successful software engineering in practice require team members to possess not only sound programming skills such as analysis, design, coding and testing but also soft skills such as communication, collaboration and self-management. However, existing examination-based assessments are often inadequate for quantifying students’ soft skill development. The purpose of this paper is to explore alternative ways for assessing software engineering students’ skills through a data-driven approach.

In this paper, the exploratory data analysis approach is adopted. Leveraging the proposed online agile project management tool – Human-centred Agile Software Engineering (HASE), a study was conducted involving 21 Scrum teams consisting of over 100 undergraduate software engineering students in multi-week coursework projects in 2014.

During this study, students performed close to 170,000 software engineering activities logged by HASE. By analysing the collected activity trajectory data set, the authors demonstrate the potential for this new research direction to enable software engineering educators to have a quantifiable way of understanding their students’ skill development, and take a proactive approach in helping them improve their programming and soft skills.

To the best of the authors’ knowledge, there has yet to be published previous studies using software engineering activity data to assess software engineers’ skills.