2005
DOI: 10.4018/jdm.2005100102
|View full text |Cite
|
Sign up to set email alerts
|

On the Adaptation of an Agile Information Systems Development Method

Abstract: Little specific research has been conducted to date on the adaptation of agile information systems development (ISD) methods. This article presents the work practice in dealing with the adaptation of such a method in the ISD department of one of the leading financial institutes in Europe. Two forms of method adaptation, static adaptation and dynamic adaptation, are introduced and discussed in detail. We provide some insights plus an instrument that the ISD department studied uses to deal with the dynamic metho… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

1
31
0

Year Published

2007
2007
2019
2019

Publication Types

Select...
5
3

Relationship

1
7

Authors

Journals

citations
Cited by 35 publications
(34 citation statements)
references
References 0 publications
1
31
0
Order By: Relevance
“…Furthermore, there is evidence to suggest that this lack of cumulative reflection on past research is continuing. For example, in the new body of agile method research, there are many studies documenting how agile methods have been tailored, fragmented, and even combined (e.g., Fitzgerald et al 2006, Aydin et al 2004, Bowers et al 2002, Cao et al 2004, Fenwick 2003). Yet rather than taking the new method variant forward, subsequent researchers inevitably return to "base camp" and relay yet another account of how the original textbook version was tailored or customized.…”
Section: Problem Statementmentioning
confidence: 99%
“…Furthermore, there is evidence to suggest that this lack of cumulative reflection on past research is continuing. For example, in the new body of agile method research, there are many studies documenting how agile methods have been tailored, fragmented, and even combined (e.g., Fitzgerald et al 2006, Aydin et al 2004, Bowers et al 2002, Cao et al 2004, Fenwick 2003). Yet rather than taking the new method variant forward, subsequent researchers inevitably return to "base camp" and relay yet another account of how the original textbook version was tailored or customized.…”
Section: Problem Statementmentioning
confidence: 99%
“…The principle is to delivery specific requirements using fast, creative and flexible methods in an approach popularised by the Agile Software development approach (Aydin et al, 2005;Kurian, 2006;Nerur, 2007) and adopted by various communications companies such as Sabre, Sprint, Nortel, Symantec, Fidelity, Borland and Qwest (Holler, 2006). This is against the introduction of newer systems every three to five years.…”
Section: Discussionmentioning
confidence: 99%
“…SMD is a sub-subject of method development and refers to this adaptation process of method development. It is this process or ability through which (human and non-human) agents determine a system development approach for a specific project situation through responsive changes in, and dynamic interplays between, contexts, intentions, and method fragments [4]. SMD especially employs the input of the analysis and provides the output for the assembly, rather than focuses on method analysis or assembly of method fragments per se.…”
Section: Existing Review Studies and Approaches For MDmentioning
confidence: 99%
“…The key issue of situational method development is not exclusive focus on the analysis or the assembly, it is how method fragments, context, and method stakeholders are adapted to each other in a project situation. Thus, what lies at heart of SME is method adaptation [4].…”
Section: Existing Review Studies and Approaches For MDmentioning
confidence: 99%