SAB4#39_Define scope

SAB4#39_Define scope

1. Organizational process assets

   • Documents, templates and forms.

2. Project charter

   • It tells you the business needs, and who your sponsor and stakeholders are.

3. Requirements documentation

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

4. Scope management plan

   • It’s where you keep all the work you did to plan out how you’ll collect scope information and monitor and control your scope through the project.

5. Facilitated workshops

   • You need to make sure that what you’re delivering really meets the needs of the stakeholders.
   • Quantifiable goals
     • That means writing down specific project goals that you can measure

6. Product analysis

   • This tool is all about turning those things into project work that needs to be done.

7. Alternatives generation

   • Think of other ways that you could do the work. Exploring different ways to do the work will help you find the one that is most efficient for the project.

8. Expert judgment

   •  Bring in an expert to help you define what work needs to be done.

9. Project Scope Statement

   • Product scope description
   • Project exclusions
     • This means looking for all the work the project DOESN’T include.
   • Project deliverables
     • The deliverables listed here are EVERYTHING the project creates
   • Project Constraints & Assumptions
     • Constraints are known limitations. Assumptions are things you think are true.

10. Project document updates

    • It has to do with change control