Abstract
Many IT system projects go wrong by the difference in the recognition to the scope between the vendor and the customer. It is not only because the customer cannot present detailed requirements at the time of estimate or contract negotiation, but also because many vendors in Japan often show an infeasible estimate by ambiguous expression owing to severity of bidding competition. By exchanging the scope statement which describes the scope definition of the services with which the vendor provides the customer, it is possible to aim at avoidance or mitigation of this problem. This paper concretely describes the contents and effects of the scope statement.
