Toward a Theory of Information System Development Success: Perceptions of Software Development Team Members
Zelazny, Lucian M.
MetadataShow full item record
This dissertation increases our understanding of information system project success by investigating how software development team members define the success of an information system development effort. The theoretical model of ISD success is developed and tested. ISD success is measured through the eyes of the software development team membersâ since they are the most influential stakeholders during the development of the system. This dissertation was conducted in two phases: 1) theory building and 2) theory testing. The theory building phase began with a thorough literature review. Semi-structured interviews were conducted and the data analyzed to add emergent concepts to the model. The result of the theory building phase is the theoretical model of ISD success. The theory testing stage began with the development and validation of a survey instrument to measure the constructs and subconstructs found within the theoretical model of ISD success. Data was collected and the model tested using partial least squares regression. The findings indicate that software development team members view ISD success as being composed of process quality, functional product quality, non-functional product quality, team member benefits, and team member satisfaction. Team member satisfaction is highly influenced by team member benefits, moderately influenced by functional product quality and slightly influence by non-functional product quality and process quality. Software development team members view process quality as being composed of within budget and process maturity; non-functional product as being composed of reliability, usability, testability, and efficiency; team member benefits as being composed of learning and teamwork; and team member satisfaction as being composed of product satisfaction, process satisfaction, and personal satisfaction. Software development team members do not view on time as a significant contributor to their definition of process quality; they do not view modifiability, portability, or reusability as significant contributors to their definition of non-functional product quality; and they do not view recognition as a significant contributor to team member benefits.
- Doctoral Dissertations