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.

Rapid changes in the business environment and the accelerating dynamics and increasing complexity shaping the functioning of organizations have given rise to modern concepts of people management. The Management 3.0 (M3.0) concept was developed based on agile project management concept; however, it can be implemented not only in projects, but also in the entire organization. It consists of six pillars such as: energizing people, empowering teams, aligning constraints, developing competencies, growing structure, and improving everything. The paper aims to present the relationships between the level of implementation of the above-presented pillars and such variables as the scope of use of agile project management methodologies, and project managers' (PMs) as well as HR practitioners' knowledge in this area.

Members of PMI and IPMA representing 34 companies located in Poland took part in the research which was based on a CAWI method.

Research shows that the level of M3.0 implementation – in terms of its six pillars – is internally consistent but mostly on a “defined” level. No correlation was observed between the implementation of M3.0 and the frequency with which agile project management methodology is applied. On the other hand, there is a strong correlation between the level of PMs' knowledge and the implementation of some of the M3.0 pillars. HR specialists' knowledge in the field of M3.0 is not associated with organizational advances in the implementation of M3.0.

As the first research project in the area of M3.0, this study proposes practical implications as well as topics which require further empirical exploration.

Organizational culture has an impact on various activities in organizations, including project management (PM). The aim of the study is to answer the following research questions: RQ1: what significance is attributed to organizational culture compared to the objective project characteristics when choosing the dominant PM methodology in organizations? RQ2: which type of organizational culture is preferred for successful implementation of different PM methodologies? RQ3: what kind (if any) of relationship exists between the dominant type of organizational culture in organizations and the dominant PM methodology?

The author surveyed 100 project managers working in the financial industry in Poland with the use of personal structured interviews. The competing values framework (CVF) concept authored by Cameron and Quinn was used.

Project managers find organizational culture more important than objective project characteristics when choosing the dominant PM methodology in an organization. Although statistical analysis revealed a significant relationship between the preferred type of organizational culture and PM methodology, there is no significant relationship between the existing type of organizational culture and the PM methodology which prevails in the company.

Future research should investigate other industries and other typologies of organizational culture.

The paper provides recommendations for management practice on how to shape organizational culture in the context of successful PM with the application of different PM methodologies.

This study fills a gap in the theory of PM by identifying and empirically verifying the theoretical linkage between the type of organizational culture and PM methodology.

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.

This research work aims to arise from developing new communication channels for customer service in micro, small and medium enterprises (MSMEs), such as chatbots. In particular, the results of the usability testing of three chatbots implemented in MSMEs are presented.

The methodology employed includes participants, chatbot development platform, research methodology, software development methodology and usability test to contextualize the study's results.

Based on the results obtained from the System Usability Scale (SUS) and considering the accuracy of the chatbot's responses, it is concluded that the level of satisfaction in using chatbots is high; therefore, if the chatbot is well integrated with the communication systems/channels of the MSMEs, the client receives an excellent, fast and efficient service.

The paper analyzes chatbots for customer service and presents the usability testing results of three chatbots implemented in MSMEs.

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.

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 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.