Purpose 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. Design/methodology/approach 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. Findings 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. Practical implications 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. Originality/value 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.

Purpose – This study aims to create a better understanding of how practitioners implement and work Agile while balancing the tensions arising between stability and change.

Design/methodology/approach – 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.

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

Research limitations/implications – 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.

Practical implications – 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.

Originality/value – 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.

Today's dynamic business environment must continuously adapt its software development methods to changing technologies and new requirements on the part of customers. Therefore, Agile methods are being used more and more used because they emphasize both flexibility and the ability to change. However, at the same time, the business-driven need for predictability and control remains. The purpose of this case study is to explore and theorize on paradoxical tensions and ambidexterity during an Agile software development project at a government agency. The study empirically examines how tensions and the ambidextrous responses to these tensions are related to Agile values. Data was collected by conducting interviews and studying internal project documents. Four categories of tensions (learning, organizing, performing, and belonging) were used for analytical purposes. The findings suggest that most of the tensions perceived were in the categories of learning and performing. There are, furthermore, several connections between the ambidextrous responses to these tensions and Agile principles. A deeper understanding of Agile values and principles is required in order to make projects successful. The contribution made by the study, therefore, is of great importance because Agile methods are for leading projects, not only in Agile software development, but also in other industries and sectors.