The features and functions of a product, service or achievement

Work that must be done to deliver a product, service, or result with specified features and functionality

Project scope sometimes also includes product scope. Product life cycle includes project life cycle

Gather requirements

The above process is carried out at the beginning of the project

Confirm scope. Control range

Sponsors and client representatives should remain involved in the project. Use backlog items (product requirements and user stories) to reflect current needs

Validating scope occurs as each deliverable is produced or at stage review points

Scope of control is an ongoing process. and updated when necessary by implementing an overall change control process

Identify and recommend feasible solutions that meet these needs

Validation and control

Document project purpose

quality management plan

group Culture

policies and procedures

Similar projects in the past

Alternatives analysis

project manager

Develop a project scope statement. Create a WBS based on the detailed project scope statement

Determine how the scope baseline will be approved and maintained. Formal acceptance of completed project deliverables

How to plan, track and report on various requirements activities

Configuration management activities

A tracking structure that reflects which requirement attributes will be included in the tracking matrix

Business analysis. Requirements elicitation. Requirements analysis. Requirements documents

Project requirements from similar previous projects. Graphical techniques. Guidance. Conflict management

Brainstorming. Interview. Confidential Information. Interviews are formal or informal methods of obtaining information through direct conversations with stakeholders.

Focus groups. Gather intended stakeholders and subject matter experts. A trained moderator leads the interactive discussion

Questionnaire. Audience diversity. Investigations need to be completed quickly. Respondents were geographically dispersed. Suitable for statistical analysis

Benchmark comparison. Compare to identify best practices with other people’s children. Comparable organizations can be internal or external

File analysis

Vote - Agree. Majority agrees. The number of participants is an odd number. A relative majority agrees. Used when there are more than two options

Autocratic decision making. Multi-criteria decision analysis. Evaluate and rank many ideas

Affinity diagram. Group a large number of ideas for further review and analysis. mind Mapping. Reflect the commonalities and differences among creatives

nominal group technique

Observe and talk. Observation, also known as "work following"

guide

A visual depiction of the product range

Before manufacturing the intended product, a prototype of the product is built. Storyboarding is a prototyping technique

Prototype included. Miniature products. Computer generated 2D and 3D models. Mock-up or simulation

Business needs. Stakeholder needs. Transition and readiness requirements. Project requirements. Quality requirements

Solution needs. Functional Requirements. non-functional requirements

Business needs, opportunities, goals and objectives. Project Objectives. Project scope and WBS deliverables. product design

product development. Test strategies and test scenarios. High-level requirements to detailed requirements

High-level description. Product features. Approval requirements. Project scope plan. scope management plan

Assumption. log. Assumptions. Constraints.Requirements document. risk register

group Culture. Infrastructure.Personnel management system. market conditions

Policies, procedures, and templates for developing project scope statements. Project files/lessons learned from previous projects

Data analysis (alternative analysis). Interpersonal and team skills (facilitation). Decision-making (multi-criteria decision analysis)

Identify and analyze deliverables and related work. Determine the structure and orchestration method of WBS. Decomposition layer by layer from top to bottom

Develop and assign identification codes to WBS components. Verify that deliverables are broken down to the appropriate extent

Progressively divide the project scope and project deliverables into smaller, more manageable components. A work package is the lowest level of work in the WBS

Top down. Merge lower-level components from the bottom up. Each stage of the project life cycle is the second layer, and products and project deliverables are the third layer.

Primary deliverables serve as the second layer. Incorporate various lower-level components developed by organizations outside the project team, such as contract WBS for outsourced work

The agile method is to break down long stories into user stories. Rolling planning to decompose. 100% principle: summarizing upward layer by layer

project scope statement

WBS

work package

planning package

WBS Dictionary

Scope management plan. Requirements management plan. Scope baseline

Lessons Learned Register. Quality Report. Requirements Document. Requirements Tracking Matrix

Deliverables that have been completed and checked as correct by the control quality process

The degree to which it meets the needs. No amount. The severity of the inconsistency or the number of confirmations performed within a certain time period

Conduct activities such as measurement, review and validation to determine whether work and deliverables meet requirements and product acceptance criteria

review. Product Review. Inspection

vote

Job performance information. Change request. It may be necessary to submit a change request for the deliverables and carry out defect remediation

Lessons learned register.Requirements document. Requirements Tracking Matrix

Scope management plan. Requirements management plan. Change management plan. Configuration management plan. Scope benchmark. performance measurement benchmarks

Lessons Learned Register. Requirements Document

Requirements tracking matrix. Exploring the impact of any changes or deviations from the scope baseline on the project objectives

The number of change requests received. The number of change requests accepted. Number of deliverables verified, validated and completed

Existing, formal and informal policies, procedures and guidance related to scope control. Available monitoring and reporting methods and templates

Deviation analysis. Determine whether corrective or preventive action is needed

trend analysis. Determine whether performance is improving or deteriorating

Classification of changes. Identified scope deviations and causes. Impact of deviations on schedule and cost. Predictions of future scope performance

Project document updates. Lessons learned register. Causes of deviations and selected corrective actions. Requirements documentation. Requirements tracking matrix

scope management plan

Scope benchmark.

Progress benchmark. scope. resource. progress estimate

Cost basis. scope. resource. Cost Estimate

Performance measurement benchmarks. scope. Progress performance. Cost Estimate