Agility is responsiveness to change

Gren, Lucas; Lenberg, Per

doi:10.1145/3383219.3383265

Cited by 24 publications

(24 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Scholars also stress the importance of understanding ASD's project context and rigorously examining if, how, why and when ASD impacts outcomes in order to strengthen our theoretical understanding of ASD (Fruhling & De Vreede 2006;Lee & Xia, 2010;Moe et al, 2008). While we agree that measuring the specific level of ASD use and its project context is warranted, some studies advocate for the measurement of techniques over methods due to their claim that few teams adopt ASD methods as a whole (Gren & Lenberg, 2020).…”

Section: Measuring Asd Techniques and Their Project Contextmentioning

confidence: 99%

“…Scholars advocate for a stronger connection between ASD and its theoretical base (Dingsøyr et al, 2012;Highsmith, 2010). To strengthen our understanding of ASD concepts and their theoretical underpinnings, prior studies argue that researchers should seek to understand the conditions under which ASD is effective and the factors that can control its influence on outcomes through empirical examination (Lee & Xia, 2010) While many identify the core of ASD as centred around agility (Conboy, 2009;Gren & Lenberg, 2020;Lee & Xia, 2010), or the ability to respond to change, and theorise based on this core, others suggest that an ASD core has yet to be discovered and that traditional theorization will help researchers identify it. We find promise in the former approach as it leverages the strengths of the measurement recommendations previously discussed (i.e., measuring agility) by highlighting which aspects of ASD may impact outcomes in a given context.…”

Section: Theorising Exclusively To Asdmentioning

confidence: 99%

See 1 more Smart Citation

Issues, challenges, and a proposed theoretical core of agile software development research

Baham

Hirschheim

2021

Information Systems Journal

View full text Add to dashboard Cite

Over the last two decades, agile software development (ASD) has garnered much attention in both research and practice. Several ASD methods and techniques have been developed and studied. In particular, researchers have provided several theoretical perspectives on ASD and contributed rich insights to the ASD practice. Still, despite calls for a more unified theoretical understanding of ASD, a theoretical core of ASD has not been identified. This paper offers a theoretical core of ASD research, clarifying what is essential and what is less essential for IS agility, hoping to spark a scholarly discussion, and provides implications of such a core for understanding method tailoring.

show abstract

Section: Measuring Asd Techniques and Their Project Contextmentioning

confidence: 99%

Section: Theorising Exclusively To Asdmentioning

confidence: 99%

Issues, challenges, and a proposed theoretical core of agile software development research

Baham

Hirschheim

2021

Information Systems Journal

View full text Add to dashboard Cite

show abstract

“…Thus, as mentioned before, it is important for the new Agile way of working to be understood, accepted and supported by all stakeholders. Unfortunately, it is rather the case that most software organizations are still hierarchical, with management units having little or no interest in, or knowledge of, process-oriented Agile practices (Gren and Lenberg, 2020). On that basis, Van Waardenburg and Van Vliet (2013) identify one successful mitigation strategy as "changing the mindset of business stakeholders".…”

Section: Take a Holistic View And Let It Take Timementioning

confidence: 99%

Balancing between stability and change in Agile teams

Lindskog

Netz

2021

IJMPB

View full text Add to dashboard Cite

PurposeThis 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/approachA 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.FindingsAs 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/implicationsThe 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 implicationsThe 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/valueThe 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.

show abstract

“…Additionally, to enable responsiveness to change, the Agile Manifesto [3] states that ASD values individuals and interactions more than processes and tools [4]. The team's importance in ASD is evidenced by the Agile Manifesto having six out of the twelve principles directly related to the team (i.e., individuals).…”

Section: Introductionmentioning

confidence: 99%

Towards a Comprehensive Understanding of Agile Teamwork: A literature-based Thematic Network

Freire

2021

Proceedings of the 33rd International Conference on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Agile Software Development (ASD) has become the mainstream software development method of choice. Its core fundamentals are based on Teamwork factors and the higher value it gives to individuals and their interactions over processes and tools. Teamwork and human factors have been addressed as essential topics in the literature, and researchers have stated the importance of measuring it to increase the chances of success of ASD projects. However, there is no common understanding regarding the factors that should be considered for defining an ASD Teamwork construct. Driven by this problem, this paper presents a thematic network that defines the themes (i.e., factors) that should be considered when addressing ASD Teamwork. The ASD Teamwork thematic network is the result of a process that consisted of (i) defining the studies used as a data source through a literature review; (ii) extracting data from these studies; (iii) translating this data into codes; (iv) translating the codes into themes; (v) creating the model of higher-order themes; and, (vi) assessing the trustworthiness of the synthesis. The resulting thematic network comprises four higher-level themes: Cohesion, Orientation, Shared Leadership, and Autonomy. We believe that the constructed thematic network can be generalized to ASD and used as the basis by researchers who intend to explore ASD Teamwork. Further, practitioners can use our results to understand agile teams' dynamics better and improve their efficiency.

show abstract

Agility is responsiveness to change

Cited by 24 publications

References 11 publications

Issues, challenges, and a proposed theoretical core of agile software development research

Issues, challenges, and a proposed theoretical core of agile software development research

Balancing between stability and change in Agile teams

Towards a Comprehensive Understanding of Agile Teamwork: A literature-based Thematic Network

Contact Info

Product

Resources

About