Search results

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.

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.

After deciding to become agile, many information technology (IT) units struggle; they underestimate the needed managerial expertise to alter their current culture toward an agile one, particularly when cross-cultural (f)actors are involved. Given that work values are the key to an organizational culture, the study derived a set of agile work values of culturally diverse IT professionals together with a set of well-known generic work values. Consequently, the authors illustrate that managers in charge of the transition to an effective agile culture must pay serious attention to the specific value constellations of its often highly diverse workforce.

A literature review resulted in an initial list of agile work values. Then, mainly through a Delphi round, 12 agile-specific work values were established. These were survey rated, along with the validated set of 18 generic work values, by 102 British and Indian IT professionals in a digital service and consulting firm that was requested by its client to become agile. The observations made in 14 feedback group-interview-type dialogs enriched the surveyed data further.

In the current exploratory study, four generic value dimensions were complemented by two agile-specific ones: team communication and shared responsibility. Among the British and Indian (on-site and offshore) workers, only 2 of the 30 current work values were shared while 7 significant value differences were found, explaining the noted employee bitterness, productivity losses and client disengagement. This situation was reflected in the many discrepancies between the professionals' ideal agile way of working and how their unit was currently functioning.

The multi-method study shows an over-optimistic approach to becoming agile in a common cross-cultural context; insights are gained on how to optimize agile ways of organizing IT work when British IT workers collaborate with Indian IT workers. It may benefit many agile practitioners and managers working with(in) cross-culturally mixed and partly remote teams.

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.

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.

Roadmapping has been used as an approach to support market, product and technology-integrated planning, resulting in a document commonly known as a roadmap. Despite the gains made in relation to the technique, recent studies indicate that most users leave or have difficulties in sustaining the process (i.e. maintaining the updated roadmaps). This paper aims to present a framework for continuous roadmap updating that incorporates principles from agile management fields.

The framework was developed through action research in a manufacturing firm in the construction industry.

The results demonstrate a positive impact on the degree of continuous information monitoring, roadmap credibility and use of the roadmap during innovation strategy decisions.

The key contribution of this framework is the demonstration of a new strategy for carrying out the maps in which information is internalized by the organization itself, using agile teams, without commissioned specialists and as part of the work standards.

In the present article, the authors tackle the problem of IT documentation, which plays an important role in information technology (IT) project management.

They provide a simple tool based on five complementary views, which should be detailed by the project team using a classic source code management platform.

The proposed tool is open source and may be reused by any IT team in various project contexts and heterogeneous development methods.

This research provides an operational framework, which facilitates IT project management and documentation. The framework is open source and may be easily downloaded by any other IT team.

The purpose of this paper is to highlight a collaborative effort between academia (University of North Texas, Team Sciences) and practice (Toyota Connected (TC)). This study concentrated on current problems that had been experienced by TC: How to structure and manage multiteam systems (MTSs)?

This research study utilized a realist systematic review to address an existing problem by working collaboratively with TC and academia. This collaboration involved problem identification, the development of research questions and a full systematic review guided by the research questions.

This realist systematic review merged the literature with current practices at TC in an effort to gather evidence to support the best method of structuring and managing MTSs. The findings include a leadership structure that incorporates both shared leadership (bottom-up) and existing hierarchical structures (top-down).

The MTS models presented in this study provide new models for organizations/manufacturers/industries to use as a guide when structuring their MTSs.

This study provides an example of a collaborative research effort between practice and academia using a realist systematic review. The paper also provides some multiteam system models that could be implemented and tested in different organizations. Also, new responsibilities and roles for scrum and MTSs are presented as a new method of achieving Agile.

Business process re-engineering (BPR) initiatives are complex endeavours which require many factors to ensure success. However, most studies focus on the organisational processes and improvement within the organisation itself and less on the project team and management dynamics. The study aimed to identify factors that enabled the completion of a BPR, in a technical firm, based on reflections on the project management style.

The study entailed a descriptive and interpretive case study with reflections from project team members. Data were analysed using descriptive statistics and content analysis.

Findings revealed that critical success factors for BPR in a technical firm include project leadership and sponsorship, organisational culture and attributes, team dynamics and the nature (activities), and duration of the process.

The findings will benefit project managers in improving their competence and project success through reflective practice. The identified factors could be used in future projects of a similar nature and size to improve how organisations execute BPR projects.

The study used reflections to identify success factors for BPR in a technical firm.

This paper aims to describe the students’ experience in adopting design thinking (DT) and extreme programming (XP) throughout a course of technology innovation workshop in a master of business administration (MBA) degree program.

This study analyzes data (performed process and achieved results) from the students’ reports and the instructor’s observations about three courses held in 2016, 2017 and 2018. In each course, there were students conducting activities to understand, develop, and validate the market, customer, user and prototype.

This paper identifies that the processes of DT and XP promote active and collaborative learning relationships. The adopted activities along with a mix of different backgrounds from the students can promote good insights to understand the user problem and build a technological solution with incremental innovation.

This paper describes only a unique view from the instructor’s knowledge; therefore, others might present different scenarios and results.

The paper contributes to the characterization of DT and XP activities when teaching technological innovation in a MBA.