SAB10#41_#42_#43_Scope

SAB10#41_#42_#43_Scope

1. Project Scope

   • All the work that needs to be done to make the product
   • To determine if it is completed, the work accomplished is measured against the scope baseline
     • Project Management Plan

2. Product Scope

   • Features and functions of the product or service that you and your team are building
   • To determine if it is achieved, it is compared with the requirements
     • Requirements documentation
     • Project scope statement

3. Advices

   • Any change to scope must be evaluated for its effect on time, cost, risk, quality, resources and customer satisfaction
   • No changes to scope are allowed without an approved change request
   • Scope changes should not be approved if they relate to work that does not fit within the project charter
   • Yo need to continuously determine what is and is not included in the project
   • Creating the project Scope Baseline happens after the WBS

4. WBS

   • Decomposition
     • IS created with the help of the team
     • Each level is a smaller piece of the previous level
     • The entire project is included in the highest levels
     • Some levels will be broken down further than others
     • Includes only deliverables that are required for the project
     • Deliverables not included are not part of the project
     • The team breaks down the WBS untill work packager are reached
       • Deliverables are really and confidently estimated
       • Deliverables can be completed quickly
       • Can be completed without interrumption (for more information)
       • May be outsourced or contracted out

5. Documents

   • Project Scope Statement
   • WBS
     • Does not show the order of the work or any dependencies
   • WBS Dictionary
   • Scope Management Plan
   • Requirements

6. Scope Creep

   • Uncontrolled changes that cause the team to do extra work