SAB11#39_Define_Scope

SAB11#39_Define_Scope

1. Concerned with what is and is not included in the project and its deliverables

   • The planning is iterative
   • this process uses the scope management plan
     • the requirements documentation
     • requirements process
     • the project charter
     • additional information :assumpytions and constrains
     • Scope management plan
     • OPAs
   • When the requirements have been determined
     • The result is a realistic schedule and budget that can achieve the project´s agreed-to scope
       •  if the resulting schedule and budget do not meet the sponsor´s or management´s expectations for the project, the project manager needs to balance then requirements (scope) against the budget, schedule, and the others constraints in the project 
       • Unrealistic schedules are the project manager´s fault because then haven´t done planning in an iterative way
       • project managers spend a large portion of their time, looking for options to adjust the project and still meet the project schedule or budget
         • while the work is being done Tools: 1.negotiating scope  2.fast tracking
       • the processes of define scope will continue as the project progresses, and will be iterated. Regardless of when this process is performed, its purpose is always to determine what scope is and is not in the project
   • The planning is iterative

2. Product analysis

   • Analyze the objectives and description of the product stated by the customer or sponsor and turn then into tangible deliverables.
   • Product analysis is a critical tool that allows the project manager to make sure the product and project scope are understood and accurate

3. Project scope statement

   • can take a lot of time and involve the expert judgment of many stakeholders and even experts from outside the origanization
     • The expert judgment
   • you should identify areas where people requested scope but it was not approved to be included in the project
     • The project scope statement
       • The project scope statement tells you what you have to do
       • Product scope
       • Project scope
       • Deliverables( for the product and the project)
       • Acceptance criteria
       • what is not part of the projec
       • Assumptions asn constrains
       • Project documents updates
   • identify in the project scope stament what is not in the project to make it clear that such additions are nor allowed

4. Facilitated workshops

   • You need to make sure thah what you´re delivering really meets then needs of the stakeholders
   • Write down specific project goals that you can measure, which makes it a lot easier for the team to plan for the work they have to do.

Bilder und Dateien der Mindmap