Exploring control tensions in is project portfolio management

Research output: Chapter in Book or Conference Publication/ProceedingConference Publicationpeer-review

3 Citations (Scopus)

Abstract

While the concept of control has been widely studied in information technology project management, and a plethora of mechanisms are commonly used to control information systems development (ISD) teams, very little research exists on the management, and particularly control, of IS project portfolios. Using exploratory case studies this research-in-progress seeks to contribute to practice by first using control theory as a lens to uncover a range of formal and informal control mechanisms used in IS projects and portfolios. Secondly, it will identify and categorise the tensions that exist between IS project and portfolio controls. Finally, it will uncover the implications of tensions between project and portfolio controls and their impact on the management of IS project portfolios. This work contributes to the advancement of control theory and provides new insights for theory and practice by integrating the study of tensions and control.

Original languageEnglish
Title of host publication35th International Conference on Information Systems "Building a Better World Through Information Systems", ICIS 2014
PublisherAssociation for Information Systems
ISBN (Print)9781634396943
Publication statusPublished - 2014
Event35th International Conference on Information Systems: Building a Better World Through Information Systems, ICIS 2014 - Auckland, New Zealand
Duration: 14 Dec 201417 Dec 2014

Conference

Conference35th International Conference on Information Systems: Building a Better World Through Information Systems, ICIS 2014
Country/TerritoryNew Zealand
CityAuckland
Period14/12/1417/12/14

Keywords

  • Formal control
  • Informal control
  • Project portfolio management
  • Tension

Fingerprint

Dive into the research topics of 'Exploring control tensions in is project portfolio management'. Together they form a unique fingerprint.

Cite this