2020
DOI: 10.17705/1jais.00623
|View full text |Cite
|
Sign up to set email alerts
|

How Much Method-in-Use Matters? A Case Study of Agile and Waterfall Software Projects

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
8
0
1

Year Published

2021
2021
2024
2024

Publication Types

Select...
6
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 15 publications
(15 citation statements)
references
References 57 publications
0
8
0
1
Order By: Relevance
“…SDMs significantly inform and shape the cognitions and actions of organisational members engaged in ISD (Hirschheim & Klein, 1989), and technical artefacts such as an SDM can act as a carrier and an important institutional embodiment serving to preserve rules by constraining the actions of human actors (Gosain, 2004). SDMs are often not used in the manner intended by method developers; in practice, SDMs are often adapted and modified to meet organisational and project exigencies (Päivärinta, Sein, & Peltola, 2010); but Thummadi and Lyytinen (2020) reinforce that research on SDMs remains current. Despite general agreement concerning the importance of understanding the systems developer‐client relationship (Majchrzak, Beath, Lim, & Chin, 2005; Markus & Bjørn‐Andersen, 1987; Milne & Maiden, 2012; Siadati et al, 2019), there has only been limited research exploring the role that SDMs can play in influencing this relationship.…”
Section: Introductionmentioning
confidence: 99%
“…SDMs significantly inform and shape the cognitions and actions of organisational members engaged in ISD (Hirschheim & Klein, 1989), and technical artefacts such as an SDM can act as a carrier and an important institutional embodiment serving to preserve rules by constraining the actions of human actors (Gosain, 2004). SDMs are often not used in the manner intended by method developers; in practice, SDMs are often adapted and modified to meet organisational and project exigencies (Päivärinta, Sein, & Peltola, 2010); but Thummadi and Lyytinen (2020) reinforce that research on SDMs remains current. Despite general agreement concerning the importance of understanding the systems developer‐client relationship (Majchrzak, Beath, Lim, & Chin, 2005; Markus & Bjørn‐Andersen, 1987; Milne & Maiden, 2012; Siadati et al, 2019), there has only been limited research exploring the role that SDMs can play in influencing this relationship.…”
Section: Introductionmentioning
confidence: 99%
“…So, each stage should not be done simultaneously. Thus, the difference between the waterfall method and the agile method lies in the SDLC stage [8,9]. This model also includes software development that is somewhat less iterative and flexible.…”
Section: Background and Analysismentioning
confidence: 99%
“…Almeida and Simões (2019) implicitly positioned an argument on how difficult it can be for organisations to select one methodology over the other, and that there were only a few case studies as at the time of their study. Also, little is known about the extent to which any of the methodologies truly influences software design and its outcomes (Thummadi & Lyytinen, 2020). A question that that came out of Heeager and Nielsen (2018) that doesn't seems to have been empirically answered is whether certain software are better developed using a specific methodology rather than the other.…”
Section: Problematisation and Motivationmentioning
confidence: 99%
“…Literature has tries to address the differences between Agile and Waterfall methodologies but from cost, quality, and productivity perspectives (Thummadi & Lyytinen, 2020). Even though there are few areas of agreement among authors, the debate continues.…”
Section: Problematisation and Motivationmentioning
confidence: 99%