Abstract
Premises, such as short time for delivery, a continued functional change demand, practical use of newest IT technology, and reduction of customer's organization, are imposed on the systems development project of these days in many cases. While the demand to a system develops, in order to carry out such a project, it is becoming impossible to cope with it only by the project management by QCD on condition of the old waterfall type development technique. In this paper, the case is reported about how specification decision and subsequent change management were performed, and how the project was carried out, and the method of project management is reviewed from a viewpoint of modern PM. In the project concerned, the following techniques were taken and practiced as practical solution. (1) Planning of the development schedule consisted on two phases (2) Change management linked to the risk management The first effect caused by the above-mentioned technique was we've easily got consensus with our customers when we wanted specifications fixed. Since the development schedule was consisted of two phases overlapped, compared with shingle-line schedule, they were able to make decision more easily. Moreover, it became easy to share the risk items among stakeholders. So, we could take proper actions within time of a margin for risk, when risk item became actual specification change demand. The two-phases development method is a kind of parallel development method, and the work burden in fields, such as progress management, man-hour control, and a quality control, becomes large for a project manager. However, I feel the merit beyond it and want to continue to tackle as one of the practice methods of risk management.
