Software development projects are about change, yet change is problematic in any situation. Individuals resist change and software developers are no different than other organizational actors in this regard. This paper describes a case study which examines the changes to the IS development environment wrought by the introduction of a new software development methodology. One aspect of the new methodology involves the use of user stories in place of traditional requirements documentation. The findings of this longitudinal study illustrated that developers’ commitment to the use of user stories diminished greatly, ranging from initial commitment to skepticism, to virtual abandonment. In order to explain the underlying reasons for the reductio...
Purpose This paper aims to expose the behaviours through which modern professional people commonly ...
Research into organizations has concluded that organizational effectiveness is paradoxical (i.e., ef...
If software developers are to be taken as prototypes of the new knowledge worker, we need look no fu...
Software development projects are about change, yet change is problematic in any situation. Individu...
This paper reports on an in-depth case study of a large and strategic IT development project facing ...
Abstract Software process improvement (SPI) approaches have been designed to produce changes at many...
Software process improvement (SPI) approaches have been designed to produce changes at many levels, ...
Escalation is a common and costly problem among IT projects. Although the potential of de-escalation...
Literature and practice has agreed that commitment plays an important role in software process impro...
User stories are a simple and direct way of creating and managing software requirements. They are w...
This interpretive grounded theory (GT) study describes and analyses the experiences of information s...
Mitigating the risk due to requirement volatility requires that we treat this as a systemic problem ...
Escalating commitment refers to situations where decision makers tend to persist with failing course...
Escalation of commitment is common in many software projects. It stands for the situation where mana...
Software-based information systems must be developed and implemented as a part of business change. T...
Purpose This paper aims to expose the behaviours through which modern professional people commonly ...
Research into organizations has concluded that organizational effectiveness is paradoxical (i.e., ef...
If software developers are to be taken as prototypes of the new knowledge worker, we need look no fu...
Software development projects are about change, yet change is problematic in any situation. Individu...
This paper reports on an in-depth case study of a large and strategic IT development project facing ...
Abstract Software process improvement (SPI) approaches have been designed to produce changes at many...
Software process improvement (SPI) approaches have been designed to produce changes at many levels, ...
Escalation is a common and costly problem among IT projects. Although the potential of de-escalation...
Literature and practice has agreed that commitment plays an important role in software process impro...
User stories are a simple and direct way of creating and managing software requirements. They are w...
This interpretive grounded theory (GT) study describes and analyses the experiences of information s...
Mitigating the risk due to requirement volatility requires that we treat this as a systemic problem ...
Escalating commitment refers to situations where decision makers tend to persist with failing course...
Escalation of commitment is common in many software projects. It stands for the situation where mana...
Software-based information systems must be developed and implemented as a part of business change. T...
Purpose This paper aims to expose the behaviours through which modern professional people commonly ...
Research into organizations has concluded that organizational effectiveness is paradoxical (i.e., ef...
If software developers are to be taken as prototypes of the new knowledge worker, we need look no fu...