Scope Managment Flashcards
Who is responsible for developing the scope baseline?
The project team - after obtaining input from customer and other stakeholders
The scope statement…
Must be precise and can be quite detailed
Constraints may be listed in…
The scope statement
The assumptions log
in a separate constraints log
The Scope Statement includes 3 parts
Description of the project and product scope
Deliverables
Assumptions and constraings
The Detailed Scope Statement includes…
Product scope description
Deliverables
Acceptance criteria
Exclusions
Which reviews does a scope statement undergo?
A preliminary review
Later on, a final review
Who approves the product scope?
Customers (i.e. their requirements), but do not generally approve the project scope (what you are going to do to complete their requirements).
What is the difference between Requirements, Perform Quality Control, and Validate Scope?
Requirements - used to measure the completion of a project. If you don’t have complete requirements then you can’t measure whether the project is complete.
Perform Quality Control - checks for correctness (like QA testing)
Validate Scope - checks for acceptance (customer checks that finished product fully meets requirements)
Who needs to know if there is a change in the project or product scope at any time during the project?
The customer - who can then make an informed decision (or at least provide input to the project team.
A WBS is developed by the team, but is used to communicate with all stakeholders
- The most valuable result of WBS is team buy-in
- WBS also helps prevent work from falling through the cracks. Conversely, it avoids gold-plating projects
What is a context diagram and when do you use it?
It’s a visual depiction of the product scope showing a business system (process, equipment, computer system, etc.), and how people and other systems (actors) interact with it. Examples - PBMN diagrams and other flow charts used by business analysts.
You use it during Collect Requirements
What is a vital scoping tool for project scope?
Work Breakdown Structure (WBS)
Code of Accounts
Unique IDs in WBS
Control Accounts
Higher level than work packages and are figured out in Schedule Management during Define Activities (post creation of WBS)
What would cause someone to have difficult estimating cost?
Lack of scope definition
