Scope Management Flashcards
1
Q
Plan Scope Management Sub-Process Output
A
- Scope Management Plan
- Requirements Management Plan
2
Q
What is a “Requirements Management Plan”
A
- Output from “Plan Scope Management” sub-process
- Guiding document for how requirements will be documented and managed:
- Includes a traceability matrix
3
Q
Plan Scope Management Sub-Process Inputs
&
Purpose
A
- Charter (High level requirements)
- Project Management Plan; Affects how you write the scope mgmt plan
- Quality Management Plan
- Project Life Cycle description
- Development Approach
- EEF (Regulations, and Risk appetites)
- OPA (Templates)
4
Q
Scope Management Plan Purpose
A
Guiding document for:
- Defining Scope
- Create WBS (~developing the scope)
- Validate Scope (~approval)
- Control scope (~change requests)
5
Q
Definition of Project Scope
A
- The work that is needed to be accomplished in order to deliver a product, service, or result w/ specified features and functions
6
Q
Definition of Product Scope
A
- The features and functions that characterize a product, service, or result
7
Q
Collect Requirements Sub-Process Output
A
- Requirements Documentation
- Requirements Traceabiilty Matrix
8
Q
Inputs for Collect Requirements Sub-Process
& Purpose
A
- Project Charter (High-level requirements)
- Project Management Plan Components:
- Scope Management Plan
- Requirements Management Plan (which and how to use tools for this process)
- Stakeholder Engagement Plan
- Project Docs:
- Assumption Log (which reqs not included)
- Lessons Learned Register (reqs ~ projects)
- Stakeholder Register
- Business Docs:
- Business Case
- Agreements; Buyer may set forth requirements
9
Q
Collect Requirements Sub-Process Tools/Techniques
A
- Expert Judgement
- Data Gathering: brainstorming/interviewing/focus groups/questionnaires & surveys/Bench Marking
- Data Analysis: Analyzing documents, agreements, policies, proposals, or business plans
10
Q
Describe “Requirements Documentation”
A
- 1 of 2 outputs from “Collect Reqs” sub-process
- Details project objectives:
1) Includes stakeholder/business reqs.
2) Acceptance Criteria
3) Quality Requirements
4) Organizational Impacts of the requirements
5) Legal/Ethical Compliance requirements
6) Requirements Assumptions & Constraints
11
Q
Describe “Requirement Traceability Matrix”
Where does it come from?
A
- 1 of 2 outputs from “Collect Reqs.” sub-process
- Links requirements back to the scope
- Used to help manage scope
- Describes
- who provided the requirement
- why the requirement was added
- the current status of the requirements
12
Q
Define Scope Sub-Process Output
A
- Scope Statement
- Updated Project Docs (Assumption Log, Reqs. Doc., Reqs. Traceability Matrix, Stakeholder Register)
13
Q
Define Scope Sub-Process Inputs & Why
A
- Project Charter; contains reqs.
- PMP (Scope Management Plan); how to doc.
- Proj. Docs:
- Assumption Logs; scope statement includes assumptions
- Reqs. Doc.; Details the requirements
- Risk Register; risk affects scope
- EFA; risk appetite and organizational culture
- OPA; previous lessons learned, templates
14
Q
What is Product Analysis?
A
- Tool & Technique for “Define Scope” sub-process
- detailed understanding of project’s product, service, or result
- allows focus on correct interpretation of requirements
- Examples: Product breakdown, system analysis, system requirements
14
Q
What is Product Analysis?
A
- Tool & Technique for “Define Scope” sub-process
- detailed understanding of project’s product, service, or result
- allows focus on correct interpretation of requirements
- Examples: Product breakdown, system analysis, system requirements
15
Q
What does a “Scope Statement” contain?
A
- Define scope sub-process output
- Lists deliverables
- Lists acceptance criteria
- Lists constraints & exclusions
16
Q
“Create WBS” Sub-Process Outputs (tricky)
A
- Scope Baseline which is not one document
- Synthesized from Scope Statement, WBS, and WBS Dictionary
- Project Documents Updates (Assumption Log, Reqs. Documentation)
17
Q
What is a “WBS”?
A
- A decomposition of the deliverables from the scope statement into manageable components or work packages
- Does not include the work required to create those deliverables
18
Q
What is a “WBS Dictionary”?
A
Details:
- Time estimates
- Cost estimates
- Account info
- Work packages
- Owners
- Milestones
- Details of taskss
19
Q
“Create WBS” Sub-Process Inputs & Why
A
- PMP/Scope Management Plan; how-to guide
- Project Docs/Scope Statement; lists deliverables
- Requirements Documentation; need details for “WBS Dictionary”
20
Q
“Validate Scope” Sub-Process Inputs & Why
A
- PMP: Scope Mgmt, Reqs. Mgmt, Scope Baseline; how to & reference points for comparison
- Proj. Docs: Lessons Learned, Reqs. Doc., Quality Reports, Traceability Matrix; in case change requests and quality improvement suggestions
- Verified Deliverables
- Work Performance Data; used to create information
21
Q
What is Inspection?
A
- Tool/Technique for measuring, examining, testing, and verifying a deliverable for acceptance
- Also called product review, audit, or walkthrough
22
Q
“Validate Scope” Sub-Process Outputs
A
- Accepted deliverables
- Change requests
- Work Performance Information; update status on deliverable
- Project Docs. Updates; Update lessons learned, Requirements Documentation, and traceability matrix
23
Q
“Control Scope” Sub-Process Inputs & Why
A
- PMP: Scope Mgmt., Req. Mgmt., Change Mgmt, Config Mgmt.,Scope Baseline, Performance Measures; All help variance analysis
- Project Docs: Lessons Learned, Reqs. Doc., Req. Traceability Matrix;
- Work Performance Data; status of what got done to be compared with baseline, the comparison
- OPA
24
Q
“Control Scope” Tool/Techniques & Method Choice
A
- Data Analysis:
1) Variance analysis - C.p. planned work vs actual work has variance against the baseline
2) Trend Analysis - Performance of scope over time
25
Q
“Control Scope” Sub-Process Output
A
- Work Performance Information (planned vs actual)
- Change Requests if variance unaccceptable
- PMP Updates: May update Scope Mgmt Plan, All 4 baselines
- Project Doc Updates: Lessons Learned, Reqs. Documentation, Performance Baseline Measures
