 | 2009 |
|---|
| 44 |       | Donal J. Flynn,
Gary S. C. Pan,
Mark Keil,
Magnus Mähring:
De-escalating IT projects: the DMM model.
Commun. ACM 52(10): 131-134 (2009) |
| 2008 |
|---|
| 43 | | Mark Keil,
Lei Li,
Lars Mathiassen,
Guangzhi Zheng:
The influence of checklists and roles on software practitioner risk perception and decision-making.
Journal of Systems and Software 81(6): 908-919 (2008) |
| 2007 |
|---|
| 42 | | Stephen Du,
Mark Keil,
Lars Mathiassen,
Yide Shen,
Amrit Tiwana:
Attention-shaping tools, expertise, and perceived control in IT project risk assessment.
Decision Support Systems 43(1): 269-283 (2007) |
| 41 | | Mark Keil,
Ghi Paul Im,
Magnus Mähring:
Reporting bad news on software projects: the effects of culturally constituted views of face-saving.
Inf. Syst. J. 17(1): 59-87 (2007) |
| 2006 |
|---|
| 40 | | Mark Keil,
Lei Li,
Lars Mathiassen,
Guangzhi Zheng:
The Influence of Checklists and Roles on Software Practitioner Risk Perception and Decision-Making.
HICSS 2006 |
| 39 | | Stephen Du,
Mark Keil,
Lars Mathiassen,
Yide Shen,
Amrit Tiwana:
The Role of Perceived Control, Attention-Shaping, and Expertise in IT Project Risk Assessment.
HICSS 2006 |
| 38 | | Lynette Kvasny,
Mark Keil:
The challenges of redressing the digital divide: a tale of two US cities.
Inf. Syst. J. 16(1): 23-53 (2006) |
| 37 | | Mark Keil,
Amrit Tiwana:
Relative importance of evaluation criteria for enterprise systems: a conjoint study.
Inf. Syst. J. 16(3): 237-262 (2006) |
| 2005 |
|---|
| 36 |  | J. J. Hseih,
Mark Keil,
Arun Rai:
Understanding Digital Inequality.
ICIS 2005 |
| 35 | | Mark Keil,
Amrit Tiwana:
Beyond Cost: The Drivers of COTS Application Value.
IEEE Software 22(3): 64-69 (2005) |
| 2004 |
|---|
| 34 | | Amrit Tiwana,
Mark Keil:
The one-minute risk assessment tool.
Commun. ACM 47(11): 73-77 (2004) |
| 33 | | Linda Wallace,
Mark Keil:
Software project risks and their effect on outcomes.
Commun. ACM 47(4): 68-73 (2004) |
| 32 | | Mark Keil,
H. Jeff Smith,
Suzanne D. Pawlowski,
Leigh Jin:
'Why didn't somebody tell me?': climate, information asymmetry, and bad news about troubled projects.
DATA BASE 35(2): 65-84 (2004) |
| 31 | | Magnus Mähring,
Jonny Holmström,
Mark Keil,
Ramiro Montealegre:
Trojan actor-networks and swift translation: Bringing actor-network theory to IT project escalation studies.
IT & People 17(2): 210-238 (2004) |
| 2003 |
|---|
| 30 | | Mark Keil,
Garret W. Meader,
Lynette Kvasny:
Bridging the Digital Divide: The Story of the Free Internet Initiative in LaGrange, Georgia.
HICSS 2003: 140 |
| 29 | | G. Peter Zhang,
Mark Keil,
Arun Rai,
Joan Mann:
Predicting information technology project escalation: A neural network approach.
European Journal of Operational Research 146(1): 115-129 (2003) |
| 28 | | Michael Gallivan,
Mark Keil:
The user-developer communication process: a critical case study.
Inf. Syst. J. 13(1): 37-68 (2003) |
| 27 | | H. Jeff Smith,
Mark Keil:
The reluctance to report bad news on troubled software projects: a theoretical model.
Inf. Syst. J. 13(1): 69-96 (2003) |
| 2002 |
|---|
| 26 | | Mark Keil,
Amrit Tiwana,
Ashley A. Bush:
Reconciling user and project manager perceptions of IT project risk: a Delphi study.
Inf. Syst. J. 12(2): 103-120 (2002) |
| 2001 |
|---|
| 25 | | Andrew P. Snow,
Mark Keil:
The Challenges of Accurate Project Status Reporting.
HICSS 2001 |
| 24 | | Mark Keil,
Daniel Robey:
Blowing the whistle on troubled software projects.
Commun. ACM 44(4): 87-93 (2001) |
| 2000 |
|---|
| 23 | | Paul E. Cule,
Roy C. Schmidt,
Kalle Lyytinen,
Mark Keil:
Strategies for Heading Off is Project Failure.
IS Management 17(2): 1-9 (2000) |
| 22 | | Mark Keil,
David M. Mount,
Stephen K. Wismath:
Visibility Stabs and Depth-First Spiralling on Line Segments in Output Sensitive Time.
Int. J. Comput. Geometry Appl. 10(5): 535-552 (2000) |
| 21 | | Mark Keil,
Linda Wallace,
Daniel E. Turk,
Gayle Dixon-Randall,
Urban Nulden:
An investigation of risk perception and risk propensity on the decision to continue a software development project.
Journal of Systems and Software 53(2): 145-157 (2000) |
| 20 | | Mark Keil,
Bernard C. Y. Tan,
Kwok Kee Wei,
Timo Saarinen,
Virpi Kristiina Tuunainen,
Arjen Wassenaar:
A Cross-Cultural Study on Escalation of Commitment Behavior in Software Projects.
MIS Quarterly 24(2): (2000) |
| 19 | | Ramiro Montealegre,
Mark Keil:
De-escalating Information Technology Projects: Lessons from the Denver International Airport.
MIS Quarterly 24(3): (2000) |
| 18 | | Mark Keil,
Joan Mann,
Arun Rai:
Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models.
MIS Quarterly 24(4): (2000) |
| 1999 |
|---|
| 17 | | Mark Keil,
Ephraim R. McLean:
From the Editors.
DATA BASE 30(1): 4 (1999) |
| 16 | | Mark Keil,
Ephraim R. McLean:
From the Editors.
DATA BASE 30(2): 4 (1999) |
| 15 | | Mark Keil,
Ephraim R. McLean:
From the Editors.
DATA BASE 30(3&4): 4 (1999) |
| 1998 |
|---|
| 14 | | Mark Keil,
Paul E. Cule,
Kalle Lyytinen,
Roy C. Schmidt:
A Framework for Identifying Software Project Risks.
Commun. ACM 41(11): 76-83 (1998) |
| 13 | | Ephraim R. McLean,
Mark Keil:
From the Editors.
DATA BASE 29(1): 4 (1998) |
| 12 | | David Gefen,
Mark Keil:
The Impact of Developer Reponsiveness on Perceptions of Usefulness and Ease of Use: An Extension of the Technology Acceptance Model.
DATA BASE 29(2): 35-49 (1998) |
| 11 | | Mark Keil,
Ephraim R. McLean:
From the Editors.
DATA BASE 29(2): 4 (1998) |
| 10 | | Mark Keil,
Ephraim R. McLean:
From the Editors.
DATA BASE 29(3): 4 (1998) |
| 9 | | Mark Keil,
Ephraim R. McLean:
From the Editors.
DATA BASE 29(4): 4 (1998) |
| 1997 |
|---|
| 8 | | Mark Keil,
Joan Mann:
Understanding the Nature and Extent of IS Project Escalation: Results from a Survey of IS Audit and Control Professionals.
HICSS (3) 1997: 139-148 |
| 7 | | Mark Keil,
Daniel Robey:
Turning runaway software projects around: The de-escalation of commitment to failing courses of action.
ICIS 1997: 472-473 |
| 1995 |
|---|
| 6 | | Mark Keil,
Erran Carmel:
Customer-Development Links in Software Development.
Commun. ACM 38(5): 33-44 (1995) |
| 5 | | Mark Keil:
Pulling the Plug: Software Project Management and the Problem of Project Escalation.
MIS Quarterly 19(4): (1995) |
| 1994 |
|---|
| 4 | | Mark Keil,
Richard Mixon:
Understanding Runaway IT Projects: Preliminary Results from a Program of Research Based on Escalation Theory.
HICSS (3) 1994: 469-478 |
| 3 | | Mark Keil,
Gopal K. Kapur,
M. Lynne Markus,
James A. Willbern:
Managing IT Projects for Success: Reengineering or Better Project Management?
ICIS 1994: 486 |
| 1993 |
|---|
| 2 | | Mark Keil,
Richard Mixon:
Laboratory Studies of IS Failure as Escalating Commitment to a Failing Course of Action: Overcoming the Obstacles.
ICIS 1993: 382 |
| 1992 |
|---|
| 1 | | Laxmi Gewali,
Mark Keil,
Simeon C. Ntafos:
On covering orthogonal polygons with star-shaped polygons.
Inf. Sci. 65(1-2): 45-63 (1992) |
