Term
Define Project Scope
Management |
|
Definition
It's the process required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. |
|
|
Term
What processes are included in
Project Scope Management? |
|
Definition
-
Collections Requirements
-
Define Scope
-
Create WBS
-
Verify Scope
-
Control Scope
|
|
|
Term
Scope can refer to what
within the
project context? |
|
Definition
- Product scope - features and functions that characterize a product, service or result
-
Project scope - the work needs to be accomplished to deliver a product, service or result with specified features/functions
|
|
|
Term
Define Collection
Requirements? |
|
Definition
It's the process of defining and documenting stakeholders' needs to meet the project objectives. |
|
|
Term
What "requirments" become the
foundation of WBS? |
|
Definition
|
|
Term
What are the inputs to
Collect Requirements? |
|
Definition
-
Project charter
-
Stakeholder register
|
|
|
Term
What are the tools/techniques
to
Collect Requirements? |
|
Definition
- Interview - formal/informal; one-on-one
- Focus groups - trained moderator guides the group
- Facilitated workshops - focus workshops JAD or QFD
- Group creativity techniques - brainstorming, Delphi Technique, idea/mind mapping, affinity diagrams
- Group decision making techniques -
- Questionnaires and surveys - written set of quesitons designed to quickly gather information
- Observation - direct way to view individuals in their environment
- Prototypes
|
|
|
Term
What are the outputs to
Collect Requirements? |
|
Definition
- Requirements documentation
- Requirements management plan
- Requirements traceability matrix
|
|
|
Term
Name the Group Decisions Making Techniques
used as a Tool n Techique to
Collect Information. |
|
Definition
- Unanimity - everyone agrees on single course of action
- Majority - support from more than 50% of members
- Plurality - largest block in a group decides even if a majority is not achieved
- Dictatorship - one individual makes the decision for the group
|
|
|
Term
|
Definition
Joint Application Development (or Design) - used in software industry. Focused on bringing users and the development team together to improve software development process. |
|
|
Term
|
Definition
Quality Function Deployment - facilitated workshop technique that helps determine critical characteristics for new product development; used in MFG. |
|
|
Term
|
Definition
Voice of customers - collection of customer needs and then needs are objectively sorted and prioritized and goals are set to achieve them. |
|
|
Term
|
Definition
A selected group of experts answers questionnaires and provides feedback regarding the responses from each round of requirement gathering |
|
|
Term
|
Definition
Ideas generated within a brainstorming session are then consolidated into single map to reflect commonality in understanding, and generate new ideas. |
|
|
Term
What does a Requirements Documentation
set out to do? |
|
Definition
Describes how individual requirements meet the business need for the project. |
|
|
Term
Name some components
to the
Requirements Documentation |
|
Definition
- Business need or opportunity to be seized
- Business and project objectives for traceability
- Functional requirements, describing business processes, information and interaction with the product
- Non-functional requirements; level of service, performance
- Quality requirements
- Acceptance criteria
- Business rules stating the guiding principles of the org.
- Impacts to other organizational areas
- Impacts to other entities inside or outside the performing org.
- Support and training requirements
- Requirements assumptions and constraints
|
|
|
Term
What does the Requirments Management Plan
do? |
|
Definition
Documents how requirements will be analyzed, documented and manged throughout the project. |
|
|
Term
Name a few of the components
that the Requirements Mangement Plan
can include |
|
Definition
-
How requirements activities will be planned, tracked and reported.
-
Configuration management activities such as how changes to the product, service or result requirements will be initiated, how impacts will be analyzed, how they will be traced, tracked and reported.
-
Requirements prioritization process
-
Product metrics that will be used
-
Traceability structure
|
|
|
Term
Define Requirements Traceabilty Matrix |
|
Definition
A table that links requirements to their origin and traces them throughout the project life cycles. It provides a means to track requirements throughout the project life cycle, helping to ensure that requirements approved in the requirements documentation are delivered at the end of the project |
|
|
Term
|
Definition
It's the process of developing a detailed description of the project and product which is critical to the project success and builds upon the major deliverables, assumptions, and constraints. |
|
|
Term
What are the inputs to
Scope? |
|
Definition
- Project charter
- Requirements documentation
- Organizational Process Assets
|
|
|
Term
What are the tools/techniques to
Scope? |
|
Definition
- Expert judgement
- Product analysis - only used for projects that have products to deliver
- Alternative identification
- Facilitated workshops
|
|
|
Term
What are the outputs to
Scope? |
|
Definition
- Project scope statement
- Project document updates - stakeholder register, requirments documentation and requirements traceability matrix
|
|
|
Term
What is a Project Scope Statement? |
|
Definition
It describes in detail the project deliverables and the work required to create those deliverables. Also provides a common understanding of the project scope among stakeholders. |
|
|
Term
What does a detailed project
scope statement include? |
|
Definition
|
|
Term
|
Definition
WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. It's a deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives. |
|
|
Term
What are the inputs to
Create WBS |
|
Definition
- Project scope statement
- Requirements documentation
- Organizational process assets
|
|
|
Term
What are the Tools n Techniques
to Create WBS? |
|
Definition
Decomposition - subdivision of project deliverables into smaller, more manageable components until the work and deliverable are defined to the work package level. |
|
|
Term
|
Definition
Planned work contained within the lowest level of WBS component |
|
|
Term
Decomposition of the total project work
into project work into work packages generally
involves what types of activities? |
|
Definition
- Identifying and analyzing the deliverable and related work
- Structuring and organizing the WBS
- Decomposing the upper WBS levels into lower level detailed components
- Developing and assigning identification codes to the WBS components
- Verifying that the degree of decomposition of the work is necessary and sufficient
|
|
|
Term
WBS structure can be created
in what types of forms? |
|
Definition
|
|
Term
What are the outputs
to
Create WBS? |
|
Definition
-
WBS
-
WBS dictionary
-
Scope baseline
-
Project document updates
|
|
|
Term
What are the components of the scope baseline? |
|
Definition
|
|
Term
|
Definition
Document generated by the Create WBS process that supports the WBBS. It provides more detailed description of work and technical documents for each WBS element |
|
|
Term
|
Definition
A deliverable-oriented hierarchical decomposition of the work to be executed by the project team, to accomplish the project objectives and create the required deliverables of project work. |
|
|
Term
|
Definition
Process of formalizing acceptance of the completed project deliverables. |
|
|
Term
Is Verify Scope the same as Quality Control? |
|
Definition
No, Verify Scope primary concern is with the acceptance of the deliverables. While Quality Control is primarily concerned with correctness of the deliverables and meeting the quality requirements specified for the deliverables. |
|
|
Term
What are the inputs to
Verfiy Scope? |
|
Definition
- Project management plan
- Requirements documentation
- Requirements traceability matrix
- Validate deliverables
|
|
|
Term
What are the tools n techniques
to
Verify Scope? |
|
Definition
|
|
Term
What are the outputs to
Verify Scope? |
|
Definition
|
|
Term
|
Definition
It is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. |
|
|
Term
What are the inputs to
Control Scope? |
|
Definition
- Project management plan
- Work performance information
- Requirements documentation
- Requirements traceability matrix
- Organizational process assets
|
|
|
Term
What are the Tools n Techniques
to
Control Scope? |
|
Definition
Variance analysis - relative to the baseline |
|
|
Term
What are the outputs to
Control Scope? |
|
Definition
- Work performance measurements
- Organizational process assets updates
- Change requests
- Project management plan updates - scope baseline and other baseline updates
- Project document updates
|
|
|