Level 6 Level 8
Level 7

Project Scope Management


42 words 0 ignored

Ready to learn       Ready to review

Ignore words

Check the boxes below to ignore/unignore words, then click save at the bottom. Ignored words will never appear in any learning session.

All None

Ignore?
collect requirements
process of defining and documenting stakeholder needs to meet the project objectives
define scope
detailed description of project and product
product scope
features and functions of a product or service or result
project scope
work that needs to be accomplished to deliver product with features charter has established
collect requirements
inputs: project charter, stakeholder register
stakeholder register
information about who is an appropriate stakeholder
collect requirements
tools and techniques: interviews, focus groups, facilitated workshops, group creativity techniques, group decision making techniques, questionnaires, surveys, observations and prototypes
group creativity
techniques: brainstorming, mindmapping, affinity diagrams
prototype
technique to use a working model to generate early feedback
Delphi
technique to get anonymous (or unbiased) expert consensus
affinity diagram
technique: collect ideas on cards, look for related ideas, sort in to groups
collect requirements
outputs: requirements documentation, requirements management plan, requirements traceability matrix
requirements documentation
documentation: business need, project objectives (for traceability), functional requirements, non-functional requirements, acceptance criteria, impacts, support or training requirements
functional requirements
business processes, product interaction, text or models
non-functional requirements
levels of service, performance, safety
requirements management plan
how requirement activities will be planned, tracked and recorded, configuration management activities, prioritization, product metrics, traceability structure
define scope
inputs: project charter, requirements documentation, OPA (template for scope statement, archived information from previous similar projects)
project charter
high level project description, approval requirements
define scope
tools and techniques: expert judgement, product analysis, alternatives identification, facilitated workshops
product analysis
product breakdown, systems analysis/engineering, value analysis/engineering
alternatives identification
brainstorming, lateral thinking, pair wise comparisons
define scope
outputs: project scope statement, project document updates
project scope statement
product scope description, product acceptance criteria, project deliverables, project exclusions, project contraints (pre-defined budget, imposed dates or schedule milestones)
work package
80 hour work package rule or less (some use 40)
WBS
basis for all scheduling, costs, performance measurement
WBS
tool and technique: decomposition
decomposition
breaking down work into smaller components to visualize work that needs to be completed
work package
lowest level on a WBS
WBS
does not show dependencies, but uses identification codes
create WBS
outputs: WBS, WBS dictionary, scope baseline, project document updates
WBS dictionary
code of account identifier, schedule activities, resources required, cost estimates, technical references, contract information, scope baseline, project document updates
WBS
other name for project breakdown structure (PBS)
BOM
describes physical items required for project
RBS
breaks down work by human resource factors
OBS
breaks down work components by organization factors
CWBS
defines level of reporting between buyer and seller, used to determine assignments and manage the work
scope baseline
The sum of the project deliverables
WBS
The deliverable oriented, hierachical, decomposition of the work executed by the team
inspection
number one way to verify scope
inspection
measuring, examing and verifying to determine if the product follows the acceptance criteria (stakeholder, customer, sponsor)
verify scope
outputs: accepted deliverables, change requests, product document updates
control scope
work performance measurements, OPA updates (causes of variances, correct actions chosen and resons), change requests, project management plan updates (baseline updates), and project document updates