TY - GEN
T1 - A Case Study of Risk Management in Agile Systems Development
AU - Conboy, Kieran
PY - 2009/6/1
Y1 - 2009/6/1
N2 - A principal objective of agile development methods is to reduce risk thereby resulting in more successful and effective information systems. However, while there is an extensive body of academic literature on risk management, very little research has attempted to rigorously apply this as a lens to study risk management in agile development projects. The purpose of this research was to ascertain the extent to which risk management practices are incorporated into agile development projects. A case study was conducted involving a change management consultancy firm whose main business involved the deployment of agile approaches. The study found that while there is a perception that risk management practices are not carried out in agile environments, the extent to which risk management is conducted on these projects is in some cases just as substantial to that carried out on traditional projects. In fact, in this case it appeared that the teams were more rigorous in their risk management than is often the case.
AB - A principal objective of agile development methods is to reduce risk thereby resulting in more successful and effective information systems. However, while there is an extensive body of academic literature on risk management, very little research has attempted to rigorously apply this as a lens to study risk management in agile development projects. The purpose of this research was to ascertain the extent to which risk management practices are incorporated into agile development projects. A case study was conducted involving a change management consultancy firm whose main business involved the deployment of agile approaches. The study found that while there is a perception that risk management practices are not carried out in agile environments, the extent to which risk management is conducted on these projects is in some cases just as substantial to that carried out on traditional projects. In fact, in this case it appeared that the teams were more rigorous in their risk management than is often the case.
UR - https://www.scopus.com/pages/publications/84870695190
M3 - Conference Publication
SN - 9788861293915
T3 - 17th European Conference on Information Systems, ECIS 2009
BT - 17th European Conference on Information Systems
CY - Verona, Italy
T2 - 17th European Conference on Information Systems, ECIS 2009
Y2 - 8 June 2009 through 10 June 2009
ER -