The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.

Explaining software developer acceptance of methodologies: a comparison of five theoretical models

The work

AuthorsCynthia K. Riemenschneider; Bill C. Hardgrave; Fred D. Davis
Editors
Typearticle
Year2002
Citekeyriemenschneider2002explaining

Where it appeared

Published inIEEE Transactions on Software Engineering
PublisherIEEE Computer Society
Volume28
Issue12
Pages1135--1145

From OpenAlex, which stores abstracts as an index of words and their positions: what is shown is rebuilt from that, and reads fluently whether or not it is what the author wrote.

Abstract

Many organizations attempt to deploy methodologies intended to improve software development processes. However, resistance by individual software developers against using such methodologies often obstructs their successful deployment. To better explain why individual developers accept or resist methodologies, five theoretical models of individual intentions to accept information technology tools were examined. In a field study of 128 developers in a large organization that implemented a methodology, each model explained significant variance in developers' intentions to use the methodology. Similar to findings from the tool adoption context, we found that, if a methodology is not regarded as useful by developers, its prospects for successful deployment may be severely undermined. In contrast to the typical pattern of findings in a tool context, however, we found that methodology adoption intentions are driven by: 1) the presence of an organizational mandate to use the methodology, 2) the compatibility of the methodology with how developers perform their work, and 3) the opinions of developers' coworkers and supervisors toward using the methodology. Collectively, these results provide surprising new insights into why software developers accept or resist methodologies and suggest what software engineering managers might do to overcome developer resistance.

How it got here

How it got hereagent via openalex
Added2026-10-24 18:59 UTC
Not denied bya person 2026-10-29 17:12 UTC

Cite it as

@article{riemenschneider2002explaining,
  title        = {Explaining software developer acceptance of methodologies: a comparison of five theoretical models},
  author       = {Cynthia K. Riemenschneider and Bill C. Hardgrave and Fred D. Davis},
  year         = {2002},
  journal      = {IEEE Transactions on Software Engineering},
  publisher    = {IEEE Computer Society},
  volume       = {28},
  number       = {12},
  pages        = {1135--1145},
  doi          = {10.1109/tse.2002.1158287},
}

This record lives at https://refs.drheap.org/riemenschneider2002explaining/ and will keep doing so.