메뉴 건너뛰기




Volumn 83, Issue 11, 2010, Pages 2175-2187

Software engineering projects may fail before they are started: Post-mortem analysis of five cancelled projects

Author keywords

Customer; Post mortem analysis; Project cancellation; Project failure; Software engineering; Supplier

Indexed keywords

CUSTOMER; POSTMORTEM ANALYSIS; PROJECT CANCELLATION; PROJECT FAILURES; SUPPLIER;

EID: 77957326008     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.jss.2010.06.023     Document Type: Article
Times cited : (44)

References (36)
  • 3
    • 0036575888 scopus 로고    scopus 로고
    • Postmortem: Never leave a project without it
    • A. Birk, T. Dingsøyr, and T. Stlhane Postmortem: never leave a project without it IEEE Software 19 3 2002 43 45
    • (2002) IEEE Software , vol.19 , Issue.3 , pp. 43-45
    • Birk, A.1    Dingsøyr, T.2    Stlhane, T.3
  • 5
    • 25444497494 scopus 로고    scopus 로고
    • Why software fails?
    • R.N. Charette Why software fails? IEEE Spectrum 42 September (9) 2005 42 49
    • (2005) IEEE Spectrum , vol.42 , Issue.SEPTEMBER 9 , pp. 42-49
    • Charette, R.N.1
  • 6
    • 67649103417 scopus 로고    scopus 로고
    • Exhuming IT projects from their graves: An analysis of eight failure cases and their risk factors
    • A.Y.K. Chua Exhuming IT projects from their graves: an analysis of eight failure cases and their risk factors Journal of Computer Information Systems 2009 31 39 Spring
    • (2009) Journal of Computer Information Systems , pp. 31-39
    • Chua, A.Y.K.1
  • 7
    • 0030190827 scopus 로고    scopus 로고
    • A defined process for project postmortem review
    • B. Collier, T. DeMarco, and P. Fearey A defined process for project postmortem review IEEE Software 13 4 1996 65 72
    • (1996) IEEE Software , vol.13 , Issue.4 , pp. 65-72
    • Collier, B.1    Demarco, T.2    Fearey, P.3
  • 9
    • 33846842411 scopus 로고    scopus 로고
    • Tying the pieces together: A normative framework for integrating sales and project operations
    • M.J. Cooper, and C.S. Budd Tying the pieces together: a normative framework for integrating sales and project operations Industrial Marketing Management 36 2 2007 173 182
    • (2007) Industrial Marketing Management , vol.36 , Issue.2 , pp. 173-182
    • Cooper, M.J.1    Budd, C.S.2
  • 10
    • 0040270463 scopus 로고
    • Learning from abandoned information systems development projects
    • K. Ewusi-Mensah, and Z.H. Przasnyski Learning from abandoned information systems development projects Journal of Information Systems 10 1 1995 3 13
    • (1995) Journal of Information Systems , vol.10 , Issue.1 , pp. 3-13
    • Ewusi-Mensah, K.1    Przasnyski, Z.H.2
  • 12
    • 44949276584 scopus 로고
    • To start or to start-up? That is the key question of project initiation
    • M. Fangel To start or to start-up? That is the key question of project initiation International Journal of Project Management 9 1 1991 5 9
    • (1991) International Journal of Project Management , vol.9 , Issue.1 , pp. 5-9
    • Fangel, M.1
  • 14
    • 78649658885 scopus 로고    scopus 로고
    • How not to prepare for a consulting assignment, and other ugly consultancy truths
    • R.L. Glass How not to prepare for a consulting assignment, and other ugly consultancy truths Communications of the ACM 41 12 1998 11 13
    • (1998) Communications of the ACM , vol.41 , Issue.12 , pp. 11-13
    • Glass, R.L.1
  • 16
    • 0035337684 scopus 로고    scopus 로고
    • Frequently forgotten fundamental facts about software engineering
    • R.L. Glass Frequently forgotten fundamental facts about software engineering IEEE Software 18 May (3) 2001 111 112
    • (2001) IEEE Software , vol.18 , Issue.MAY 3 , pp. 111-112
    • Glass, R.L.1
  • 17
    • 0036734141 scopus 로고    scopus 로고
    • Project retrospectives, and why they never happen
    • R.L. Glass Project retrospectives, and why they never happen IEEE Software 19 5 2002 111 112
    • (2002) IEEE Software , vol.19 , Issue.5 , pp. 111-112
    • Glass, R.L.1
  • 18
    • 21244436832 scopus 로고    scopus 로고
    • It failure rates - 70% or 10-15%?
    • R.L. Glass It failure rates - 70% or 10-15%? IEEE Software 22 3 2005 111 112
    • (2005) IEEE Software , vol.22 , Issue.3 , pp. 111-112
    • Glass, R.L.1
  • 19
    • 33746238130 scopus 로고    scopus 로고
    • A case study on the success of introducing general non-construction activities for project management and planning improvement
    • Springer-Verlag
    • T. Haapio, and J.J. Ahonen A case study on the success of introducing general non-construction activities for project management and planning improvement Proceedings of PROFES 2006, vol. 4034 of LNCS Springer-Verlag 2006 151 165
    • (2006) Proceedings of PROFES 2006, Vol. 4034 of LNCS , pp. 151-165
    • Haapio, T.1    Ahonen, J.J.2
  • 21
    • 0033201528 scopus 로고    scopus 로고
    • Surviving the project management battle
    • G. Moore Surviving the project management battle Engineering Management Journal 9 5 1999 227 230
    • (1999) Engineering Management Journal , vol.9 , Issue.5 , pp. 227-230
    • Moore, G.1
  • 25
    • 0032640164 scopus 로고    scopus 로고
    • Critical success factors in software engineering
    • J.S. Reel Critical success factors in software engineering IEEE Software 16 3 1999 18 23
    • (1999) IEEE Software , vol.16 , Issue.3 , pp. 18-23
    • Reel, J.S.1
  • 29
    • 33846669891 scopus 로고    scopus 로고
    • The marketing strategy of a project-based firm: The four portfolios framework
    • H. Tikkanen, J. Kujala, and K. Artto The marketing strategy of a project-based firm: the four portfolios framework Industrial Marketing Management 36 2007 194 205
    • (2007) Industrial Marketing Management , vol.36 , pp. 194-205
    • Tikkanen, H.1    Kujala, J.2    Artto, K.3
  • 30
    • 0001142060 scopus 로고
    • Goals-and-methods matrix: Coping with projects with ill defined goals and/or methods of achieving them
    • J.R. Turner, and R.A. Cochrane Goals-and-methods matrix: coping with projects with ill defined goals and/or methods of achieving them International Journal of Project Management 11 2 1993 93 102
    • (1993) International Journal of Project Management , vol.11 , Issue.2 , pp. 93-102
    • Turner, J.R.1    Cochrane, R.A.2
  • 31
    • 19344363085 scopus 로고    scopus 로고
    • In-house software development What project management practices lead to success?
    • J.M. Verner, and W.M. Evanco In-house software development What project management practices lead to success? IEEE Software 22 1 2005 85 93
    • (2005) IEEE Software , vol.22 , Issue.1 , pp. 85-93
    • Verner, J.M.1    Evanco, W.M.2
  • 32
    • 0035998260 scopus 로고    scopus 로고
    • Organizational learning through postproject reviews in R&D
    • M. von Zedtwitz Organizational learning through postproject reviews in R&D R&D Management 32 3 2002 255 268
    • (2002) R&D Management , vol.32 , Issue.3 , pp. 255-268
    • Von Zedtwitz, M.1
  • 34
    • 1642446537 scopus 로고    scopus 로고
    • Identifying the hard lessons from projects - Easily
    • T. Williams Identifying the hard lessons from projects - easily International Journal of Project Management 22 4 2004 273 279
    • (2004) International Journal of Project Management , vol.22 , Issue.4 , pp. 273-279
    • Williams, T.1


* 이 정보는 Elsevier사의 SCOPUS DB에서 KISTI가 분석하여 추출한 것입니다.