Abstract
It is sometimes seen that a project results in failure due to an accident derived from a problem coming to light shortly before the closing of the project. Delay in problem detection raises the possibility of not only decreasing the time left for problem solving but also having a big influence on the whole project. It is thought the detection of the problems at the early stage is very important for the project success. "Was not the problem able to be detected at an earlier stage?" is often discussed as a lesson learned when the project was completed. Although the progress and pending problem are reported at each meeting with the project members, the project status is not always correctly reported to the project manager because the report unconsciously becomes superficial in the fear of being scolded for a mistake or the report is sometimes inadequate due to low awareness of the reporter, etc. The author wonders whether there are difficulties in the usual methods to confirm the progress, and investigates how to detect problems more appropriately in earlier stage. The method is practically attempted and its effectiveness is evaluated.
