Abstract
In IT projects, it is difficult for project managers to know the status of progress, quality, and risks correctly, because the software products are basically invisible. Particularly in troubled projects, serious problems are often not identified as risks in advance. In such projects, risks cannot be avoided and are actualized as critical problems. Therefore it is important to visualize the status of the project. This paper reports the effects of applying the "visualization" management methods to an ongoing IT project.
