Abstract
Reasons for failed system development projects may include inaccurate estimation and failure in the selection of software architecture. In addition, they may also include other unconsidered risks. In order to avoid failed projects resulting from these reasons, at NTT Data Corp., we perform reviews and take support measures over a wide range. When these measures are taken, however, as of starting the project formally, most matters have been already determined and cannot be changed; therefore, suggestions or advice through these measures do not function effectively, resulting in insufficient reduction of potential risks in some cases. In this paper, in order to avoid such cases, we will propose how to get a complete picture of a project earlier at the launch of the project and take various measures in a timely fashion. Specifically, registration of project information upon study of the project can help the Measures Promotion Dept. grasp the outline of the project to take various measures at just the right time. With this approach, we could successfully prevent often-repeated oversights when putting the complete picture of the project together.
