An Inventory of Personal Constructs for Information Systems Project Risk Researchers

Abstract

This paper explores the application of personal construct elicitation techniques to the identification of the situational factors that managers of bespoke information system development projects take into account when planning new projects for new customers. It is shown that the personal constructs elicited reflect most of the contingency variables and risk-drivers mentioned in the information systems development literature, but also include some situational characteristics not addressed in this literature. It is concluded that personal construct elicitation techniques have a valuable role to play in information systems development research.

The repertory grid technique: Its place in empirical software engineering research

“…Where an individual did not agree that a construct was an accurate representation of their construct the original one was reinstated. Following this process limited quantitative analysis was done in terms of frequency counting of the occurrences of the final constructs, and a ranked list was produced (see the data in [21]). …”

“…The analysis of these data sets focused around using simple manual frequency analysis of the constructs, and creating ranked listings (as in Moynihan's study [21,22]). It seems unlikely from the detail in the paper that grids were constructed.…”

“…The repertory grid has as its elements the eight distinct studies that were being investigated by the researchers (thus in essence these elements were supplied). The elements are: risks in third party software development projects [21,22], practitioner roles in SPI [2], successful software inspection process [13], excellent systems analysts [14][15][16][17], characteristics in system development team members [34], generic team traits v. software team roles [33] , ISD training and impacts on cognitive structure [20], identifying aspects in requirements [23].…”

“…Moynihan's exploratory study focused on using personal construct theory to identify the prevalent risks factors in software development projects which are undertaken for third parties [21,22]. His participants were 14 Irish software project managers.…”

“…Many of the studies reviewed in this paper are exploratory in nature, e.g. [14][15][16][17]21,22] and [34]. Moreover, those studies that are focused on behavioural or organisational aspects of the application of software engineering could also use the full repertory grid approach as a useful tool within a study.…”