Understanding post-adoptive agile usage: An exploratory cross-case analysis

@article{Senapathi2011UnderstandingPA,
  title={Understanding post-adoptive agile usage: An exploratory cross-case analysis},
  author={Mali Senapathi and Ananth Srinivasan},
  journal={J. Syst. Softw.},
  year={2011},
  volume={85},
  pages={1255-1268}
}
The widespread adoption of agile methodologies raises the question of their continued and effective usage in organizations. An agile usage model consisting of innovation, sociological, technological, team, and organizational factors is used to inform an analysis of post-adoptive usage of agile practices in two major organizations. Analysis of the two case studies found that a methodology champion and top management support were the most important factors influencing continued usage, while… 

Figures and Tables from this paper

Agile Usage: Refining a Theoretical Model
TLDR
The objective of this study is to use multiple data collection methods to further evaluate and refine the AUM, and the final refined conceptual model of Agile Usage is presented along with implications for research and practice.
Organizational culture and the acceptance of agile methodology
TLDR
Three types of culture are noted; group culture, development culture and rational culture, promoting the acceptance of agile methodology so that the hierarchical hinders acceptance.
Understanding Agile Software Development Assimilation Beyond Acceptance
Agile software development methods represent a departure from the heavily regimented and document-driven procedures of traditional, waterfall approaches. Despite the highly touted benefits of
The amorphous nature of agile: no one size fits all
Purpose This paper aims to investigate the extent to which newly agile organizations followed 2001’s Agile Manifesto, especially in terms of the 12 principles of the agile approach, as
Widely Used but also Highly Valued? Acceptance Factors and Their Perceptions in Water-Scrum-Fall Projects
TLDR
The results indicate that, compared to traditional development methodologies, some aspects of Water-Scrum-Fall bring relative advantages and are more compatible to the way developers prefer to work, yet there also exist potential acceptance barriers such as a restricted individual autonomy and increased process complexity.
Hidden facilitators of agile transition: Agile coaches and agile champions
TLDR
Two hidden facilitators of Agile transition, Agile coaches and Agile champions, which rarely have been taken into consideration are presented and shown that considering these facilitators when can highly impress the success of the transition.
Fit between Agile practices and organizational cultures
TLDR
This paper proposes a theoretical framework that deals with an alternative way in which organizations identify their cultural types, and understand underlying principles of each Agile practice in order to form the fit between organizational culture and Agile.
Mindful revolution or mindless trend? Examining agile development as a management fashion
TLDR
In some cases that agile appears to be characterized as a short-term, transitory trend, while in others it is embedded in an organization’s processes and culture, which can encourage managerial awareness of the link between fashions and agile development.
Explaining Agility with a Process Theory of Change
TLDR
Viewing agility as a process theory helps address the research-practice gap by highlighting the need for skepticism of methods and practices, and by suggesting practically relevant research questions.
...
...

References

SHOWING 1-10 OF 38 REFERENCES
Agile Practices in Use from an Innovation Assimilation Perspective: A Multiple Case Study
TLDR
An exploratory study of the application of innovation theory to agile practices in use, focusing in particular on the later stages of assimilation i.e. acceptance, routinization and infusion indicates the period of agile use does not have a proportional effect on their assimilation stages.
AGILE SOFTWARE DEVELOPMENT: A SURVEY OF EARLY ADOPTERS
In the past few years, anecdotal evidence of mostly positive experiences with the implementation of agile development methods has emerged from case studies. We used a survey strategy, which enables
What Do We Know about Agile Software Development?
TLDR
To clarify the effectiveness of agile methods, the literature is reviewed and a systematic study of what the authors know empirically about its benefits and limitations is conducted.
‘Lots done, more to do’: the current state of agile systems development research
TLDR
Agile research has lagged behind practice, as is often the case with new and emerging phenomena in Information Systems Development (ISD).
Acceptance of software process innovations – the case of extreme programming
TLDR
This study study widely differing patterns of adherence to XP practices within an organization, and tease out the various issues and challenges posed by the adoption of XP.
Agile Software Development: The People Factor
TLDR
The effects of working in an agile style is described and the problem it addresses and the way in which it addresses the problem are introduced.
Post-implementation management of CASE methodology
TLDR
The implementation lifecycle of CASE methodology is reviewed and it is suggested that the post-implementation stage is the most critical for ensuring its successful use and incorporation within an organization.
Factors that Impact Implementing a System Development Methodology
TLDR
The study uses a survey instrument and an exploratory factor analysis to identify five factors important to implementing an SDM: organizational SDM transition, functional management involvement/support, SDM Transition, the use of models and external support.
Lean Software Management: BBC Worldwide Case Study
TLDR
The conclusion is that the performance of the software development team was improved by adopting a lean approach, and the faster delivery with a focus on creating the highest value to the customer also reduced both technical and market risks.
...
...