Alternatives generation - ex: Lateral thinking
Product analysis techniques -
The baseline for evaluating whether requests for changes or additional work are contained within or
outside the project's exclusion is provided by the Project Scope statement.
Quality function deployment is an example of a facilitated workshop used in the manufacturing industry as a tool and technique to collect requirements. It helps to determine the critical characteristics for new product development and starts by collecting customer needs, known as the voice of the customer.
Project scope creep is typically the result of uncontrolled changes. Scope control works to control the impact of any project scope changes.
The key document generated from the create WBS process is the actual WBS. Each WBS component is assigned a unique identifier to provide a structure for hierarchical summation of costs, schedule and resource information.
Project Performance measurements - Variance analysis is a tool and technique for control scope. Project performance measurements are used to assess the magnitude of variance, to determine the cause of the variance, and to decide whether corrective or preventive action is required.
Nominal group technique enhances brainstorming with a voting process, which is used to rank the most useful ideas for further brainstorming or for prioritization.
Identifying and analyzing the deliverables and related work is the first step in the decompostion of a project. The deliverables should be defined in terms of how the project will be organized.
Assumptions are factors that, for planning purposes, are considered to be true, real or certain without proof or demonstration.
Documentation that the customer has accepted completed deliverables is an output of validated scope.
Work authorization system is not used in control scope.
Work performance information is an output of validated scope. It emphasizes deliverables - whether or not they have started, their progress, and ones that have finished or have been accepted.
Phase-to-phase relationship: The requirements management plan defines how requirements will be analyzed, documented and managed. It is strongly influenced by the phase-to-phase relationship.
The requirements traceability matrix is an output of the collect requirements process. It includes tracing requirements to business needs, opportunities and objectives; product design;product development; test strategy scenarios; as well as high-level requirements to more detailed requirements.
Context diagram is a tool and technique in collect requirements and is an example of a scope model. The context diagram visually depicts the product scope as it shows a business system (process, equipment or computer etc) and how people and other systems (actors) interact with it. The diagram shows inputs to the business system, the actor(s) providing the input, outputs from the business system and actor(s) receiving the output.
The project scope statement describes the deliverables and the work required to create them. It also provides a common understanding of the scope among stakeholders. The product scope statement is a key component as it progressively elaborates the characteristics of the product, service or result in the project charter and requirements documentation.