• Journal of Information Technology Applications and Management
• /
• v.13 no.4
• /
• pp.237-255
• /
• 2006

This study was exploratively performed to demonstrate the management behavior of the public software project in korea. In this study, 167 auditing reports on the public software project which were carried out during $1999{\sim}2003$, were employed and surveyed. Survey reveals that quality management was the most neglected in process of software project management relative to other 12 management areas. And configuration management, risk management, time management, and scope management follow up in order in its vulnerability in software project management.

• Asia pacific journal of information systems
• /
• v.6 no.1
• /
• pp.241-267
• /
• 1996

The problems like exceeding estimated cost, late due-date, expensive maintenance, insuffiency of experts and low productivity are becoming emphasized related with the software development. In order to overcome these problems and to develop the highly qualified software within the limited resources, a project management tool is used. The purpose of this study is to develop a conceptual model of the project management system which can plan, analyze and control the software development projects effectively. The model is constructed with plan and track management system, cost management system and operation management system for the efficient project management. It is named by LSD-PMS : Large-scale Software Development Project Management System. We reviewed 5 cases of project management. LSD-PMS is evaluated and reviewed by the project managers in the field. It is proved that LSD-PMS is a tool which can help project managers develop software successfully given budget and time schedule. In the future, this system should be further developed as an integrated model with system implementation tools such as CASE products.

• Journal of Information Technology Applications and Management
• /
• v.11 no.4
• /
• pp.103-120
• /
• 2004

Identifying validated risk factors in software risk management is imperative for project managers. Although validated risk lists were provided by previous researchers, risk list associated with software project performance areas was not provided as yet. This paper represents a first step toward understanding risk lists by various project performance areas (time, cost, and quality) to help project managers alleviating the possibility of software project failure. Four simultaneous exploratory surveys were conducted with 29 experienced software project managers. Three different risk factor ranking sets for each project performance area were compared with, the risk ranking, which was provided without clarifying specific project performance areas. The risk lists and their corresponding perceived importance were different from previous research results. This implies that identifying risk factors for specific project performance areas can provide additional information for project managers. We concluded by discussing implications of our finds for both research and improving risk management practice.

• Proceedings of the Safety Management and Science Conference
• /
• 2006.04a
• /
• pp.525-544
• /
• 2006

This paper is to introduce guidelines for project quality management system. International standards such as ISO 10006, IEC 62198, ISO/IEC TR 16326 and ISO 15188 are considered. This study is to discuss guidelines for quality management in projects, and application guidelines for project risk management, and guide for the application of ISO/IEC 12207 to software project management, and project management guidelines for terminology standardization.

• IE interfaces
• /
• v.21 no.2
• /
• pp.198-208
• /
• 2008

Effective management of a project is a crucial issue to software companies. There are various international standards, such as CMM, ISO9000, and SPICE, applied to project management. But, small scale companies have some difficulties in accepting those standards because of its complexity and enormous manpower requirements. This study proposes a project management approach streamlining the CMM by which a small scale software company can perform the tasks with ease. A prototype system has also been developed to show the capability of the proposed model.

• The Journal of Information Systems
• /
• v.13 no.1
• /
• pp.1-20
• /
• 2004

Most of the software development projects bear risks that need analysis and management. Risk management plays a critical role for the success of software project management. In this study, we have used delphi method to delineate critical risk factors. The study pulls out 20 project risk factors from 21 project managers. It is certainly clear that certain features are more risky than others. Our study shows that unrealistic cost estimation and changes in scope and objective are more risky than other features.

• Asia pacific journal of information systems
• /
• v.13 no.2
• /
• pp.199-217
• /
• 2003

Based on the IS literature on software project risk management, we developed an integrated model to investigate the risk factors and risk management factors in project development. We also analyzed the interrelation between project risk and project risk management. The questionaries are collected from 83 project leaders. We tested reliability and validity of the measure and analyzed the obtained data. The results support our risk-based hypothesis that shows the importance of risk management in reducing project risks and improving performance of project and process.

• Journal of Information Technology Applications and Management
• /
• v.11 no.2
• /
• pp.15-27
• /
• 2004

Most software projects inevitably involve various types and degrees of uncertainty. Without proper risk assessment and coordination, software projects can easily run out of control and consume significant additional resource. Thus, risk management techniques are critical issues to information system researchers. Previous empirical studies of U.S. software firms support the adoption of development standardization and user requirement analysis techniques in risk-based software project management. Using data collected from software projects developed in Korea during 1999-2000, we conduct a comparative study to determine how risk management strategies impact software product and process performance in countries with dissimilar IT capabilities. In addition, we offer an alternative conceptualization of residual performance risk. We show that the use of residual performance risk as an intervening variable is inappropriate in IT developing countries like Korea where the role of late stage risk control remedies are critical. A revised model is proposed that generates more reliable empirical implications for Korean software projects.

• The Journal of Information Systems
• /
• v.16 no.4
• /
• pp.243-268
• /
• 2007

It is critical to manage risks to complete IS(Information Systems) projects successfully. Identifying risk factors would be the first step for the project risk management. Previous research has discussed the issue with various points of view, such as different risk factors based on project types and roles involved in their projects. This paper empirically explored how people perceive different risk factors by project development methodology, between self-developing IS using programming language like C, Visual Basic and adapting software package already developed by software venders like ERP, CRM packages. There are researches regarding project risk factors for project management in the several point of views. And there are also researches regarding comparison between self-developing and adapting software packages methodology in IS project. However, there are no study on project risk factors comparison between self-developing IS using programming language and adapting software packages already developed by software venders in IS project. This research can be differentiated from previous ones, because it was considered both point of project risk management and development methodology in IS project. This research results implied meaningful messages to enterprise company to be planned IS projects and people who involved in IS projects. They should consider and need to prepare differently according to each development methodology for preventing project risks. It makes them reduce project risks in each case and complete successfully IS projects. Especially, if they have no experiences for implementing software packages, they can forecast the project risks and prepare them in advance.

• Journal of Information Technology Applications and Management
• /
• v.12 no.1
• /
• pp.213-229
• /
• 2005

Cost overrun or schedule delay of the software development project happens frequently despite that software developers continue to make every effort for the effective management of the projects. Previous researches have ascertained that these problems are ascribed to the uncertainty of projects and the improper management of the projects. The purposes of this research are to investigate the impacts of user participation and task interdependence on the performance of the projects and also to find out the appropriate project management method to improve the project performance. Even though the model fitness of the path model is proved to be very high, the verification of the hypotheses showed a variety of results including the four verifications and the one refutation of the hypotheses as well as the suggestion of one alternative hypothesis. The contribution of this research is that the integration model is proposed and verified, comprising the relationship among the user participation, the task interdependence, and the performance of software development projects. A project manager can utilize the implication of this research for an effective management of software development project.