Serious problem projects (SPPs) often occur, particularly in a system integration environment, and it is difficult to prevent them, since the relationships among phenomena that occur throughout the project life cycle are extremely complicated. Our goal is to make it easier to identify major risks by distinguishing phenomena that are sources of future SPPs from phenomena observed in actual field projects. By choosing several events whose causal relation is known to be cyclic, we constructed a causal model and clarified that it can contribute to the easier recognition of SPPs empirically, by analyzing actual SPP cases.
GanoL. (1999). Apollo root cause analysis.Yakima, WA: Apollonian Publications.
2.
GongyiL., & YokoyamaS. (2007). Proposal of updating method for project risk evaluation. Journal of the Society of Project Management, 9(2), 27–33.
3.
HaiharaM. (2005, January). Puromane shippai-gaku(in Japanese). Minato-ku, Tokyo, Japan: Nikkei IT Professionals; pp. 136–141.
4.
Information-Technology Promotion Agency Software Engineering Center (IPA SEC). (2006). MIERUKA of IT project (about lower development phase)(in Japanese). Minato-ku, Tokyo, Japan: Nikkei BP.
5.
Information-Technology Promotion Agency Software Engineering Center (IPA SEC). (2007). MIERUKA (visualization) of IT project (about upper development phase)(in Japanese). Minatoku, Tokyo, Japan: Nikkei BP.
6.
Information-Technology Promotion Agency Software Engineering Center (IPA SEC). (2008a). MIERUKA of IT project (about middle development phase)(in Japanese). Minato-ku, Tokyo, Japan: Nikkei BP.
7.
Information-Technology Promotion Agency Software Engineering Center (IPA SEC). (2008b). MIERUKA of IT project (summary)(in Japanese). Minato-ku, Tokyo, Japan: Nikkei BP.
8.
JensenF. V., & NielsenT. D. (2007). Bayesian networks and decision graphs.New York: Springer.
9.
KappelmanL. A., McKeemanR., & ZhangL. (2006). Early warning signs of IT project failure: The dominant dozen. Information Systems Management, 23(4), 31–36.
10.
KepnerH., & TregoeB. (1997). The new rational manager.Princeton, NJ: Princeton Research Press.
11.
KhodakaramiV., FentonN., & NeilM. (2007). Project scheduling: Improved approach to incorporate uncertainty using Bayesian networks. Project Management Journal, 38(2), 37–49.
12.
McManusJ., & Wood-HarperT. (2007, Autumn). Understanding the sources of information systems project failure. Management Services, pp. 38–43.
13.
Project Management Institute. (2004). A guide to the project management body of knowledge (PMBOK® Guide)—Third edition. Newtown Square, PA: Author.
14.
Project Management Institute. (2008). A guide to the project management body of knowledge (PMBOK® Guide)— Fourth edition. Newtown Square, PA: Author.
15.
ReichB. H. (2007). Managing knowledge and learning in IT Projects: A conceptual framework and guidelines for practice. Project Management Journal, 38(2), 5–17.
16.
RobertsonS., & WilliamsT. (2006). Understanding project failure: Using cognitive mapping in an insurance project. Project Management Journal, 37(4), 55–71.
17.
RobsonM. (1995). Problem solving in groups.Brookfield, VT: Gower.
18.
TaylorH. (2006). Risk management and problem resolution strategies for IT projects: Prescription and practice. Project Management Journal, 37(5), 49–63.
