Abstract
In recent years, it is an important task to control addition and/or change of requirement that occurs repetitively throughout IT development project. In this paper, as a solution to such addition and/or change of requirement, "non-phased requirement definition" is introduced, and project management technique to put it into practice is explained. While discussing about addition and/or change of requirement, Preliminary Project Scope Statement process and Close Project process should be done considering about the Project Close (as Integration). By this planning, gathering accurate information and making precise investing decision become feasible, and the fact that flexible response could be made against sudden addition and/or change of requirement throughout the project is confirmed.
