• Asia pacific journal of information systems
• /
• 제6권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
• /
• 제12권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.

• 한국IT서비스학회지
• /
• 제7권3호
• /
• pp.129-144
• /
• 2008

The uncertainty of software projects makes a big gap between the initial schedule/expense and the final one. Moreover, it is difficult for a project manager to reschedule and re-budget for reflecting the effects of changes in the software development. In this paper, we suggest EVM (Earned Value Management) to control the schedule and the expenses of an on-going software development project. In order to apply EVM to a software project, we consider turnkey contracts and propose the way to calculate the earned value for the software development. Finally, we illustrate our method with the case of N-company. We expect our EVM help to analyze and to predict the final schedule and the expense of a software development project.

• Asia pacific journal of information systems
• /
• 제13권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.

• 한국정보시스템학회지:정보시스템연구
• /
• 제16권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
• /
• 제11권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.

• 한국정보시스템학회지:정보시스템연구
• /
• 제13권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.

• 한국IT서비스학회지
• /
• 제13권2호
• /
• pp.195-217
• /
• 2014

This paper has explored when implementing SW development project of the IT service corporations, what factors affect its productivity in SW development methodology. The importance of the AHP analysis surveyed from the experts in IT service companies and related committee, was shown in the order of the following processes : 1) Deployment process 2) Management process 3) Establishment process. It is measured the methodology levels of establishment, deployment and management in each project using the survey results collected from project execution members and analyzed the productivity of projects that have been executed within 2 years. Using project methodology level, productivity correlation analysis, and regression analysis, this study confirms that the methodology deployment level brings positive effects significantly to SW development productivity. The significance of this study would be not only to research and analyze SW development productivity using the real project execution data but also to underline the necessities and the importance of steady research, deployment and support for SW development productivity improvement.

• 한국IT서비스학회지
• /
• 제10권4호
• /
• pp.191-204
• /
• 2011

Recently, many software companies are trying to improve the software quality and project outcome with more costs and efforts in development time. In the software convergence and integration environments, it is required efforts to gain high quality of software. In other words, it is required to utilize software engineering knowledge and technology for higher software quality and better software project productivity. The Software development productivity can be varied by software process capability according to building a framework for software development, selection and use of appropriate technology, human resource management. Software process capability will influence software project outcome which is the general opinion. This study provides empirical evidence about software engineering efforts and investment approach to lead software project performance. We measured the software engineering efforts by SW engineering level and analyzed the corelation between software engineering level and schedule deviation. And, we verified that this performance is affected by the size of software company. As a result, software process capability is important to build a infrastructure and develop systematically software project. The higher software engineering level can lead to improved software project performance.

• 한국컴퓨터정보학회논문지
• /
• 제16권12호
• /
• pp.113-120
• /
• 2011

정보시스템 구축 프로젝트의 복잡성과 규모가 점차 커지면서, 프로젝트가 실패하는 경우가 발생한다. 프로젝트의 실패의 원인을 분석해보면 사용자의 프로젝트 이해 부족, 불명확한 요구사항 및 요구사항변경 등으로 소프트웨어 개발 생명주기 중 요구사항 분석 단계에서 대부분의 원인을 찾을 수 있다. 본 논문은 소프트웨어 개발 프로젝트에서 요구분석을 통해 도출된 기능과 변경요구 기능간의 추적 등 개발 생명주기 전체 기간 동안 지속적인 요구사항 변경 관리가 가능하게 하는 도구를 설계하였다. 그리고 프로젝트 관련자들 사이에서 충분한 합의와 협의를 통해 공통의 이해를 구축하는 효과적인 의사소통을 지원하는데 필요한 기능에 대해 논의한다.