Pilot implementation

Learning from field tests in IS development

Morten Hertzum, Jørgen P. Bansler, Erling C. Havn, Jesper Simonsen

Publikation: Bidrag til tidsskriftTidsskriftartikelForskningpeer review

Resumé

A recurrent problem in information-systems development (ISD) is that many design shortcomings are not detected during development, but first after the system has been delivered and implemented in its intended environment. Pilot implementations appear to promise a way to extend prototyping from the laboratory to the field, thereby allowing users to experience a system design under realistic conditions and developers to get feedback from realistic use while the design is still malleable. We characterize pilot implementation, contrast it with prototyping, propose a five-element model of pilot implementation, and provide three empirical illustrations of our model. We conclude that pilot implementation has much merit as an ISD technique when system performance is contingent on context. But we also warn developers that, despite their seductive conceptual simplicity, pilot implementations can be difficult to plan and conduct. It is sometimes assumed that pilot implementations are less complicated and risky than ordinary implementations. Pilot implementations are, however, neither prototyping nor small-scale versions of full-scale implementations; they are fundamentally different and have their own challenges, which will be enumerated and discussed in this article.
OriginalsprogEngelsk
TidsskriftCommunications of the Association for Information Systems
Vol/bind30
Udgave nummer1
Sider (fra-til)313-328
Antal sider16
ISSN1529-3181
DOI
StatusUdgivet - maj 2012

Emneord

  • pilot implementation
  • pilot system
  • information systems development
  • prototyping
  • socio-technical change

Citer dette

Hertzum, Morten ; Bansler, Jørgen P. ; Havn, Erling C. ; Simonsen, Jesper. / Pilot implementation : Learning from field tests in IS development. I: Communications of the Association for Information Systems. 2012 ; Bind 30, Nr. 1. s. 313-328.
@article{1f0eeae9287d4bf089a7ca67cafc1421,
title = "Pilot implementation: Learning from field tests in IS development",
abstract = "A recurrent problem in information-systems development (ISD) is that many design shortcomings are not detected during development, but first after the system has been delivered and implemented in its intended environment. Pilot implementations appear to promise a way to extend prototyping from the laboratory to the field, thereby allowing users to experience a system design under realistic conditions and developers to get feedback from realistic use while the design is still malleable. We characterize pilot implementation, contrast it with prototyping, propose a five-element model of pilot implementation and provide three empirical illustrations of our model. We conclude that pilot implementation has much merit as an ISD technique when system performance is contingent on context. But we also warn developers that, despite their seductive conceptual simplicity, pilot implementations can be difficult to plan and conduct. It is sometimes assumed that pilot implementations are less complicated and risky than ordinary implementations. Pilot implementations are, however, neither prototyping nor small-scale versions of full-scale implementations; they are fundamentally different and have their own challenges, which will be enumerated and discussed in this article.",
keywords = "pilot implementation, pilot system, information systems development, prototyping, socio-technical change",
author = "Morten Hertzum and Bansler, {J{\o}rgen P.} and Havn, {Erling C.} and Jesper Simonsen",
year = "2012",
month = "5",
doi = "10.17705/1CAIS.03020",
language = "English",
volume = "30",
pages = "313--328",
journal = "Communications of the Association for Information Systems",
issn = "1529-3181",
publisher = "Association for Information Systems",
number = "1",

}

Pilot implementation : Learning from field tests in IS development. / Hertzum, Morten; Bansler, Jørgen P.; Havn, Erling C.; Simonsen, Jesper.

I: Communications of the Association for Information Systems, Bind 30, Nr. 1, 05.2012, s. 313-328.

Publikation: Bidrag til tidsskriftTidsskriftartikelForskningpeer review

TY - JOUR

T1 - Pilot implementation

T2 - Learning from field tests in IS development

AU - Hertzum, Morten

AU - Bansler, Jørgen P.

AU - Havn, Erling C.

AU - Simonsen, Jesper

PY - 2012/5

Y1 - 2012/5

N2 - A recurrent problem in information-systems development (ISD) is that many design shortcomings are not detected during development, but first after the system has been delivered and implemented in its intended environment. Pilot implementations appear to promise a way to extend prototyping from the laboratory to the field, thereby allowing users to experience a system design under realistic conditions and developers to get feedback from realistic use while the design is still malleable. We characterize pilot implementation, contrast it with prototyping, propose a five-element model of pilot implementation and provide three empirical illustrations of our model. We conclude that pilot implementation has much merit as an ISD technique when system performance is contingent on context. But we also warn developers that, despite their seductive conceptual simplicity, pilot implementations can be difficult to plan and conduct. It is sometimes assumed that pilot implementations are less complicated and risky than ordinary implementations. Pilot implementations are, however, neither prototyping nor small-scale versions of full-scale implementations; they are fundamentally different and have their own challenges, which will be enumerated and discussed in this article.

AB - A recurrent problem in information-systems development (ISD) is that many design shortcomings are not detected during development, but first after the system has been delivered and implemented in its intended environment. Pilot implementations appear to promise a way to extend prototyping from the laboratory to the field, thereby allowing users to experience a system design under realistic conditions and developers to get feedback from realistic use while the design is still malleable. We characterize pilot implementation, contrast it with prototyping, propose a five-element model of pilot implementation and provide three empirical illustrations of our model. We conclude that pilot implementation has much merit as an ISD technique when system performance is contingent on context. But we also warn developers that, despite their seductive conceptual simplicity, pilot implementations can be difficult to plan and conduct. It is sometimes assumed that pilot implementations are less complicated and risky than ordinary implementations. Pilot implementations are, however, neither prototyping nor small-scale versions of full-scale implementations; they are fundamentally different and have their own challenges, which will be enumerated and discussed in this article.

KW - pilot implementation

KW - pilot system

KW - information systems development

KW - prototyping

KW - socio-technical change

U2 - 10.17705/1CAIS.03020

DO - 10.17705/1CAIS.03020

M3 - Journal article

VL - 30

SP - 313

EP - 328

JO - Communications of the Association for Information Systems

JF - Communications of the Association for Information Systems

SN - 1529-3181

IS - 1

ER -