Scope Flashcards
What is the definition of scope management?
Defining what work is required and then making sure all of that work—and only that work—is completed
What is the difference between product scope and project scope?
Product scope refers to the requirements related to the product, service, or result of the project, while project scope involves the work the project team will do to deliver the product of the project
What is timeboxing?
An agile planning tool using short, fixed periods of time set for the team to complete a selected and prioritized set of activities
Describe the purpose of a minimal viable product (MVP).
On an agile project, it allows the customer to take delivery of the product and use it while the team continues to build the rest of the product
Also known as minimal marketable features (MMFs)
Describe what scope management looks like on a predictive project.
Develop a plan for how to plan, validate, and control scope and requirements.
Determine requirements.
Analyze and balance stakeholder needs to determine scope.
Create a WBS to break the scope down to smaller, more manageable
pieces. Define each piece in a WBS dictionary.
Obtain validation (signed acceptance) that the completed scope of work is acceptable to the customer or sponsor.
Measure scope performance and adjust as needed.
Describe what scope management looks like on an agile project.
Requirements are identified and documented at a sufficient level of detail so they can be prioritized and estimated at a high level.
The product’s features are kept in a list called the product backlog.
The work is broken into product releases.
For each release, the work is completed through iterations.
The work of each iteration (and release) is defined successively in more detail just before the work for each iteration begins.
How is product scope different for agile projects than it is for plan-driven projects?
Product scope is typically more flexible in agile projects
What artifacts result from the Plan Scope Management process?
Scope management plan
Requirements management plan
What is the difference between a product backlog and a product roadmap?
A product backlog is a list of the functional and nonfunctional work identified for the project, while a product roadmap is a visual representation of the product’s main components, broken into sequential product releases
What is the difference between eliciting requirements in a predictive environment versus an adaptive environment?
Predictive environment: A missed requirement early in the project could mean significant changes and conflict throughout the remainder of a project
Adaptive environment: Agile teams initially define requirements at a high level and then progressively refine them, helping to avoid or lessen the effect of change requests
Name several requirements-gathering techniques.
Brainstorming
Interviews
Focus groups
Questionnaires and surveys
Benchmarking
Voting
Multicriteria decision analysis
Affinity diagrams
Mind maps
Nominal group technique
Observation
Facilitation
Context diagrams
Prototypes
What artifacts should a project manager look at to resolve competing requirements?
Competing requirements can be resolved by accepting those that best comply with the:
Business case
Project charter
Scope statement
Known project constraints
What are some ways requirements can be verified?
Meetings
Prototypes
Iteration reviews
What are acceptance criteria?
Criteria used to ensure the project meets stakeholder requirements
What is the value of a requirements traceability matrix?
Helps link requirements to objectives and/or other requirements to ensure the strategic goals are accomplished
What is product analysis?
A method of analyzing the objectives and description of the product as stated by the customer or sponsor
What is the key artifact of the Define Scope process?
Project scope statement
What are the key items included in a project scope statement?
Product scope
Project scope
List of product deliverables
Acceptance criteria
What is not part of the project?
Assumptions and constraints
When is a work breakdown structure (WBS) created, and what is it used for?
Created during project planning by the team and used to define or decompose the project into smaller, more manageable pieces
Graphically provides a structured vision for a project and helps ensure that nothing is missed and no deliverables are forgotten
How are work packages different from activities?
Work packages are deliverables (things), rather than actions (activities)
Work packages are shown in a WBS
Activities are shown in an activity list and network diagram
What is a WBS dictionary?
Documentation providing details needed to build each work package
What makes up the scope baseline?
Project scope statement
WBS
WBS dictionary
Describe scope decomposition on an agile project.
High-level requirements are gathered at the beginning of the project.
Features are created from large and complex, high-level requirements.
Medium-level requirements are broken into smaller stories.
Each story needs to be broken further by various types of requirements.
What is MoSCoW analysis?
A breakdown method of higher-level requirements at the release map and product (feature) backlog levels
MoSCoW stands for “Must have, Should have, Could have, and Would like to have,” and is a prioritization scheme for selecting features and functionality
What is the Validate Scope process?
When is it done?
The process of gaining formal acceptance of the deliverables by the customer or sponsor
Done during project monitoring and controlling and at the end of each phase of the project life cycle
What key artifacts result from the Validate Scope process?
Work performance information
Change requests
Accepted deliverables
Updates to project management plan and project documents
What are some methods for controlling and validating scope?
Predictive:
Inspection
Data analysis
Decision making
Adaptive:
Agile ceremonies
Customer-valued prioritization
Incremental product delivery
