A study of critical success factors of information system projects in China
K. B. Chuah,
Dept. of MEEM,
City University of Hong Kong
School of Management,
Proceedings of the PMI Research Conference
11-14 July 2004 – London, UK
Although there are many studies in project management literature on factors that affect the success or failure of projects, few have focused specifically on Information System (IS) projects, especially in China. This research sets out to study the critical success factors (CSFs) of contemporary information system projects in China. This paper presents the results of a large-scale questionnaire survey conducted in the Mainland of China to collect empirical support for the set of CSFs postulated based on extensive literature review. The survey reported here has collected responses of 247 IS project practitioners from three different sample sources. The first is randomly selected from the telephone directory’s yellow pages; the second from class lists of part-time students in Master of Business Administration (MBA) and professional training courses in Shanghai; and the third from a web-based survey. The data collected were analyzed using the computer programs SPSS® and SAS®. The result largely supports the findings of similar previous studies done in the West. This China survey has identified a newly added factor, relationship management, which we believe is the manifestation of the unique characteristics of Chinese culture and management practice. Furthermore, differences are also identified and discussed in the CSFs of this study when compared with those from the USA and Canada.
There have been many studies reported in project management literature on factors that contribute to the success or failure of projects. However, many of these critical success factors (CSFs) identified are rather too general as they tend to be derived from a wide variety of project types and not specific to a certain class of projects; in particular, the information system (IS) projects. The IS projects are still growing fast and continuing to be invested with huge amounts of money all over the world today. They have, however, also suffered greatly from a high rate of failure. Unfortunately, extensive literature review finds little effort focused specifically on the CSFs of IS projects. Two such studies are found in literature. Jiang, Klein, & Balloun (1996) reported their empirical findings of system implementation success factors in the United States of America (USA) based on Pinto and Slevin (1987) success-factors research in 1987. Recently, Hartman and Ashrafi presented their empirical result of the 10 most important CSFs from their interviews of 12 Information Systems /Information Technology projects in Canada (Hartman & Ashrafi, 2002). China’s IS project failure rate is even worse than those in the developed countries. Our recent literature review finds no published work about CSF studies in the IS projects of China. The business and industrial environment of China is still very different from the West. We believe that the CSFs identified in the developed countries from the West may not be totally applicable in the same manner to the Chinese IS project management practice and environment.
To bridge this gap, this research sets out to: 1) identify and study the major CSFs of IS projects in China; and 2) compare the difference of these CSFs with those found in the Western developed countries, namely the USA and Canada. The research findings will help the contemporary Chinese IS project practitioners to manage their project more effectively.
To achieve this research objective, the paper is organized as follows. First, in the second section, extensive literature of CSF in project management and IS are reviewed and a set of CSFs are postulated. Then the questionnaire is designed, the data collection in the Mainland of China is introduced, and the analysis of the survey data is described. In the third section, the survey results and comparison of the findings with previous research results are discussed. The fourth section is devoted to conclusions and future research directions.
2. Research Design
2.1 Review of checklist of success factors
The study of critical factors in project management has been conducted for many years. Notable contributions include Sayles and Chandler (1971); Martin (1976); Cleland and King (1983); Baker, Murphy, & Fisher (1983); Locke (1984); Morris and Hough (1987); Pinto and Slevin (1987); etc. Many of these studies can be regarded as having covered the majority of the important factors generic to most projects. However, factors affecting success of the project or the extent of their influence vary from one type of project to another, industry to industry, or even country to country (Pinto & Covin, 1989, Odedra-straub, 1993). What is universally agreed upon is that “managing projects is difficult” and “the world often interferes with our plans” (Cicmil, 1997).
To generate a hypothetical CSF list generic enough to cover most of the concerns of Chinese IS project managers, extensive literature has first been reviewed. The most commonly cited set of CSFs is compiled and used as the basis of the questionnaire designed. The postulated CSFs are:
a) Effective communication
Numerous authors have stressed that good communication is the key to a successful project (Cleland & King, 1983; Locke, 1984; Keider, 1984; Pinto & Slevin, 1988; Barki, Rivard, & Talbot, 1993). IS projects are probably no exception. In fact, Martinez’s study has revealed that the greatest threat to the success of any IS project is a failure to communicate effectively (Martinez, 1996).
IS projects are often complex and cross-disciplinary in nature. Good communication among project team members should lead to expectations that are more realistic, better relationships, and more effective teamwork (Milis & Mercken, 2002). Outside the project team, the most important stakeholder to an IS project is its users. IS literature has repeatedly emphasized the importance of communication between the IS developers and its users (Edstrom, 1977; Cronan & Means, 1984; Martin & Fuerst, 1984; Bostrom, 1989). Furthermore, the communication should also be extended to all major stakeholders, such as top management and so on, as verified by empirical evidence (Keider, 1984; Effy & John, 2000). In the Chinese industrial environment of today, is this multi- dimensional communication such an important factor too?
b) Top management support
Literature echoes the general consensus view that top management support is one of the most critical factors to project success (Anderson & Narasimhan, 1979; Pinto & Slevin, 1987; The Standish Group, 1994; Belassi & Tukel, 1996; Fowler & Walsh, 1999). There is also reported empirical evidence that shows the crucial role of top management involvement in IS development projects (Ewusi-mensah & Parzasnyski, 1991, 1994).
Top management support for the project must be real as well as perceived. It is obvious that top management must be willing to provide sufficient resources (financial, manpower, time, etc) for the project (Martin, 1976; Cleland & King, 1983; Baker et al., 1983; Belassi & Tukel, 1996). Moreover, senior management has to realize the complexity of changes resulting from IS projects (Ewusi-mensah & Parzasnyski, 1994). Empirical surveys have found that the fear of unemployment and the fear of the unknown impact computers would cause were significant obstacles to IT adoption in China in the early 90‘s (Ishman, Pegels, & Sanders, 1994). It is natural to extend this to the implementation of IS projects in China.
c) User involvement
Many project management and IS studies have found that user involvement is crucial to the successful completion of IS development projects (Robey & Farrow, 1982; Ives & Olson, 1984; Barki & Hartwick, 1989; Ewusi-mensah & Parzasnyski, 1994; Jiang et al., 1996; Jiang, Chen, & Klein, 2002; Dvir, Raz, & Shenhar, 2003).
IS development projects are described as conceptually intensive (Ewusi-mensah, 1997) and quasi-occasional (Wateridge, 1999), as it is often difficult to completely and explicitly determine the system requirements at the start of the project. It is suggested that requirements must be allowed to be refined as a project progresses and then be fixed at some appropriate point in time (Wateridge, 1999). An effective way to refine system requirements is for the project manager to involve the users from the start of the project and have them continue for as long as they are needed (Dvir et al., 2003).
d) Project manager and team members
Because the project manager and the members of the project team are changed with the responsibility of managing and carrying out the project work, general agreement between them is critical to project success (Turner, 1993; Belassi & Tukel, 1996; Milis & Mercken, 2002). In the study, this factor will be further divided into project manager and project team members.
First, the project manager should be competent. Although some projects fail because of technology or design problems, most of the factors that lead to the failure of system development projects are within the control of the project manager (Keider, 1984). Meanwhile, your project team should be staffed with skilled and effective team players who possess the expertise that the project requires (Mcleod & Smith, 1996). Obviously, the project manager has to try to ensure that the team members can work cohesively, have a common goal, and be committed to the project.
e) Project definition
The right choice of project accounts for half of the project's success. The effort of the project team will not redeem a project that is doomed to fail because it has been ill-conceived or because of poor early decision-making (Munns & Bjeirmi, 1996).
Furthermore, the statement of the project objective must be clear and concrete (Pinto & Slevin, 1987; The Standish Group, 1994). Of course, it must be realistic (Milis & Mercken, 2002) and measurable (Wateridge, 1998) as well. Other researchers also suggest that the project objective should be congruent and agreed upon by the project stakeholders and participants (Clarke, 1999). Aiming at a clear and agreed-upon project objective, the project team’s effort must be within a definite and defined project scope. Scope changes are said to be the most common source of project overruns (Jolyon, 1998; Clarke, 1999). Inadequate definition of project scope was thought to be the second most frequent cause of most IS project failures (Keider, 1984).
f) Project planning
Literature provides much evidence that a well-set project plan plays a vital role in project success (Cleland & King, 1983; Baker et al., 1983; Milis & Mercken, 2002; Dvir et al., 2003).
For an IS project, Keider’s research indicated that the lack of good project planning is ranked as the most likely single cause of project failure (Keider, 1984). Effective planning is more than just setting up an elaborate plan at the start of a project. A good project manager monitors the progress closely and regularly updates the project plan throughout the project implementation.
g) Project control and change management
Regardless of the degree of project complexity, most project specifications change to some degree. During project implementation, change control and management are critical to the success of a project (Sayles & Chandler, 1971; Baker et al, 1983; Locke, 1984; Pinto & Slevin, 1987; Wateridge, 1999). The problem of changes is particularly severe in the case of software development and IS projects (Ewusi-mensah & Parzasnyski, 1994; Meredith & Mantel, 2000).
An IS project manager must concern himself/herself with keeping track of all changes and having a disciplined approach to cope with changes. A formal change management system is a useful tool and an integral part of a configuration management system (Mcleod & Smith, 1996). With it, a project manager can manage effectively not only user requirement change requests, one of the biggest problems of an IS project, but also any other changes in implementation (analysis, design, code, etc) (Wateridge, 1999).
h) Technology support
Although technology factors are said to be not as important a consideration as management and organization issues, they still play a contributory role to some IS projects’ abandonment, cancellation, or failure (Ewusi-mensah & Parzasnyski, 1991, 1994; Ewusi-mensah, 1997; Yeo, 2002; Hartman & Ashrafi, 2002). There must exist appropriate technical capability and infrastructure in the organization to effectively support the IS development and implementation.
i) Other three factors in the research
Apart from the above factors, the research also identifies project organization (Martin, 1976; Cleland & King, 1983; Baker et al., 1983), project management software, and techniques as CSF of an IS project. Finally, relationship management is also included as a factor in our postulated 12 CSFs to take care of the effect on the so-called unique Chinese characteristics. In this study, “relationship” is taken to be synonymous with the often-used “guanxi” or “connection.”
2.2 Questionnaire and Measurement
Although Rockart stated in his prominent seminal paper that interviewing is a useful way to acquire critical success factors (Rockart, 1979), others prefer to use questionnaire surveys (Martin, 1982; Wetherbe & Leitheisier, 1985). In this research, considering the immense geographical spread of China, a structured questionnaire survey is adopted as the main data-collection method.
A total of 12 CSFs and 65 associated CSF statements were defined in the questionnaire. Multivariate measurement was employed to assess CSF concepts. Between three and eight different statements were elicited from each of the 12 CSFs to represent differing aspects of the CSF. All these CSFs and most of the associated statements are generally based on previous CSF studies discussed. Only a few of them are adapted or newly proposed to better suit this study of Chinese practices.
A numerical scale of one to seven ranging from “very unimportant” to “very important” was used to measure a survey respondent’s perceived importance of the 65 CSF statements. A sample of the questionnaire is given in Appendix 1. Referable discussions about the design of the questionnaire are given elsewhere (Slevin & Pinto, 1986; The Standish Group, 1995).
2.3 Sample and Data Collection
There are three different sources of respondents in this survey. The first is a randomly compiled list of firms from websites and the yellow pages of a telephone directory. The second is compiled from the lists of MBA programs of Shanghai’s Fudan University and IS project professional training courses sponsored by Shanghai City government. In order to increase the generalizability of the research findings, the questionnaire is also posted on web pages of two project management websites in the Mainland of China to acquire more respondents of diverse backgrounds. The detailed distribution of questionnaires and usable return rate is presented in Table 1. After data screening and cleaning, a total of 247 usable questionnaires were reserved for data analysis.
|Respondents source||Distributed questionnaires||Returned usable questionnaires||Usable return rate|
|1. Randomly selected firms||488||96||19.67%|
|2. MBA students/IT Training practitioners||292||81||27.74%|
|3. PM Websites||/||70||/|
Table 1: Distributed and Returned Usable Questionnaires
2.4 Data analysis
To begin data analysis, the non-response bias was first examined using SPSS. A one-way multivariate analysis of variance was performed to investigate sample source difference in CSF statements. The result of MANOVA analysis obtained a Wilks' Lambda value of 0.51, with a significance value of 0.22. The result shows that there is no statistically significant difference among three different sample sources (Pallant, 2001), which means that there is no significant non-response bias. Therefore, it is acceptable to regard these three sample sources as one in the subsequent data analysis.
The scale reliability and validity of the combined data set was than analyzed. We assessed the internal consistency for multi-item scales by computing Cronbach’s alpha value. The 12 CSFs with different numbers of items have a composite scale reliability value ranging from 0.75 to 0.91, thus meeting the requirements for exploratory research.
In addition, we examined the construct validity of the measures by using confirmatory factor analysis (CFA). Because of the sample size restrictions, four separate tests were performed using SAS CALIS procedure, each having 3 CSF constructs. The result shows that 60 of 65 CSF statements have a standardized factor loading of more than 0.60 corresponding to their respective CSF. The average factor loading coefficient for all 65 items is 0.70. Meanwhile, all questionnaire items have significant t values with a confidence interval at p< 0.001.
The mean value of each CSF was also computed. The result is shown in Table 2.
|2||Clear project definition||5.87||0.80|
|3||Top management support||5.86||0.77|
|4||Competent project manager||5.76||0.84|
|7||Project control and change management||5.66||0.91|
|9||Competent project team members||5.56||0.85|
|11||Technology and expertise support||5.37||0.83|
|12||Project management software and techniques||4.88||0.87|
Table 2: CSF Mean Ranking and Reliabilities of Measures
3. Findings and discussion
Among the 12 CSFs identified for the present study of Chinese IS projects, certain factors, such as relationship management, have rarely been studied as a CSF. The present study result has ranked it in the middle, higher than a few other CSFs that have been studied more frequently. This is perhaps symptomatic of the unique characteristics of Chinese culture and management practice. Apart from this, most of the other CSFs’ rankings are similar to the research findings of empirical studies conducted in developed countries.
Two previous CSF studies in the USA (Jiang et al, 1996) and Canada (Hartman & Ashrafi, 2002) are cited in the introductory portion of the article, and the results from the present survey are compared with these two sets of findings. The comparison is summarized in Table 3.
|The Mainland of China||USA||Canada|
|Clear project definition||2||1||4|
|Top management support||3||2||5|
|Competent project manager||4||3||/|
|Project control and change management||7||12||9|
|Competent project team members||9||4||/|
|Technology and expertise support||11||/||8|
|Project management software and techniques||12||/||/|
* Factors ranked 1 and 2 in the Canada study are both about user and its involvement.
Table 3: Ranking Comparison of Corresponding CSFs in the Mainland of China, USA (Jiang et al, 1996) and Canada (Hartman & Ashrafi, 2002)
This study and the two previous studies in the USA and Canada differ greatly in research design and survey sample, and the definition and scope of CSFs proposed for the researches may also be slightly different. But they generally produce very similar insights and reveal an analogous underlying structure of CSFs for an IS project.
As mentioned earlier, one noticeable difference in our China survey results is the ranking of a newly added factor, relationship management. It is ranked 6th among the 12 factors, implying that it plays an important role in Chinese IS project implementation. A reasonable interpretation is that it is a manifestation of the significant influence of Chinese traditional belief and culture on Chinese organizational behavior and management practice today. Good personal relationships are often critical to the dealings among the Chinese, whether it is in a social or job-related context. The IS project environment is no different. Thus the relatively high ranking of the relationship management factor in this survey result is not surprising.
The top-ranked CSF in this study is “effective communication,” which ranked in the middle in the USA study and third in the Canada study. This reason for this difference is perhaps because, to Chinese project personnel, “effective communication” is not only needed to resolve problems during the project implementation, but it is also essential to maintain the previously-mentioned good personal relationships.
The next top-ranked factor is “clear project definition,” which is ranked at the top in the USA study and fourth in the Canada study. Apparently, there is a common acceptance of this factor's importance. It is easy to understand that a project must match with an organization's goals, and that its objective has to be clearly defined. In fact, the expectation of a clearly defined objective for the Chinese is not surprising because of the long history of central control in China (Andersen, Dyrhaug, & Jessen, 2002).
The CSFs that are related to the stakeholders follow next, with the exception of “competent project team members,” These CSFs include “top management support,” “competent project manager,” and “user involvement.” There is general agreement that “top management support” is always vital to project success. The results show that “competent project team members” in China play a less critical role than in the USA, while “user involvement” is judged to be more important than in the USA but less than in Canada. Although “user involvement” is deemed as important, it may not be quite as critical as many purport (Jiang et al, 1996).
“Project planning” and “project control and change management” are factors associated with project life cycle, which appears to take up the middle rankings of China’s CSFs. “Project control and change management” has relatively higher importance in China than in the USA and Canada. This may be the result of poor project control and management of change in China’s IS project.
Lowest ranked of the China’s CSFs are the “project management software and techniques” and “technology and expertise support”--which are factors associated with management techniques and technical issues. This result apparently agrees with previous research findings, and confirms that administrative, human, and organization factors are more important than technical factors. But this is not to say that technical factors are unimportant to IS projects, just that they are comparatively less important than the others.
The literature has reported few CSF studies on IS projects, especially in China. The survey study sets out to collect empirical support for the set of CSFs relevant to contemporary China’s IS projects. The preliminary result is also compared with those from two previous studies in the USA and Canada.
The result of this China survey about 12 CSFs of Chinese IS projects has for the most part supported the research findings of similar studies done in the West. One of the key findings in this preliminary analysis is that “relationship management” is viewed as an important CSF for Chinese IS projects. Also, there are noticeable differences are identified and discussed in the CSFs ranking from this China survey compared with those from USA and Canada studies.
Although there are not many surprises in the result, this empirical research using a large-scale survey still represents the first effort to study the contemporary practice of Chinese IS project management. The research findings about the CSFs and their ranking order give a better insight to contemporary Chinese IS project practitioners and help them to manage their projects more effectively. The detailed sub-factors of each CSF provide IS project managers various implications to help them cope with different project environments. Furthermore, detailed analysis of the CSFs will be carried out, which will help to lay the foundation for the development of a CSF management model for Chinese IS projects. It is envisaged that this CSF model will further lead to an IS project diagnosis and evaluation system that can provide pragmatic guides for China’s IS project managers.
Dong Chao gratefully acknowledges the generous PhD studentship he receives from City University of Hong Kong in support of his PhD study. This research is carried out in collaboration with the research team of Fudan University, Shanghai, under supervision of Dr. Zhai Li, who has received funding support from China’s Nation Natural Science Foundation.
Andersen, E S., Dyrhaug, Q L X., & Jessen, S A. 2002. Evaluation of Chinese projects and comparison with Norwegian projects. International Journal of Project Management 20(8): 601-609.
Anderson, J., & R, Narasimhan.1979. Assessing implementation risk: a methodological approach. Management Science 25(6): 512-521.
Baker, B N., Murphy, D C., & Fisher, D. 1983. Factors affecting project success. in Project Management Handbook, ed. Cleland, D. I. & King, W. R. Second Edition. New York: Van Nostrand Reinhold, 479-512.
Barki, H., & Hartwick, J. 1989. Rethinking the concept of the user involvement. MIS Quarterly 13(1): 53-63.
Barki, H., Rivard, S., & Talbot, J. 1993. To award an assessment of software development risk. Journal of Management Information System 10(2): 203-255.
Belassi, W., & Tukel, O I. 1996. A new framework for determining critical success/failure factors in projects. International Journal of Project Management 14(3): 141-151.
Bostrom, R P. 1989. Successful application of communication techniques to improve the system development process. Information and Management Science 16: 137-155.
Clarke, A. 1999. A practical use of key success factors to improve the effectiveness of project management. International Journal of Project Management 17(3): 139-145.
Cleland, D I., & King, W R. 1983, Systems Analysis and Project Management. New York: McGraw Hill.
Cicmil, Svetlana J K. 1997. Critical factors of effective project management. The TQM Magazine: 9(6): 390-396.
Cronan, R P., & Means, T L. 1984. System development: an empirical study of user communications. Data Base, Spring: 35-43.
Dvir, D., Raz, T., & Shenhar, A J. 2003. An empirical analysis of the relationship between project planning and project success. International Journal of Project Management 21:89-95.
Edstrom, A. 1977. User influence and the success of MIS project: a contingency approach. Human Relations 30(7): 96-128.
Effy, O Z., & John, J Sosik. 2000. Why information system projects are abandoned: a leadership and communication theory and exploratory study. Journal of Computer Information Systems Fall: 66-78.
Ewusi-mensah, K. 1997. Critical issues in abandoned information systems development projects. Communications of the ACM 40 (9): 74-80.
Ewusi-mensah, K., & Parzasnyski, Z H. 1991. On information system project abandonment: an exploratory study of organizational practices. MIS Quarterly 15(1): 67-86.
Ewusi-mensah, K., & Parzasnyski, Z H. 1994. Factors contributing to the abandonment of information systems development project. Journal of Information Technology 9: 185-201.
Fowler, A., & Walsh, M. 1999. Conflicting perceptions of success in an information systems project. International Journal of Project Management 17: 1-10.
Hartman, F., & Ashrafi, R A. 2002. Project management in the information systems and information technologies industries. Project Management Journal 33 (3): 5-15.
Ishman, M D., Pegels, C C., & Sanders, G L. 1994. A window on information systems technology in china, Journal of Strategic Information Systems 3 (4): 299-311.
Ives, B., & Olson, M H. 1984. User involvement and MIS success: a review of research. Management Science 30 (5): 586-603.
Jiang, J J., Chen, E., & Klein, G. 2002. The importance of building a foundation for user involvement in information system projects. Project Management Journal 33(1): 20-26.
Jiang, J J., Klein, G., & Balloun, J. 1996. Ranking of system implementation success factors. Project Management Journal 27(4): 49-53.
Jolyon, E H. (1998). Information System Project Management. American Management Association. Keider, S P. 1984. Why systems development project fail. Journal of Information Systems Management 1(3): 33-38.
Locke, D. 1984. Project Management. New York: St. Martins Press.
Martin, C C. 1976. Project Management Amaco. New York.
Martin, E W. 1982. Critical success factors of chief MIS/DP executives. MIS Quarterly 6(2): 1-9.
Martin, M P., & Fuerst, W L. 1984. Communications framework for system design. Journal of Systems Management 35(3): 18-25.
Martinez, E. 1996. Loud and clear. CIO Magazine April.
Mcleod, G., & Smith, D. 1996. Managing Information Technology Projects. Cambridge: Course Technology. Meredith, J R., & Mantel, S J. 2000. Project Management: a Managerial Approach. Fourth Edition. New York: John Willey & Sons.
Milis, K., & Mercken, R. 2002. Success factors regarding the implementation of IS/IT investment projects. International Journal of Production Economics 80: 105-117.
Morris, P W., & Hough, G H. 1987. The Anatomy of Major Projects. New York: John Wiley and Sons.
Munns, A K., & Bjeirmi, B F. 1996. The role of project management in achieving project success. International Journal of Project Management 14(2): 81-87.
Odedra-straub, M. 1993. Critical factors affecting success of CBIS: Cases from Africa. Journal of Global Information Management 1(3): 16-31.
Pallant, Julie. 2001. SPSS survival guide: a step by step guide to data analysis using SPSS. Australia: Allen & Unwin.
Pinto, J K., & Covin, J G. 1989. Critical factors in project implementation: a comparison of construction and R & D projects. Technovation 9: 49-62.
Pinto, J K., & Slevin, D P. 1987. Critical factors in successful project implementation. IEEE Transactions on Engineering Management EM-34 (1): 22-27.
Pinto, J K., & Slevin, D P. 1988. Critical success factors across the project life cycle. Project Management Journal 19(3): 67-75.
Rockart, J F. 1979. Chief executives define their own data needs. Harvard Business Review March-April: 81-93.
Robey, D., & Farrow, D. 1982. User involvement in information system development: a conflict model and empirical test. Management Science 28: 73-85.
Sayles, L R., & Chandler, M K. 1971. Managing large Systems. New York: Harper and Row.
Slevin, D P., & Pinto, J K. 1986. The project implementation profile: new too for project managers. Project Management Journal 17(3): 57-70.
The Standish Group. 1994. The CHAOS Report. Http://WWW.standishgroup.com/sample_research/chaos_1994_1.php.
The Standish Group. 1995. Unfinished voyages: a follow-up to the CHAOS report. Http://www.standishgroup.com/sample_research/unfinished_voyages_1.php.
Turner, J R. 1993. The Handbook of Project-Based Management. New York: McGraw-Hill.
Wateridge, J. 1998. How an IS/IT Projects be measured for success? International Journal of Project Management 16(1): 59-63.
Wateridge, J. 1999. The role of configuration management in the development and management of IS IT projects. International Journal of Project Management 17(4): 237-241.
Wetherbe, J C., & Leitheisier, R J. 1985. Information center: a survey of service, decision, problems, and success. Journal of Information Systems Management Summer: 3-10.
Yeo, K T. 2002. Critical failure factors in information system projects. International Journal of Project Management 20: 241-246.
Questionnaire on Critical Success Factor Of Information System Project
Instruction: Please indicate your choice by putting a check “√” in the appropriate box “□”or input your personal information on the blank provided for part one.
Part One: Personal information
Have you ever participated in an information system project (such as information system development, package implementation/ERP, system integration, and so on)?
□ Yes; □ No (If “No” is chosen, please transmit the questionnaire to your colleague who participates in the project)
How many years have you worked in information system:___________.
In which city are you working now? ____________.
Your present position in project: □ Users □ IS Executive □ IS Project Manager □ Project Team Members
Part two: Critical Success Factors
Please indicate your choice by putting a check “√” next to the appropriate scale number provided below statements. Each statement in this part is considered a potential critical success factor for an information system project. For each of them, please indication the scale below their respective importance to the success of the project from your personal experience and perception‥
Scale (Very Unimportant 1 2 3 4 5 6 7 Very Important, 0 I don't know)
|Very Unimportant||Very Important||I don't know|
|1||The project objective is viewed as important to the organization's long-term strategy objective||1||2||3||4||5||6||7||0|
|2||The project is selected and justified appropriately based on adequate project feasibility study||1||2||3||4||5||6||7||0|
|3||The project has a clear and realistic project goal||1||2||3||4||5||6||7||0|
|4||The project has a clearly defined project scope||1||2||3||4||5||6||7||0|
|5||There is broad consensus of project goal and scope among key stakeholders||1||2||3||4||5||6||7||0|
|6||The project's final deliveries are clearly defined at project startup||1||2||3||4||5||6||7||0|
|7||The project has agreed-upon success criteria among stakeholders||1||2||3||4||5||6||7||0|
|8||There is accurate project budgeting and cost estimation at project startup||1||2||3||4||5||6||7||0|
|9||There is sufficient risk estimation at project startup||1||2||3||4||5||6||7||0|
|10||The project has an easily understood master plan with well-set milestones||1||2||3||4||5||6||7||0|
|11||The project plan and milestones are agreed-upon and accepted by all key participants||1||2||3||4||5||6||7||0|
|12||The project is broken down into smaller manageable work packages with an appropriate level of detail||1||2||3||4||5||6||7||0|
|13||The project plan contains some buffering of resources and a degree of urgency||1||2||3||4||5||6||7||0|
|14||The project progress is monitored closely by efficient tracking method||1||2||3||4||5||6||7||0|
|15||There are effective information feedback channels during project execution||1||2||3||4||5||6||7||0|
|16||Project deviations off plan are well handled in time||1||2||3||4||5||6||7||0|
|17||The project plan is updated regularly according to real situation||1||2||3||4||5||6||7||0|
|18||Senior management would like to offer necessary help and support for the project when requested||1||2||3||4||5||6||7||0|
|19||Senior management commits to provide sufficient resources required for the project||1||2||3||4||5||6||7||0|
|20||Senior management would like to support proper organizational changes required for the project||1||2||3||4||5||6||7||0|
|21||The project manager has sufficient PM knowledge and relevant experience||1||2||3||4||5||6||7||0|
|22||The project manager has enough expertise relevant to project.||1||2||3||4||5||6||7||0|
|23||The project manager is able to handle conflicts that occur in the project positively and effectively.||1||2||3||4||5||6||7||0|
|24||The project manager leads his team with appropriate project leadership||1||2||3||4||5||6||7||0|
|25||The project manager is capable of acquiring adequate resources for the project||1||2||3||4||5||6||7||0|
|26||The project manager is able to allocate appropriately and make the best use of project resources||1||2||3||4||5||6||7||0|
|27||There are no or very few changes by the project manager that could affect project progress||1||2||3||4||5||6||7||0|
|28||The project team is staffed with skilled team players who possess the expertise the project requires||1||2||3||4||5||6||7||0|
|29||The team members are l motivated and committed to a shared goal||1||2||3||4||5||6||7||0|
|30||The technical members have experience relevant to the project||1||2||3||4||5||6||7||0|
|31||The team members are provided with required training||1||2||3||4||5||6||7||0|
|32||There are no or very few key staff changes that could affect the project during project processing||1||2||3||4||5||6||7||0|
|33||Users can state their requirements clearly||1||2||3||4||5||6||7||0|
|34||User requirements and expectations are realistic||1||2||3||4||5||6||7||0|
|35||Users can involve project actively as necessary||1||2||3||4||5||6||7||0|
|36||Users have the ability to use the deliveries of project||1||2||3||4||5||6||7||0|
|37||Technology and development methodology adapted in project satisfy project objective||1||2||3||4||5||6||7||0|
|38||An appropriate technical infrastructure exists to support project implementation||1||2||3||4||5||6||7||0|
|39||There is sufficient expertise and technical know-how within the organization required for the project||1||2||3||4||5||6||7||0|
|40||Project vendors can provide sufficient support for the project||1||2||3||4||5||6||7||0|
|41||There are no critical technology changes that affect the project||1||2||3||4||5||6||7||0|
|42||The project stakeholders are well informed about status of the project and necessary information||1||2||3||4||5||6||7||0|
|43||There are good communication, mutual respect, and effective conflict resolution among project team members||1||2||3||4||5||6||7||0|
|44||There is adequate and effective communication between users and project team||1||2||3||4||5||6||7||0|
|45||The project manager has sufficient communication with top management||1||2||3||4||5||6||7||0|
|46||Project participants have sufficient communication with each other as necessary||1||2||3||4||5||6||7||0|
|47||A formal change management process exists in organization to manage project changes||1||2||3||4||5||6||7||0|
|48||An effective problem-solving procedure exists during project implementation||1||2||3||4||5||6||7||0|
|49||Project scope changes are managed well||1||2||3||4||5||6||7||0|
|50||Users requirement changes are handled and managed effectively||1||2||3||4||5||6||7||0|
|51||The project is organized with appropriate project organization||1||2||3||4||5||6||7||0|
|52||The project manager is authorized with appropriate power||1||2||3||4||5||6||7||0|
|53||Each participant in the project has a clear role, responsibility, authority and report relationship with others||1||2||3||4||5||6||7||0|
|54||The project participants' performances are evaluated objectively and feedback is given promptly||1||2||3||4||5||6||7||0|
|55||The appropriate project software (such as MS Project) is utilized to facilitate the management of project||1||2||3||4||5||6||7||0|
|56||The project management techniques (such as Gant Chart, CPM/PERT) are used to support project management||1||2||3||4||5||6||7||0|
|57||There are cohesive relationships among project team members||1||2||3||4||5||6||7||0|
|58||The project manager has a good relationship with project team members||1||2||3||4||5||6||7||0|
|59||The project manager keeps harmonious relationship with top management||1||2||3||4||5||6||7||0|
|60||The project manager and project team members hold coordinated relationship with users||1||2||3||4||5||6||7||0|
|61||The project manager keeps cooperative relationship functional manager||1||2||3||4||5||6||7||0|
|62||There are suitable organizational environments for the project||1||2||3||4||5||6||7||0|
|63||Consultants or experts are able to provide required professional consultation or expertise when needed||1||2||3||4||5||6||7||0|
|64||Documents are recorded regularly and managed well in project life cycle||1||2||3||4||5||6||7||0|
|65||Users are provided with necessary training when project is finished||1||2||3||4||5||6||7||0|
Author Contact Information
Department of Manufacturing Engineering and Engineering Management, City University of Hong Kong.
Postal mailing address: Room Y1412, 1/F, Department of MEEM, City University of Hong Kong, 83 Tat Chee
Avenue, Kowloon Tong, Hong Kong, PRC.
Tel: (852) 27844609
Dr K. B. Chuah
Department of Manufacturing Engineering and Engineering Management, City University of Hong Kong.
Postal mailing address: Room Y6611, Department of MEEM, City University of Hong Kong, 83 Tat Chee
Avenue, Kowloon Tong, Hong Kong, PRC.
Tel: (852) 27888437 Fax: (852) 27887660
Dr Li Zhai
School of Management, Fudan University, Shanghai, China.
Postal mailing address: School of Management, Fudan University, Shanghai, PRC.
PMI research shows project teams that draw from an array of perspectives and skillsets deliver powerful outcomes.