Search results

Introduction: The COVID-19 pandemic was unprecedented, and none of the world’s think tanks could have predicted how far it would spread. People visualise the pandemic as a classic example of a VUCA environment (an environment characterised by volatility, uncertainty, complexity, and ambiguity). Managing COVID-19 requires unique and different leadership qualities.

Purpose: This study’s rationale emphasises that VUCA demands strategic and agile leadership. Leaders across the globe must acknowledge the fact that the elements of VUCA, i.e. volatility, uncertainty, complexity, and ambiguity, are not synonymous and hence need differential treatment. Also, recommend adopting agile leadership to tackle the VUCA world.

Methodology: This is a conceptual study focusing on agile leadership. The study addresses the challenge of leading in the VUCA environment. The constituting components of VUCA are differentiated, followed by an extensive literature review of agile leadership.

Findings: VUCA is the new normal and is there to stay. Business leaders still need to counter VUCA due to their incapacity to distinguish and treat the components equally. Furthermore, there is an emergent need to develop an agile workforce, agile organisations, and agile leadership to combat VUCA. The study indicates that business leaders must be agile enough to handle the COVID-19 pandemic and future crises. There is a constant need to ensure agility. This study will provide a deep insight into VUCA and help business leaders emerge victorious in turbulent times.

This study seeks to illuminate the managerial tensions inherent in implementing scaled agile (on the organizational, top management, middle management and team levels) and to frame these challenges within the broader context of project management.

The study adopts a grounded theory approach and delves into a qualitative dataset sourced from 34 interviews with subject matter experts actively engaged in scaling agile initiatives within large organizations spanning various industries. Additionally, the data have been enriched through a comprehensive literature review of the existing body of knowledge on scaling agile.

As a result of our investigation, we propose a framework of managerial tensions in scaling agile in large corporate settings and a series of research propositions and questions that may contribute significantly to the body of knowledge surrounding the phenomenon of “deprojectification” and propose agenda for the future studies in the field of project management.

The study also carries significant managerial implications. Firstly, based on the insights from the practice of scaling agile in large corporate setting, management can build awareness of the challenges inherent of transitioning to agile practices. This may help to anticipate the possible problems and proactively develop strategies how to address them. Secondly, management can be instructed about contingencies inherent in scaling agile, along with the potential disfunctions and side effects (unintended outcomes) that may emerge during the transition process. Thirdly, project management practitioners can gain insights on how scaling agile may cause shifts in the approach to managing projects, project team management and competencies that need to be developed to cope with environments where various approaches to managing projects coexist.

These insights can aid in the agile transition process, beginning with directing managerial attention toward contextual factors and progressing through potential challenges at the organizational, top management, middle management and team levels. Furthermore, the study highlights possible dysfunctionalities and side effects of scaling agile, shedding light on the “dark side” of agile.

The study contributes to the expansion of the empirical database on the implementation of agile practices in large organizational settings. It plays a role in defining and delineating the phenomenon of scaling agile within the context of project management and outlines a research agenda for future project management studies. Additionally, our study adds to the ongoing discourse surrounding the “deprojectification” effect that can occur during the scaling of agile. Lastly, it establishes connections between project management and software development literature regarding the implementation of agile at scale.

This study aims to apply the Delphi method to explore the possibilities for implementing agility management concepts in Slovenian health-care organisations.

The research is based on a qualitative Delphi study encompassing 15 employees in different Slovenian health-care organisations.

Slovenian health-care organisations need to be more agile currently. For this reason, it is necessary to begin with organisational changes and organisational learning concepts to educate employees about the meaning and content of agile processes. It is essential to ensure that accepting employee mistakes and offering help to employees becomes normal practice, and it is necessary to ensure the greater trust of the management towards the employees.

The research empowers health-care professionals with new management and leadership concepts, such as agile management, sustainable leadership and leadership development methods in health care.

Agile project teams are self-managing and self-organizing teams, and these two characteristics are pivotal attributes of emergent leadership. Emergent leadership is thus common in agile teams – however, how these (informal) emergent leaders can be identified in teams remains far from understood. The purpose of this research is to uncover techniques that enable top management to identify emergent agile leaders.

We approached six agile teams from four organizations. We employ social network analysis (SNA) and aggregation approaches to identify emergent agile leaders.

We approached six agile teams from four organizations. We employ SNA and aggregation approaches to identify emergent agile leaders.

Seven emergent leaders are identified using the SNA and aggregation approaches. The same leaders are also identified using the KeyPlayer algorithms. One emergent leader is identified from each of the five teams, for a total of five emergent leaders from the five teams. However, two emergent leaders are identified for the remaining sixth team.

Emergent leadership is a relatively new phenomenon where leaders emerge from within teams without having a formal leadership assigned role. A challenge remains as to how such leaders can be identified without any formal leadership status. We contribute by showing how network analysis and aggregation approaches are suitable for the identification of emergent leadership talent within teams. In addition, we help advance leadership research by describing the network behaviors of emergent leaders and offering a way forward to identify more than one emergent leader in a team. We also show some limitations of the approaches used and offer some useful insights.

This study aims to examine the enablers of productivity of enterprise-level Agile development process using modified total interpretative structural modeling (TISM). The two main objectives of the current study are to determine the variables influencing enterprise-level agile development productivity and to develop modified TISM for the corresponding components.

To identify enablers of the productivity of enterprise-level agile software development process a literature review and opinions of domain experts were collected. A hierarchical relationship among variables that show direct and indirect influence is created using the modified TISM (M-TISM) technique with Cross Impact Matrix-Multiplication Applied to Classification analysis. This study examined and analyzed the relationships between the determinants within the enterprise using a M-TISM technique.

With the literature review, the study could identify ten enabling factors of the productivity of Agile development process at the enterprise level. Results depict that program increment (PI) planning and scalable backlog management, continuous integration and continuous delivery (CI/CD), agile release trains (ART), agile work culture, delivery excellence, lean and DevOps practices, value stream mapping (VMS), team skills and expertise, collaborative culture, agile coaching, customer engagement have an impact on the productivity of enterprise-level Agile development process. The results show that team collaboration, agile ways of working and customer engagement have a greater impact on productivity improvement for enterprise-level Agile development process.

The developed model is useful for organizations employing scaled Agile development processes in software development. This study provides a recommended listing of key enablers, that may enable productivity improvements in the Agile development process at the enterprise level. Strategists should focus on team collaboration and Agile project management. This study offers a modified TISM model to academicians to help them understand the effects of numerous variables on maintaining the productivity of an enterprise-level Agile. The identified characteristics and their hierarchical structure can help project managers during the execution of Agile projects at the enterprise level, more effectively, increasing their success and productivity.

The study addresses the gap in the literature by interpretative relationships between the identified enabling factors. The model validation is carried out by a panel of nine experts from several information technology organizations deploying Agile software development at the enterprise level. This unique method broadens the knowledge base in Agile software development at scale and provides project managers and practitioners with a practical foundation.

The purpose of this literature review paper is to explore the concept of organization agility and its relevance in today's dynamic business environment. By conducting an in-depth review of existing academic and industry literature on organization agility, this study aims to identify the key factors that influence an organization's agility and the benefits and drawbacks associated with fostering agility.

Through the technique of bibliometric analysis, we provide the growth trajectory of the field by identifying the publication trends, prominent authors and countries and most prolific journal publishing in the concerned domain. We also provide the intellectual structure of the organization agility research by identifying the prominent themes that have been worked upon till date. In addition, with the backing of the theories, contexts, characteristics and methodology (TCCM) framework, we identify the most frequently applied theories, constructs and methods in organization agility research and provide new avenues for future research by analyzing the most frequently used theories, methods, constructs and research contexts.

With the ever-increasing ambiguity and need for change (why), organization agility serves as the organization's backbone. It acts as a springboard for the organization, an anchor point that remains constant while other functional aspects constantly fluctuate and change. Organization agility can be defined (what) as the ability of organizations to quickly respond to market needs by sensing, renewing, adapting and succeeding in a turbulent market. To summarize, organizational agility matters at three fundamental aspects (where): strategic level or the market capitalizing level, internal operational level and individual level.

This paper is unique in the sense that it is the first comprehensive literature review in the field of organization agility research to use a hybrid methodology (bibliometric review with TCCMs).

This paper aims to close the gap between the generic concept of knowledge activities (KAs) and implementing them in the context of software engineering organisations concentrating on the non-technical aspects, such as team organisation and practices.

This qualitative research used a questionnaire with practitioners such as software developers and team leads who were asked to provide feedback on a set of team practices and measures typically used in software engineering projects and assess their relation to the activities of acquiring, codifying, storing, maintaining, transferring and creating knowledge. The obtained results were analysed using frequency analysis and further descriptive statistics yielding a matrix linking the investigated team practices and measures to KAs.

Team practices and measures commonly applied in software engineering can be facilitated to trigger particular KAs. While most of these team practices and measures originate from agile methods, they are not restricted to these. A purposeful composition can help in assembling a balanced set of KAs aimed at fostering given knowledge goals in software engineering organisations.

By bridging the communication and terminology gap between knowledge management research and software engineering practitioners, this work lays the foundation for assessing software teams’ knowledge profiles more easily and creating prerequisites for implementing knowledge management by facilitating common practices and measures often already part of their daily work. Hence, overhead can be avoided when implementing knowledge management.

To the best of the authors’ knowledge, this is the first study investigating application and relevance of KAs in the software industry by linking them to practices and measures well-accepted in software engineering, thus providing the necessary vocabulary for the implementation of knowledge management in software development teams.

Agile principles have been widely used in software development team practice since the creation of the Agile Manifesto. Studies have examined variables related to agile principles without systematically considering the relationships among key team, agile methodology, and process variables underlying the agile principles and how these variables jointly influence the achievement of software development agility. In this study, the authors tested a team/methodology–process–agility model that links team variables (team autonomy and team competence) and methodological variable (iterative development) to process variables (communication and collaborative decision-making), which are in turn linked to software development agility (ability to sense, respond and learn).

Survey data from one hundred and sixty software development professionals were analyzed using structural equation modeling methods.

The results support the team/methodology–process–agility model. Process variables (communication and collaborative decision-making) mediated the effects of team (autonomy and competence) and methodological (iterative development) variables on software development agility. In addition, team, methodology and process variables had different effects on the three dimensions of software development agility.

The results contribute to the literature on organizational IT management by establishing a team/methodology–process–agility model that can serve as a basis for developing a core theoretical foundation underlying agile principles and practices. The results also have practical implications for organizations in understanding and managing holistically the different roles that agile methodological, team and process factors play in achieving software development agility.

This study aims to examine the impact of two dimensions of agile work practices (i.e. agile taskwork and agile teamwork) on team efficacy and creativity. Further, it examines the mediating effect of team efficacy in the relationship between two dimensions of agile work practices and team creativity.

The data were collected from 563 professionals working in 290 information technology (IT) companies in India using a self-reporting structured questionnaire. Partial least squares-structural equation modeling (PLS-SEM) was used to test the hypothesized model.

The results demonstrate that agile taskwork and agile teamwork positively impact team creativity and team efficacy, and team efficacy positively impacts team creativity. Furthermore, team efficacy partially mediates the impact of agile taskwork and agile teamwork on team creativity.

This study shows the importance of agile work practices and team efficacy to enhance team creativity. The research offers managers strategies to boost team creativity.

There is a dearth of research examining the distinct effects of agile taskwork and agile teamwork on team efficacy and team creativity. Also, this study is one of its kind that examines the mediating mechanisms that explain the effect of agile taskwork and agile teamwork on team creativity.

In software development (SD), practitioners have realized the importance of lean thinking. A new term “Leagile” is coined, which is an integrated approach of traditional lean and agile thinking to managing the operations. The study aims to investigate the application of the Leagile principles in a new sector and establish a relationship between the adoption of Leagile approach and operational performance (OP) in SD organizations.

Empirical research is conducted to investigate the linkage between the Leagile principles and operational measures. Data is collected through surveys from 256 SD industries located in 11 states of India and analysed using the structural equation modelling approach.

The practitioners envisage a positive impact of adoption of Leagile principles on OP of SD organizations, but one of the principles, i.e. perfection, is unable to influence the performance.

The study contributes by authorizing the contribution of Leagile principles towards OP of SD organizations. The outcomes will motivate the practitioners to enhance the adoption of Leagile principles in SD organizations.