SAB#39_DEFINE_SCOPE_OK

SAB#39_DEFINE_SCOPE_OK

1. The define scope process is primarily concerned with what is and is not included in the Project and its deliverables

   • The process of define scope will continue as the Project progresses and will be iterated. Regardless of when this process is performed, its purpose is a always to determine what scope is and is not in the Project.

2. PROJECT CHARTER

   • You’ll need this because it tells you the business needs, and who your sponor and stakeholders are.

3. REQUIREMENTS DOCUMENTATION

   • All of those requirements you collected are an input to Define Scope.

4. SCOPE MANAGEMENT PLAN

   • You’ll keep referring to the Scope Management plan through all of the Scope Management processes

5. ORGANIZATIONAL PROCESS ASSETS

   • Just like with the Scope Management plan, templates and forms will help save you time.

6. FACILITATED WORKSHOPS

   • They find out from the stakeholders what they need to know about the project and the scope of the product, this ensures that the product is what the stakeholders really want.

7. PRODUCT ANALYSIS

   • Once the work is complete, you're going to have to make sure that you're delivering matches what you put in your requirements

8. ALTERNATIVES GENERATION

   • Think of other ways that you could do the work

9. EXPERT JUDGMENT

   • You’ve seen this one before! Bring in an expert to help you figure out what work needs to be done.

10. PROJECT SCOPE STATEMENT

    • After you have done your scope planning, figured out as much as you could using stakeholder and product analysis, and identified all of the possible ways of doing the work, you should be ready to add any new findings to the project scope statement
    • Product Scope Description
    • Project Exclusions
    • Project Deliverables
    • Project Acceptance Criteria
    • Project Constraints
    • Project Assumptions

11. PROJECT DOCUMENT UPDATES