Scope management represented by "Service Statement"(PM Case)

Bibliographic Information

Other Title
  • サービス仕様書を中心としたスコープマネジメント(我が社のPM事例)
  • 我が社のPM事例 サービス仕様書を中心としたスコープマネジメント
  • ワガシャ ノ PM ジレイ サービス シヨウショ オ チュウシン ト シタ スコープ マネジメント

Search this article

Abstract

Many IT system projects go wrong by the difference in the recognition to the scope between the vendor and the customer. It is difficult to determine all requirements of a project including development of business application software during estimating and contract negotiation. A project will surely result in failure if the reasons and assumptions of estimation are left ambiguous and unauthorized. Unless the products and work assignments are established as the baseline of project scope, failure will occur indeed. To avoid or to mitigate such problems, it is effective to make a "Service Statement" for a scope statement which describes the scope definition of vender's services provided for a customer at the stage of contract.

Journal

Details 詳細情報について

Report a problem

Back to top