ISMN 5370 TEST 2 STUDY GUIDE
Scope - Answers :refers to all the work involved in creating the products of the project
and the processes used to create them.
deliverable - Answers :describes a product created as a part or a project
Six main Scope Management Processes - Answers :1. Planning scope management 2.
Collecting requirements 3. Defining scope 4. Creating the WBS 5. Validating scope 6.
Controlling scope
Planning Scope Management (Scope Process 1) - Answers :involves determining how
the project's scope and requirements will be managed.
Collecting requirements (Scope Process 2) - Answers :involves defining and
documenting the features and functions of the products for the project as well as the
processes used for creating them.
Defining scope (Scope Process 3) - Answers :involves reviewing the scope
management plan, project charter, requirements documents, and organizational
process assets to create a scope statement, adding more information as requirements
are developed and change requests are approved.
Creating the WBS (Scope Process 4) - Answers :involves subdividing the major project
deliverables into smaller, more manageable components.
Validating scope (Scope Process 5) - Answers :involves formalizing acceptance of the
project deliverables.
Controlling Scope (Scope Process 6) - Answers :involves controlling changes to project
scope throughout life of the project -- a challenge on many IT projects.
Scope Management Plan includes: - Answers :1. How to prepare a detailed project
scope statement 2. How to create a WBS 3. How to maintain and approve the WBS 4.
How to obtain formal acceptance of the completed project deliverables 5. How to control
requests for changes in the project scope.
Requirements management plan - Answers :documents how project requirements will
be analyzed, documented, and managed.
Benchmarking - Answers :generating ideas by comparing specific project practices or
product characteristics to those of other projects or products inside or outside the
performing organization, can also be used to collect requirements.
, Requirements traceability matrix (RTM) - Answers :a table that lists requirements, their
various attributes, and the status of the requirements to ensure that all are addressed.
Project Scope statements - Answers :should include at least a product scope
description, product user acceptance criteria, and detailed information on all project
deliverables.
Work breakdown structure (WBS) - Answers :a deliverable-oriented grouping of the
work involved in a project that defines its total scope.
work package - Answers :a task at the lowest level of the WBS
decomposition - Answers :subdividing project deliverables into smaller pieces.
scope baseline - Answers :includes the approved project scope statement and its
associated WBS and WBS dictionary.
Approaches to developing WBSs - Answers :1. Using guidelines 2. the analogy
approach 3. the top-down approach 4. the bottom-up approach 5. the mind-mapping
approach
Analogy approach - Answers :you us a similar project's WBS as a starting point
top-down approach - Answers :start with the largest items of the project and break them
into subordinate items.
bottom-up approach - Answers :team members first identify as many specific tasks
related to the project as possible.
Mind-mapping approach - Answers :technique that uses branches radiating from a core
idea to structure thoughts and ideas.
WBS dictionary - Answers :a document that provides detailed information about each
WBS item.
scope creep - Answers :the tendency for project scope to keep getting bigger and
bigger.
Scope validation - Answers :involves formal acceptance of the completed project
deliverables
Prototyping - Answers :involves developing a working replica of the system or some
aspect of the system
Variance - Answers :is the difference between planned and actual performance
Scope - Answers :refers to all the work involved in creating the products of the project
and the processes used to create them.
deliverable - Answers :describes a product created as a part or a project
Six main Scope Management Processes - Answers :1. Planning scope management 2.
Collecting requirements 3. Defining scope 4. Creating the WBS 5. Validating scope 6.
Controlling scope
Planning Scope Management (Scope Process 1) - Answers :involves determining how
the project's scope and requirements will be managed.
Collecting requirements (Scope Process 2) - Answers :involves defining and
documenting the features and functions of the products for the project as well as the
processes used for creating them.
Defining scope (Scope Process 3) - Answers :involves reviewing the scope
management plan, project charter, requirements documents, and organizational
process assets to create a scope statement, adding more information as requirements
are developed and change requests are approved.
Creating the WBS (Scope Process 4) - Answers :involves subdividing the major project
deliverables into smaller, more manageable components.
Validating scope (Scope Process 5) - Answers :involves formalizing acceptance of the
project deliverables.
Controlling Scope (Scope Process 6) - Answers :involves controlling changes to project
scope throughout life of the project -- a challenge on many IT projects.
Scope Management Plan includes: - Answers :1. How to prepare a detailed project
scope statement 2. How to create a WBS 3. How to maintain and approve the WBS 4.
How to obtain formal acceptance of the completed project deliverables 5. How to control
requests for changes in the project scope.
Requirements management plan - Answers :documents how project requirements will
be analyzed, documented, and managed.
Benchmarking - Answers :generating ideas by comparing specific project practices or
product characteristics to those of other projects or products inside or outside the
performing organization, can also be used to collect requirements.
, Requirements traceability matrix (RTM) - Answers :a table that lists requirements, their
various attributes, and the status of the requirements to ensure that all are addressed.
Project Scope statements - Answers :should include at least a product scope
description, product user acceptance criteria, and detailed information on all project
deliverables.
Work breakdown structure (WBS) - Answers :a deliverable-oriented grouping of the
work involved in a project that defines its total scope.
work package - Answers :a task at the lowest level of the WBS
decomposition - Answers :subdividing project deliverables into smaller pieces.
scope baseline - Answers :includes the approved project scope statement and its
associated WBS and WBS dictionary.
Approaches to developing WBSs - Answers :1. Using guidelines 2. the analogy
approach 3. the top-down approach 4. the bottom-up approach 5. the mind-mapping
approach
Analogy approach - Answers :you us a similar project's WBS as a starting point
top-down approach - Answers :start with the largest items of the project and break them
into subordinate items.
bottom-up approach - Answers :team members first identify as many specific tasks
related to the project as possible.
Mind-mapping approach - Answers :technique that uses branches radiating from a core
idea to structure thoughts and ideas.
WBS dictionary - Answers :a document that provides detailed information about each
WBS item.
scope creep - Answers :the tendency for project scope to keep getting bigger and
bigger.
Scope validation - Answers :involves formal acceptance of the completed project
deliverables
Prototyping - Answers :involves developing a working replica of the system or some
aspect of the system
Variance - Answers :is the difference between planned and actual performance
