From Empowerment Dynamics to Team Adaptability: Exploring and Conceptualizing the Continuous Agile Team Innovation Process

To foster their innovation teams’ adaptability, organizations are increasingly relying on agile teams. While research on the adoption of agile methods and practices has grown tremendously in the past decade, little is currently known about the human side of agile teams and how it contributes toward the emergence of adaptability. While the Agile Manifesto states that individuals and interactions are more important for agile product development than tools and processes, research on how these interactions unfold is still in its infancy. To shed light on the human side of adaptability, 44 semi‐structured, in‐depth interviews were conducted with team members and leaders from various teams at three organizations (i.e., two German and one multinational European firm). The inductive analysis identified empowerment as a focal human factor for adaptability emergence. A model of the continuous agile team innovation process is developed and uncovers the importance of dynamic empowerment states and their temporary equilibria for team adaptability. The underlying findings demonstrate that empowerment is not a static state, but rather emerges through the interactions between various actors. Specifically, the team and its leader engage in both empowerment‐enhancing and empowerment‐reducing activities. These activities are further influenced by the agile team’s immediate context: Two‐fold customer influences, that is, supporting and hindering empowerment interactions, and the organizational environment, that is, undergoing an agile transformation and supportive top management behaviors, play an important role in affecting the empowerment dynamics that result in team adaptability. As such, this study contributes to the innovation and management literatures by revealing the dynamic role of the empowerment and adaptability constructs for agile innovation processes and the importance of various actors and the organizational environment for fostering adaptability. Practical insights are offered to management, teams, and team members on how to create conditions for empowerment dynamics and consequently adaptability to unfold

Decisions-making in Agile Information Systems Development: The Role of Empowerment and Authority

Agile information systems development (ISD) teams are claimed to work via self-organized and autonomous methods. Yet little research exists on how these teams make decisions. Therefore, this research-in-progress paper conceptualizes a multilevel model that examines decision-making–team empowerment and project managers’ decision-making authority–in agile ISD teams and its effect on team members’ work engagement and performance. Preliminary results show satisfactory psychometric criteria for the measurement instrument. Within the main study, multilevel analyses using hierarchical linear modeling and hierarchical linear regression will be used to examine cross-level effects. We expect our research to contribute to deeper understanding of agile ISD teams’ decision-making and to the limited evidence on project managers’ role in agile ISD

Looking for a place to hide: a study of social loafing in agile teams

Social loafing refers to the behaviour of individual members of a team who have tendency not to work as hard as they could or should, because social groups provide a degree of anonymity such that individual team members feel that their poor performance will be hidden by the overall output of the team. Agile Software Development philosophy espouses the importance of cohesive project teams, the empowerment of these teams, and the collective ownership of the code produced by the team — social values similar to those of communities of practice. This paper posits that one of the unintended consequences of Agile Software Development is that it may give rise to social loafing, under certain conditions. In order to test this proposition, research was carried out on two software development teams over an eight month period to determine if the values inherent in Agile Software Development could give rise to social loafing The theoretical assumption adopted by the authors was that the project team which fully adopted the agile approach would exhibit a greater tendency for social loafing, in comparison to the other team. The findings of the study indicate, however, that the opposite was the case; accordingly, the study’s findings are interpreted to offer an explanation for this apparent paradox

Unpacking Agile Enterprise Architecture Innovation work practices: A Qualitative Case Study of a Railroad Company

Agile EA is the process for managing enterprise architecture modeling and redesign efforts with principles of agile methods. However, very little work has been done till date on how organizations adopt these methodological innovations such as integration of agile methods with enterprise architecture. This is problematic, because we know that organizations face stiff challenges in bringing new innovations that fundamentally disrupt their enterprise architecture. Hence we ask: How does agile EA get adopted in practice and what are the underlying mechanisms through which teams self-organize and adapt? To this end, we studied a large-scale agile EA development effort to modernize the legacy systems at a top railroad company referred to as “Alpha” (a pseudonym). Our qualitative analysis shows how multi-teams self-organize and adjust the pace of the development efforts by strategically (1) choosing different type of agile methods and (2) embedding resources across teams for increasing communications

Agile or Fragile? - The Depleting Effects of Agile Methodologies for Software Developers

Despite the increasing diffusion of agile software development methodologies (ASDM) in firms, aca-demic studies in this field – though rising in number – are largely missing out on the implications for the individual software developer. The application of agile methodologies in software development projects has significant impact on the individual developer’s way of working. While some empirical research evaluated the advantages of ASDM for individuals, potential negative consequences for de-velopers, who have to cope with multiple draining demands in their daily work, remains largely unex-plored. Using resource depletion theory as a lens, we develop a research model to examine how the use of ASDM potentially decreases individual job satisfaction and increases turnover intention. We suggest that the effect is mediated by developers’ level of depletion expressed by psychological strain. In addition, we aim to determine who is more or less affected by depletion in an agile context intro-ducing the capacity for self-control as a moderator. To test our model, we plan to conduct a cross-sectional field survey among software developers working in agile teams. Drawing attention to under-represented negative implications on an individual level, we want to contribute to a more balanced picture of ASDM use in theory and practice

Towards Agile Workforce – Case Study Research in Three Companies

Many companies today face a highly turbulent and volatile environment caused by intense foreign competition, rapid technological change, shorter product life-cycles, and customers demand- ing more customized products. Several strategies have been developed to deal with unpredictability in the environment. Agility and agile methods have been widely accepted as a new competitive concept in many countries, including Finland. However, the understanding of how to build agile organizations remains weak. The thesis provides initial empirical evidence to better understand essential elements of agile workforce and their relationship with organizational agility. More specifically, the research aims to understand and describe the concept of workforce agility in the selected case companies. The second goal is to discover the management practices, methods and tools that the case companies have adopted in order to enable and support the actions of an agile workforce. The thesis employs qualitative research methods with empirical approach doing semi- structured interviews in case study companies and conceptual approach using previous academic research. The case study companies are OP, DNA and Alma Media. The phenomenon of developing an agile workforce is rather new in large previously traditional organizations in Finland. Consequently, the study is exploratory by nature and aims to increase familiarity of the phenomenon in the Finnish context. The different cases were studied through interviews with managers that have been in a superior decision-making position and responsible for the change process, and managers or employees that have participated the implementation of the change process. Also, a HR specialist from Vincit was interviewed for her expertise on enterprise agility. According to the findings employees’ agile capabilities and attitudes towards agility are important factors when transforming towards enterprise agility. Findings show that companies that aim to make their organization more agile face two kinds of challenges. Firstly, companies must be able to arouse excitement and interest towards agility among employees. The second challenge concerns enabling agile work and managing the frustrations that arise. To deal with these challenges case companies employed similar practices, tools and methods that enable change management, change attitudes and culture, increase internal communication, knowledge sharing and cooperation; support empowerment and work organization, and promote new work methods and training

Why apply agile? - A literature review on work outcomes in agile information systems development

Agile information systems development (ISD) has become a popular way to manage IT projects. One of the key claims of agile ISD is to increase employees’ work outcomes, such as job satisfaction. However, the research landscape is heterogenous and lacks of a comprehensive overview. In this research, we set out to analyze and synthesize the current state of research on agile ISD and work outcomes by a systematic literature review. Overall, we found a trend of a positive relationship of agile ISD on work outcomes, although there is a variety of constructs that influence this relationship. We propose four directions for future research: perceptions of work, extended quantitative findings, multi-level effects and IT project success

Applying Adapted Big Five Teamwork Theory to Agile Software Development

Teamwork is a central tenet of agile software development but various teamwork theories only partially explain teamwork in that context. Big Five teamwork theory is one of the most influential teamwork theories, but prior research shows that the team leadership concept in this theory it is not applicable to agile software development. This paper applies an adapted form of Big Five teamwork theory to cases of agile software development. Three independent cases were drawn from a single organisation providing a measure of control over contextual factors affecting the teamwork. The findings show that the adapted form of Big Five teamwork theory, including a shared team leadership concept, is fully applicable to some forms of agile software development, but not all. For practitioners, insights as to which agile practices support teamwork are provided

Three Levels of Agile Planning in a Software Vendor Environment

There is a misconception that agile development requires minimal planning effort. In reality, an agile approach for market-driven software development requires highly disciplined, reliable, and accurate planning practices to swiftly plan and develop high value innovations in a software vendor environment. This study investigated a highly successful international software vendor based in Melbourne, Australia to provide a case study on agile planning practices. Five planning practices which were identified underlay successful agile software development for software vendors. These planning practices were driven by agile concepts such as adaptation, self-organizing, cross-functional collaboration, and empowerment/delegation. We constructed a conceptual framework for agile planning practices APP (agile planning practices) Framework illustrating the three levels of agile planning