Article

The relation of requirements uncertainty and stakeholder perception gaps to project management performance

Department of Information Management, Department of Management Information Systems, University of Central Florida, Orlando, FL 32816-1400, United States; University of Colorado, College of Business and Administration, P.O. Box 7150, Colorado Springs, CO 80933-7150, United States; Department of Information Management, National Sun Yet-Sen University, 70, Lienhai Rd., Gushan District, Kaohsiung 804, Taiwan
Journal of Systems and Software 01/2009; DOI: 10.1016/j.jss.2008.11.833
Source: DBLP

ABSTRACT Researchers consider requirements uncertainty as a problem to be addressed during information system development by choosing an appropriate strategy to mitigate the uncertainty. However, this strategy avoids addressing issues present at the start of a project. Those include differences in perception between two prominent stakeholders: users and developers. The problems caused by this perception gap are demonstrated to be at least as significant as components of requirements uncertainty. A model is developed and empirically tested that shows a good portion of residual performance risks in a project are explained by perception gaps. These gaps present a new opportunity to address difficulties in a project before the development efforts begin.

0 Bookmarks
 · 
68 Views
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Derived from engineering, adherence to planning (ATP) is the central and most often used criterion for the evaluation of information system (IS) projects. Although this evaluation is questionable as ATP does not account for all of IS projects' particularities, a systematic approach for the assessment of ATP's suitability in the context of IS projects is still missing. We propose a theory to explain the suitability of using ATP as success criterion for IS projects. Thereby, we use the project life cycle's processes and their outcomes as the theory's primary constructs. We argue for the constructs' interdependencies corroborated by a systematic literature review. Our results show that ATP's suitability is not given or at least questionable in many cases. Researchers and managers should adapt the way of evaluating IS projects to avoid misleading implications.
    12/2011;
  • [Show abstract] [Hide abstract]
    ABSTRACT: It is frequently mentioned in the literature that Information Systems (IS) projects and programmes fail because of the involved complexity. However, we have a lack of understanding about the components of complexity and the specific constituting constructs (e.g., variety). This paper addresses this theoretical gap through a systematic literature review of IS project management literature based upon the application of Xia and Lee (2005)’s framework of IS project complexity. We contribute to this framework in multiple ways. First, we provide a state-of-the-art review of literature that builds upon Xia and Lee (2005)’s study and do not only find support for the previously identified components of complexity, but also identify multiple other relevant components to be potentially considered in future empirical studies. Second, we contribute to the framework by examining the differences between IS projects and programmes in terms of the relevance of individual complexity components. Finally, an important conceptual contribution of this paper is to aggregate the various identified complexity components into four distinct constructs of complexity, i.e., variety, interdependency, uncertainty, and ambiguity. Our extended conceptualization of IS project and programme complexity provides a useful guide for future empirical research, which is needed to understand why IS projects and programmes fail.
    European Conference on Information Systems (ECIS) 2013; 06/2013
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Independently from which software process was selected for a company or a project, the selected software process usually cannot be applied without any customization. Although the need to tailor a software process to specific project require-ments seems to be widely accepted and unquestioned, the way of doing the tailoring remains unclear and is, therefore, often left to the expertise of process engineers or project managers. What are the criteria to be applied in the tailor-ing? What are dependencies between different criteria and how should certain criteria influence the software process? In this paper we investigate concrete tailoring criteria for the tailoring of software processes. To this end, we present a collection of 49 tailoring criteria as the outcomes of a sys-tematic literature review. We further analyze the impact of the discovered tailoring criteria by relating them to a set of 20 exemplary tailoring actions, which affect the project-specific software process. Our outcomes show that the fac-tors influencing the tailoring are well understood, however, the consequences of the criteria remain abstract and need to be interpreted on a project-per-project basis.
    International Conference on Software and Systems Process (ICSSP 2013); 05/2013

Full-text (2 Sources)

View
4 Downloads
Available from
Jun 4, 2014