Pages

Saturday, July 23, 2011

Strengthening the Boundaries with Scope Statement

When you have all the requirements documented, it is time to confirm the boundary of the project. If you remember, in Project Charter, we have a high level listing of the things that will be done in the project, and the things which are out of the scope.

In the Process Group: Define Scope, we will make a more detailed description of the project and the product to be delivered. With the additional information that we have collected during the requirements gathering activities, we are now able to include more information related to risks,quality, assumptions and constraints.

scope

To be able to come out with the project scope statement, we will need the high level information from the Project Charter and detailed requirements from the requirements documentation. We will need to extract the necessary information to come out with the scope statement.

For this process group, PMI identifies four tools and techniques that could be used to facilitate the process. They are:

  • Expert Judgment
  • Product Analysis
  • Alternative Identification
  • Facilitated Workshop

A scope statement will include amongst others, the following aspects, described in detailed to ensure the work to be performed is defined correctly”

  • Product scope description
  • Product acceptance criteria
  • Project deliverables
  • Project exclusions
  • Project constraints

No comments:

Post a Comment