Amethodical systems development: the deferred meaning of systems development methods
By D. Truex, Richard L. Baskerville, J. Travis. 2000
366 citations recorded by the source corpus.
Subfields: Information Systems, Management Science and Operations Research, Sociology and Political Science
View Paper: https://www.semanticscholar.org/paper/29359407500c5b1f43afc222e94f9f587fe4722b
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Information Systems
- Rory V. O'Connor
- Paul M. Clarke
- Kalle J. Lyytinen
- Juhani Warsta
- Kateryna Kuksenok
- Outi Salo
- Pekka Abrahamsson
- Jussi Ronkainen
In Management Science and Operations Research
- Rory V. O'Connor
- Paul M. Clarke
- Kalle J. Lyytinen
- Kateryna Kuksenok
- Outi Salo
- Pekka Abrahamsson
- Mike Newman
In Sociology and Political Science
Citations in the corpus
- The situational factors that affect the software development process: Towards a comprehensive reference framework (2012, background): “This inter-relationship is considered to be representative of an amethodical process [65] rather than a methodical process, suggesting that software development processes are highly dynamic, that software development is an opportunistic process that needs to be adapted and tailored constantly during”
- Influence apart from Adoption: How Interaction between Programming and Scientific Practices Shapes Modes of Inquiry in Four Oceanography Teams (2016, background): “This is not done to claim that the marginalized coding approaches are any more common than the dominant, but to provide an alternative narrative that includes practices that do exist not as an outlier or aside, but the primary focus [64].”
- Agile Software Development Methods: Review and Analysis (2017, methodology): “rol or to provide a symbolic status.” The same study further claims that these methodologies are too mechanistic to be used in detail. Parnas and Clements (1986) have made similar arguments early on. Truex et al. (2000) take an extreme position and state that it is possible that traditional methods ”
- Explaining information systems change: a punctuated socio-technical change model (2008, methodology): “…system requirements by shifting normatively design activities from organizational requirements (organizational design options) to technical design (technical design options), and then implementing it into the organizational routine (Parnas & Clements, 1986; Lyytinen, 1987a; Truex et al ., 2000).”