LSUS MBA 742 Module 2 Study Guide
Exam with Actual Answers 2025-2026
Updated.
Product Scope - Answer The features and functions that characterize a product, service
or result.
Project Scope - Answer The work performed to deliver a product, service, or result with
the specified features and functions. The term project scope is sometimes
viewed as including product scope.
Scope Baseline - Answer The approved version of a scope statement, work breakdown
structure (WBS), and its associated WBS dictionary, that can be changed only
through formal change control procedures and is used as a basis for comparison.
WBS - Answer Work Breakdown Structure
Scope Change - Answer Any change to the project scope. A change almost always requires an
adjustment to the project cost or schedule
Scope Creep - Answer The uncontrolled expansion to product or project scope without
adjustments to time, cost, and resources
Scope Management Plan - Answer A component of the project or program management
plan that describes how the scope will be defined, developed, monitored, controlled, and
verified.
Requirements Management Plan - Answer A component of the project or program
management plan that describes how requirements will be defined, developed, monitored,
controlled, and verified.
Decomposition - Answer A technique used for dividing and subdividing the project scope
and project deliverables into smaller, more manageable parts
Requirements Traceability Matrix - Answer A grid that links product requirements from their
origin to the deliverables that satisfy them
, 6 Scope Management Processes - Answer •Plan Scope Management
•Collect Requirements
•Define Scope
•Create WBS
•Validate Scope
•Control Scope
Glod Plating - Answer When a project team delivers more than what is expected based on
the product/project scope.
Usually requires more time and cost to deliver.
Outputs of the Scope Management Plan Processes - Answer Scope Management Plan
Requirements Management Plan
Key Benefit of Plan Scope Management Process - Answer Provides direction on how to
manage scope throughout the project.
Key Benefit of Collect Requirements - Answer Provides a basis to define and manage project
and product scope.
Outputs of Collect Requirements Process - Answer Requirements Documentation
Requirements Traceability Matrix
Benchmarking - Answer Benchmarking is the comparison of actual or planned practices,
such as processes and operations, to those of comparable organizations to identify best
practices, generate ideas for improvement, and provide a basis for measuring performance
Context Diagrams - Answer A visual depiction of the product scope showing a business
system(process, showing a business system (process, equipment, computer system, etc.), and
how people and other systems (actors) interact with it.
Observations (AKA "Shadowing") - Answer A technique that provides a direct way of viewing
individuals in their environment performing their jobs or tasks and carrying out processes.
Prototypes - Answer A method of obtaining early feedback on requirements by providing a
working model of the expected product before actually building it.
Exam with Actual Answers 2025-2026
Updated.
Product Scope - Answer The features and functions that characterize a product, service
or result.
Project Scope - Answer The work performed to deliver a product, service, or result with
the specified features and functions. The term project scope is sometimes
viewed as including product scope.
Scope Baseline - Answer The approved version of a scope statement, work breakdown
structure (WBS), and its associated WBS dictionary, that can be changed only
through formal change control procedures and is used as a basis for comparison.
WBS - Answer Work Breakdown Structure
Scope Change - Answer Any change to the project scope. A change almost always requires an
adjustment to the project cost or schedule
Scope Creep - Answer The uncontrolled expansion to product or project scope without
adjustments to time, cost, and resources
Scope Management Plan - Answer A component of the project or program management
plan that describes how the scope will be defined, developed, monitored, controlled, and
verified.
Requirements Management Plan - Answer A component of the project or program
management plan that describes how requirements will be defined, developed, monitored,
controlled, and verified.
Decomposition - Answer A technique used for dividing and subdividing the project scope
and project deliverables into smaller, more manageable parts
Requirements Traceability Matrix - Answer A grid that links product requirements from their
origin to the deliverables that satisfy them
, 6 Scope Management Processes - Answer •Plan Scope Management
•Collect Requirements
•Define Scope
•Create WBS
•Validate Scope
•Control Scope
Glod Plating - Answer When a project team delivers more than what is expected based on
the product/project scope.
Usually requires more time and cost to deliver.
Outputs of the Scope Management Plan Processes - Answer Scope Management Plan
Requirements Management Plan
Key Benefit of Plan Scope Management Process - Answer Provides direction on how to
manage scope throughout the project.
Key Benefit of Collect Requirements - Answer Provides a basis to define and manage project
and product scope.
Outputs of Collect Requirements Process - Answer Requirements Documentation
Requirements Traceability Matrix
Benchmarking - Answer Benchmarking is the comparison of actual or planned practices,
such as processes and operations, to those of comparable organizations to identify best
practices, generate ideas for improvement, and provide a basis for measuring performance
Context Diagrams - Answer A visual depiction of the product scope showing a business
system(process, showing a business system (process, equipment, computer system, etc.), and
how people and other systems (actors) interact with it.
Observations (AKA "Shadowing") - Answer A technique that provides a direct way of viewing
individuals in their environment performing their jobs or tasks and carrying out processes.
Prototypes - Answer A method of obtaining early feedback on requirements by providing a
working model of the expected product before actually building it.
