Open Access. Powered by Scholars. Published by Universities.®

Business Commons

Open Access. Powered by Scholars. Published by Universities.®

2011

Selected Works

Management Information Systems

Case study

Articles 1 - 4 of 4

Full-Text Articles in Business

Escalation And De-Escalation Of Commitment To Information Systems Projects: Insights From An Approach-Avoidance Process Model, Gary Pan, Shan Ling Pan Sep 2011

Escalation And De-Escalation Of Commitment To Information Systems Projects: Insights From An Approach-Avoidance Process Model, Gary Pan, Shan Ling Pan

Gary PAN

We view escalation and de-escalation of commitment as processes involving recurring instances of approach-avoidance conflict. This paper outlines an approach-avoidance process model for describing and analyzing escalation and de-escalation of commitment in information systems projects. In the model, the sequential mapping of project events is integrated with a model of approach-avoidance conflict that identifies periods of gradual evolution at two separate levels of social analysis (project and work) that are punctuated by sudden, revolutionary periods of rapid change. By conceiving the processes of commitment escalation and de-escalation as sequences of events involving approach-avoidance conflicts, researchers may develop a deeper understanding …


Transition To Is Project De-Escalation: An Exploration Into Management Executive's Influence Tactics, Gary Shan Chi Pan, Shan Ling Pan Sep 2011

Transition To Is Project De-Escalation: An Exploration Into Management Executive's Influence Tactics, Gary Shan Chi Pan, Shan Ling Pan

Gary PAN

This paper seeks to understand the factors that shape management executives' influence behaviors and the influence tactics that may be utilized during de-escalation of commitment to information systems (IS) projects. De-escalation is potentially a more important issue than escalation because de-escalation provides remedies for the ills of escalation. Therefore, it is important to understand how project stakeholders' commitment to troubled IS projects may be transformed under management executives' influence, hence allowing project teams to carry out their de-escalation activities. Here, we adopt theories of leadership, politics, and interpersonal influence, as our lenses to examine the management executive's influence behaviors during …


Escalation And De-Escalation Of Commitment To Information Systems Projects: Insights From A Project Evaluation Model, Shan Ling Pan, Gary S. C. Pan, Michael Newman, Donal Flynn Sep 2011

Escalation And De-Escalation Of Commitment To Information Systems Projects: Insights From A Project Evaluation Model, Shan Ling Pan, Gary S. C. Pan, Michael Newman, Donal Flynn

Gary PAN

This paper outlines a project evaluation model for examining escalation and de-escalation of commitment to information systems projects. We view escalation and de-escalation of commitment as processes involving recurring instances of approach-avoidance conflict. In the model, the sequential mapping of project events is integrated with a model of approach-avoidance conflict that identifies periods of gradual evolution at two separate levels of social analysis (project and work) that are punctuated by sudden, revolutionary periods of rapid change. By conceiving the processes of commitment escalation and de-escalation as sequences of events involving approach-avoidance conflicts, researchers may develop a deeper understanding of how …


Cognitive Processes In Object-Oriented Requirements Engineering Practice: Analogical Reasoning And Mental Modelling, Linda Dawson Dec 2010

Cognitive Processes In Object-Oriented Requirements Engineering Practice: Analogical Reasoning And Mental Modelling, Linda Dawson

Associate Professor Linda Dawson

This paper presents a background in cognitive processes such as problem solving and analogical reasoning for considering modeling from an object-oriented perspective within the domain of requirements engineering. The paper then describes a research project and the findings from a set of four cases which examine professional practice from perspective of cognitive modeling for object-oriented requirements engineering. In these studies, it was found that the analysts routinely built models in their minds and refined them before committing them to paper or communicating these models to others. The studies also showed that objectoriented analysts depend on analogical reasoning where they use …