Scope Flashcards
scope processes
plan scope mgmt collect requirements define scope create WBS validate scope control scope
product scope
features and functions of a product, service or result
project scope
WORK PERFORMED to deliver a product with the specified features and functions.
project scope is sometimes viewed as product scope
plan scope management
create scope management plan that documents how project & product scope will be defined, validated and controlled
plan scope management
benefit
provides guidance and directions on how scope will be managed
plan scope management
inputs
- project charter
- pmp: QUA, project life cycle description, development approach
plan scope management
TT
EDM
D: alternative analysis
plan scope management
outputs
scope management plan
requirements management plan
scope management plan
components
processes for
- preparing a proj scp statement
- For creating WBS
- How scope baseline will be approved and maintained
- How formal acceptance of deliverables will be obtained
requirements management plan
components
processes for:
- How requirements activities will be planned, tracked and reported
- Configuration mgmt activities: how to initiate changes to the product, service, or result, how to analyze the impact of the changes, and how to change approval authorization
- requirements prioritize process
- Metrics
- Traceability structure for the traceability matrix
collect requirements
determine, documenting and managing stakeholder needs and requirements to meet objectives
collect requirements
benefits
provide basis for defining product & project scope
collect requirements
inputs
- project charter
- pmp: scope management plan, requirements management plan, stakeholder engagement
- business case
collect requirements
TT
EDDD
- data gathering: BIFQB
- data representation: mind mapping
- data analysis
- Interpersonal & teams: facilitation
- Context diagrams
- Prototypes
collect requirements
outputs
- Requirements documentation
- Requirements traceability matrix
context diagrams
a scope model
Prototypes
obtain early feedback on requirements. providing a model of the expected product before actually building it. storyboarding
Requirements documentation
describe how individual requirements meet the business need for the project. requirements need to be measurable and testable
Requirements traceability matrix
a grid used to align requirements to the deliverables
a means to track requirements throughout the project life cyle
different types of requirements
- business
- stakeholder
- solution
- transition and readiness
- project
- quality
Tracing requirement includs
At a minimum, requirements can be traced to
business needs, project aims, project scope and WBS
deliverables, product design and development, testing,
and high-level requirements.
define scope
develop a DETAILED description of project & product
the process can be highly iterative
define scope
benefits
describe the boundaries and acceptance criteria
define scope
inputs
- project charter
- pmp: scope
- doc: requirements documentation
define scope
TT
E
Data analysis: alternative analysis
define scope
outputs
- project scope statement
- updates: requirements doc, requirement traceability matrix
project scope statement
typically includes
- Product scope description (progressively elaborated)
- Product acceptance criteria
- Project deliverables
- Project exclusions
- Project constraints & assumptions
what is & what is not, included in the project.
create WBS
the major deliverables are divided into smaller components that can be easily estimated (schedule and cost), managed, and controlled.
create WBS
benefits
provides a framework of what has to be delivered
create WBS
inputs
- pmp: scope
- project scope statement
- project requirement documentation
create WBS
TT
E
Decomposition
create WBS
outputs
scope baseline
work package
The smallest level of WBS work for which cost and schedule can be assessed and
administered
WBS components
- control accounts (may include 1 or more planning packages)
- planning packages
- work packages (the lowest level of the WBS).
100% rule: 100% of the work of a project (or program) needs to be represented in the WBS
WBS & components
Any unit of work defined in the WBS:
- control accounts (may include 1 or more planning packages)
- planning packages
- work packages (the lowest level of the WBS).
100% rule: 100% of the work of a project (or program) needs to be represented in the WBS
validate scope
secure sign-off (formal acceptance) of the project scope at logical intervals ((each milestone, each deliverable, etc)
ACCEPT DELIVERABLES
validate early and validate often
validate scope
inputs
- pmp: scope,
- requirements mgmt plan
- scope baseline
- verified deliverables
validate scope
TT
inspection
voting
validate scope
outputs
accepted deliverables
change requests
control scope
monitor the status of project & product scope
manage changes to the scope baseline
control scope
benefit
maintain scope baseline
control scope
inputs
- pmp: scope requirements management plan scope baseline -docs: requirements doc, requirement traceability matrix
control scope
TT
VT
variance analysis
trend analysis
control scope
outputs
work performance info
change requests
scope/schedule/cost baseline updates
performance measurement baseline
