ADAPTATION PATTERNS IN AGILE INFORMATION SYSTEMS DEVELOPMENT TEAMS

This research draws on team adaptation theory to study how agile information systems development (ISD) teams respond to non-routine events in their work environment. Based on our findings from a qualitative case study of three ISD teams, we identified non-routine events that could be distinguished according to the three categories task volatility, technological disruption, and team instability. In addition, we found three patterns of reacting to these events that differed regarding complexity and team learning. Our results show that the theoretical link between different types of events and adaption patterns depends on the type of event and the reach of the events´ impact as well as on the extent to which the teams followed an iterative development approach. While previous literature either examined ISD team agility as the extent to which agile techniqus and methods are applied, or as a capability to adapt to changes, this research is the first to study how more or less agile teams react to non-routine events. By taking a process view and examining the influnce of iterativeness on the link between events and adaptation patterns, this study helps reconcile the behavioral and capability perspectives on agility that have so far been disconnected

Bridging the Gap Between Research and Practice: The Agile Research Network

We report an action research-oriented approach to investigating agile project management methods which aims to bridge the gap between academic research and agile practice. We have set up a research network of academics from two universities, through which we run focussed project-based research into agile methods. Organisations are invited to suggest an ‘agile challenge’ and we work closely with them to investigate how challenge affects them. Our approach is both academic and practical. We use appropriate research methods such as interviews, observation and discussion to clarify and explore the nature of the challenge. We then undertake a detailed literature review to identify practical approaches that may be appropriate for adoption, and report our findings. If the organisation introduces new practices or approaches as a result of our work, we conduct an academic evaluation. Alternatively, if we uncover an under-researched area, we propose undertaking some basic research. As befits the topic, we work iteratively and incrementally and produce regular outputs. In this paper we introduce our approach, overview research methods used in the agile research literature, describe our research model, outline a case study, and discuss the advantages and disadvantages of our approach. We discuss the importance of producing outputs that are accessible to practitioners as well as researchers. Findings suggest that by investigating the challenges that organisations propose, we uncover problems that are of real relevance to the agile community and obtain rich insights into the facilitators and barriers that organisations face when using agile methods. Additionally, we find that practitioners are interested in research results as long as publications are relevant to their needs and are written accessibly. We are satisfied with the basic structure of our approach, but we anticipate that the method will evolve as we continue to work with collaborators

Enterprise Agility: Why Is Transformation so Hard?

Enterprise agility requires capabilities to transform, sense and seize new business opportunities more quickly than competitors. However, acquiring those capabilities, such as continuous delivery and scaling agility to product programmes, portfolios and business models, is challenging in many organisations. This paper introduces definitions of enterprise agility involving business management and cultural lenses for analysing large-scale agile transformation. The case organisation, in the higher education domain, leverages collaborative discovery sprints and an experimental programme to enable a bottom-up approach to transformation. Meanwhile the prevalence of bureaucracy and organisational silos are often contradictory to agile principles and values. The case study results identify transformation challenges based on observations from a five-month research period. Initial findings indicate that increased focus on organisational culture and leveraging of both bottom-up innovation and supportive top-down leadership activities, could enhance the likelihood of a successful transformation

Coordinating Knowledge Work in Multi-Team Programs: Findings from a Large-Scale Agile Development Program

Software development projects have undergone remarkable changes with the arrival of agile development methods. While intended for small, self-managing teams, these methods are increasingly used also for large development programs. A major challenge in programs is to coordinate the work of many teams, due to high uncertainty in tasks, a high degree of interdependence between tasks and because of the large number of people involved. This revelatory case study focuses on how knowledge work is coordinated in large-scale agile development programs by providing a rich description of the coordination practices used and how these practices change over time in a four year development program with 12 development teams. The main findings highlight the role of coordination modes based on feedback, the use of a number of mechanisms far beyond what is described in practitioner advice, and finally how coordination practices change over time. The findings are important to improve the outcome of large knowledge-based development programs by tailoring coordination practices to needs and ensuring adjustment over time.Comment: To appear in Project Management Journa

Adaptation of enterprise architecture efforts to an agile environment

Agile ways of working have become mainstream, with many organisations practising a form of agile. Agile maturity among those organisations differs. In a research conducted by VersionOne Inc. (2016), 82% of the participating organisations stated to be at or below the level of ‘still maturing’. Existing agile and architecture methods have begun to incorporate some aspects of each other, with agile methods including architecting, such as the Scaled Agile Framework (SAFe), and architecture frameworks such as TOGAF (the Open Group Architecture Framework), adding agile elements (Poort, 2014). This study addresses the question how to shape the architecture function to effectively achieve compliance with architecture regulations, of solutions realised in an agile environment. To answer this question a multiple-case study was done, studying three different organisations. The findings are translated into seven propositions

Learning in an Agile Setting: A Multilevel Study on the Evolution of Organizational Routines

Recognizing a serious lack of research on routinized individual actions and organizational adaptation in the stability-change paradox, we intend to provide an in-depth explanation of the way in which agile methods affect organizational learning in self-managed, team-based organizations, taking a multi-level evolutionary approach. We explore learning in agile organizations by breaking the analysis of organizational routines down into different levels \u2013 individual, team and organization \u2013 and describing the process of variation, selection and retention of routines at each level. Leveraging on multiple case studies, we discuss how team members learn and gain knowledge, from both direct and indirect experience, and analyze how teams develop conceptual frameworks and interpret those experiences. Finally, we discuss how organizational memory develops and how teams in agile organizations adapt simultaneously within an ecological structure that also comprises the changing environment. Our findings reveal substantial flaws in the capacity of agile methods to foster organizational learning