Author List: Harris, Michael L.; Collins, Rosann Webb; Hevner, Alan R.;
Information Systems Research, 2009, Volume 20, Issue 3, Page 400-419.
When should software development teams have the flexibility to modify their directions and how do we balance that flexibility with controls essential to produce acceptable outcomes? We use dynamic capabilities theory and an extension of control theory to understand these questions. This work is examined in a case study. Our results demonstrate that flexibility may be needed when the starting conditions are uncertain and that effective control in these situations requires use of traditional controls plus a new type of control we term emergent outcome control.
Keywords: agile development; control theory; emergent outcome control; flexible development; uncertainty
Algorithm:

List of Topics

#280 0.282 control controls formal systems mechanisms modes clan informal used internal literature outsourced outcome theory configuration attempts evolution authority complementary little
#54 0.168 approach conditions organizational actions emergence dynamics traditional theoretical emergent consequences developments case suggest make organization point outcomes recent trajectory claims
#165 0.112 uncertainty contingency integration environmental theory data fit key using model flexibility perspective environment perspectives high conditions processing examine issue uncertain
#209 0.108 results study research information studies relationship size variables previous variable examining dependent increases empirical variance accounting independent demonstrate important addition
#90 0.104 development life cycle prototyping new stages routines stage design experiences traditional time sdlc suggested strategies rapid effort integrated needs techniques
#152 0.101 software development process performance agile processes developers response tailoring activities specific requirements teams quality improvement outcomes productivity improve fit maturity
#174 0.062 use support information effective behaviors work usage examine extent users expertise uses longitudinal focus routine revealed volume constructs contributes operations