The SCEAS System
Navigation Menu

Search the dblp DataBase

Title:
Author:

Mark Keil: [Publications] [Author Rank by year] [Co-authors] [Prefers] [Cites] [Cited by]

Publications of Author

  1. Stephen Du, Mark Keil, Lars Mathiassen, Yide Shen, Amrit Tiwana
    The Role of Perceived Control, Attention-Shaping, and Expertise in IT Project Risk Assessment. [Citation Graph (0, 0)][DBLP]
    HICSS, 2006, pp:- [Conf]
  2. Mark Keil, Lei Li, Lars Mathiassen, Guangzhi Zheng
    The Influence of Checklists and Roles on Software Practitioner Risk Perception and Decision-Making. [Citation Graph (0, 0)][DBLP]
    HICSS, 2006, pp:- [Conf]
  3. Mark Keil, Richard Mixon
    Understanding Runaway IT Projects: Preliminary Results from a Program of Research Based on Escalation Theory. [Citation Graph (0, 0)][DBLP]
    HICSS (3), 1994, pp:469-478 [Conf]
  4. Mark Keil, Joan Mann
    Understanding the Nature and Extent of IS Project Escalation: Results from a Survey of IS Audit and Control Professionals. [Citation Graph (0, 0)][DBLP]
    HICSS (3), 1997, pp:139-148 [Conf]
  5. Mark Keil, Garret W. Meader, Lynette Kvasny
    Bridging the Digital Divide: The Story of the Free Internet Initiative in LaGrange, Georgia. [Citation Graph (0, 0)][DBLP]
    HICSS, 2003, pp:140- [Conf]
  6. Andrew P. Snow, Mark Keil
    The Challenges of Accurate Project Status Reporting. [Citation Graph (0, 0)][DBLP]
    HICSS, 2001, pp:- [Conf]
  7. J. J. Hseih, Mark Keil, Arun Rai
    Understanding Digital Inequality. [Citation Graph (0, 0)][DBLP]
    ICIS, 2005, pp:- [Conf]
  8. Mark Keil, Richard Mixon
    Laboratory Studies of IS Failure as Escalating Commitment to a Failing Course of Action: Overcoming the Obstacles. [Citation Graph (0, 0)][DBLP]
    ICIS, 1993, pp:382- [Conf]
  9. Mark Keil, Daniel Robey
    Turning runaway software projects around: The de-escalation of commitment to failing courses of action. [Citation Graph (0, 0)][DBLP]
    ICIS, 1997, pp:472-473 [Conf]
  10. Mark Keil, Gopal K. Kapur, M. Lynne Markus, James A. Willbern
    Managing IT Projects for Success: Reengineering or Better Project Management? [Citation Graph (0, 0)][DBLP]
    ICIS, 1994, pp:486- [Conf]
  11. Mark Keil, Erran Carmel
    Customer-Development Links in Software Development. [Citation Graph (0, 0)][DBLP]
    Commun. ACM, 1995, v:38, n:5, pp:33-44 [Journal]
  12. Mark Keil, Paul E. Cule, Kalle Lyytinen, Roy C. Schmidt
    A Framework for Identifying Software Project Risks. [Citation Graph (0, 0)][DBLP]
    Commun. ACM, 1998, v:41, n:11, pp:76-83 [Journal]
  13. Mark Keil, Daniel Robey
    Blowing the whistle on troubled software projects. [Citation Graph (0, 0)][DBLP]
    Commun. ACM, 2001, v:44, n:4, pp:87-93 [Journal]
  14. Amrit Tiwana, Mark Keil
    The one-minute risk assessment tool. [Citation Graph (0, 0)][DBLP]
    Commun. ACM, 2004, v:47, n:11, pp:73-77 [Journal]
  15. Linda Wallace, Mark Keil
    Software project risks and their effect on outcomes. [Citation Graph (0, 0)][DBLP]
    Commun. ACM, 2004, v:47, n:4, pp:68-73 [Journal]
  16. David Gefen, Mark Keil
    The Impact of Developer Reponsiveness on Perceptions of Usefulness and Ease of Use: An Extension of the Technology Acceptance Model. [Citation Graph (0, 0)][DBLP]
    DATA BASE, 1998, v:29, n:2, pp:35-49 [Journal]
  17. Mark Keil, Ephraim R. McLean
    From the Editors. [Citation Graph (0, 0)][DBLP]
    DATA BASE, 1998, v:29, n:2, pp:4- [Journal]
  18. Mark Keil, Ephraim R. McLean
    From the Editors. [Citation Graph (0, 0)][DBLP]
    DATA BASE, 1998, v:29, n:3, pp:4- [Journal]
  19. Mark Keil, Ephraim R. McLean
    From the Editors. [Citation Graph (0, 0)][DBLP]
    DATA BASE, 1998, v:29, n:4, pp:4- [Journal]
  20. Mark Keil, Ephraim R. McLean
    From the Editors. [Citation Graph (0, 0)][DBLP]
    DATA BASE, 1999, v:30, n:1, pp:4- [Journal]
  21. Mark Keil, Ephraim R. McLean
    From the Editors. [Citation Graph (0, 0)][DBLP]
    DATA BASE, 1999, v:30, n:2, pp:4- [Journal]
  22. Mark Keil, Ephraim R. McLean
    From the Editors. [Citation Graph (0, 0)][DBLP]
    DATA BASE, 1999, v:30, n:3&4, pp:4- [Journal]
  23. Ephraim R. McLean, Mark Keil
    From the Editors. [Citation Graph (0, 0)][DBLP]
    DATA BASE, 1998, v:29, n:1, pp:4- [Journal]
  24. Stephen Du, Mark Keil, Lars Mathiassen, Yide Shen, Amrit Tiwana
    Attention-shaping tools, expertise, and perceived control in IT project risk assessment. [Citation Graph (0, 0)][DBLP]
    Decision Support Systems, 2007, v:43, n:1, pp:269-283 [Journal]
  25. Mark Keil, David M. Mount, Stephen K. Wismath
    Visibility Stabs and Depth-First Spiralling on Line Segments in Output Sensitive Time. [Citation Graph (0, 0)][DBLP]
    Int. J. Comput. Geometry Appl., 2000, v:10, n:5, pp:535-552 [Journal]
  26. Laxmi Gewali, Mark Keil, Simeon C. Ntafos
    On covering orthogonal polygons with star-shaped polygons. [Citation Graph (0, 0)][DBLP]
    Inf. Sci., 1992, v:65, n:1-2, pp:45-63 [Journal]
  27. Mark Keil, Amrit Tiwana, Ashley Bush
    Reconciling user and project manager perceptions of IT project risk: a Delphi study. [Citation Graph (0, 0)][DBLP]
    Inf. Syst. J., 2002, v:12, n:2, pp:103-120 [Journal]
  28. H. Jeff Smith, Mark Keil
    The reluctance to report bad news on troubled software projects: a theoretical model. [Citation Graph (0, 0)][DBLP]
    Inf. Syst. J., 2003, v:13, n:1, pp:69-96 [Journal]
  29. Michael Gallivan, Mark Keil
    The user-developer communication process: a critical case study. [Citation Graph (0, 0)][DBLP]
    Inf. Syst. J., 2003, v:13, n:1, pp:37-68 [Journal]
  30. 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. [Citation Graph (0, 0)][DBLP]
    Journal of Systems and Software, 2000, v:53, n:2, pp:145-157 [Journal]
  31. Mark Keil, Joan Mann, Arun Rai
    Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models. [Citation Graph (0, 0)][DBLP]
    MIS Quarterly, 2000, v:24, n:4, pp:- [Journal]
  32. 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. [Citation Graph (0, 0)][DBLP]
    MIS Quarterly, 2000, v:24, n:2, pp:- [Journal]
  33. Mark Keil
    Pulling the Plug: Software Project Management and the Problem of Project Escalation. [Citation Graph (0, 0)][DBLP]
    MIS Quarterly, 1995, v:19, n:4, pp:- [Journal]
  34. Ramiro Montealegre, Mark Keil
    De-escalating Information Technology Projects: Lessons from the Denver International Airport. [Citation Graph (0, 0)][DBLP]
    MIS Quarterly, 2000, v:24, n:3, pp:- [Journal]
  35. Sergei Bespamyatnikh, Binay K. Bhattacharya, Mark Keil, J. David Kirkpatrick, Michael Segal
    Efficient algorithms for centers and medians in interval and circular-arc graphs. [Citation Graph (0, 0)][DBLP]
    Networks, 2002, v:39, n:3, pp:144-152 [Journal]
  36. Mark Keil, Amrit Tiwana
    Beyond Cost: The Drivers of COTS Application Value. [Citation Graph (0, 0)][DBLP]
    IEEE Software, 2005, v:22, n:3, pp:64-69 [Journal]
  37. G. Peter Zhang, Mark Keil, Arun Rai, Joan Mann
    Predicting information technology project escalation: A neural network approach. [Citation Graph (0, 0)][DBLP]
    European Journal of Operational Research, 2003, v:146, n:1, pp:115-129 [Journal]

  38. De-escalating IT projects: the DMM model. [Citation Graph (, )][DBLP]


  39. 'Why didn't somebody tell me?': climate, information asymmetry, and bad news about troubled projects. [Citation Graph (, )][DBLP]


Search in 0.003secs, Finished in 0.004secs
NOTICE1
System may not be available sometimes or not working properly, since it is still in development with continuous upgrades
NOTICE2
The rankings that are presented on this page should NOT be considered as formal since the citation info is incomplete in DBLP
 
System created by asidirop@csd.auth.gr [http://users.auth.gr/~asidirop/] © 2002
for Data Engineering Laboratory, Department of Informatics, Aristotle University © 2002