MBA 742 Module 2 Latest Exam
Questions and All Correct Answers.
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.
The two outputs of the Plan Scope Management plan process are: - Answer Scope
Management Plan and Requirements Management Plan
, The process of creating a scope management plan that documents how the project scope will
be - Answer •defined,
•validated, and
•controlled.
Collect Requirements Process - Answer The process of determining, documenting, and
managing stakeholder needs and requirements to meet project objectives.
The key benefit of the Collect Requirements process is - Answer that it provides a basis to
define and manage project and product scope.
The two outputs of the Collect Requirements process are: - Answer Requirements
documentation and 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.
Questionnaires and surveys - Answer Written sets of questions designed to quickly
accumulate information from a large number of respondents.
Requirements Documentation - Answer A description of how individual requirements meet
the business need for the project.
Scope Process - Answer The process of developing a detailed description of the project and
the product.
Risk Register - Answer The risk register contains response strategies that may affect the
project scope, such as reducing or changing project and product scope to avoid or mitigate a
risk. We will be discussing risk and risk management in more detail in later modules.
Questions and All Correct Answers.
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.
The two outputs of the Plan Scope Management plan process are: - Answer Scope
Management Plan and Requirements Management Plan
, The process of creating a scope management plan that documents how the project scope will
be - Answer •defined,
•validated, and
•controlled.
Collect Requirements Process - Answer The process of determining, documenting, and
managing stakeholder needs and requirements to meet project objectives.
The key benefit of the Collect Requirements process is - Answer that it provides a basis to
define and manage project and product scope.
The two outputs of the Collect Requirements process are: - Answer Requirements
documentation and 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.
Questionnaires and surveys - Answer Written sets of questions designed to quickly
accumulate information from a large number of respondents.
Requirements Documentation - Answer A description of how individual requirements meet
the business need for the project.
Scope Process - Answer The process of developing a detailed description of the project and
the product.
Risk Register - Answer The risk register contains response strategies that may affect the
project scope, such as reducing or changing project and product scope to avoid or mitigate a
risk. We will be discussing risk and risk management in more detail in later modules.
