Project Scope: Project scope can be described as "the work that needs to be accomplished to deliver the End Result ( product or service or other project's objectives) with the specified features and functions that includes meetings, reports, analysis and all the other parts of Project Management.

Project Scope Management

Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Managing the project scope is primarily concerned with defining and controlling what is and is not included in the project. The knowledge area of Project Scope Management consists of five processes that are listed below:

• 5.1 Collect Requirements
• 5.2 Define Scope
• 5.3 Create WBS
• 5.4 Verify Scope
• 5.5 Control Scope

Notice that Scope Management Knowledge area is 5th chapter in PMBOK Guide. Processes in this knowledge area starts from 5.1 and ends at 5.5. 

All of these 5 processes are briefly explained here:

5.1 Collect Requirements

Collect Requirements is the process of defining and documenting stakeholders needs to meet the project objectives. The project s success is directly influenced by the care taken in capturing and managing project and product requirements. 

Collect Requirements Process
Inputs	Tools & Techniques	Outputs
Project charter Stakeholder register	Interviews Focus groups Facilitated workshops Group creativity techniques Group decision making techniques Questionnaires and surveys Observations Prototypes	Requirements documentation Requirements management plan Requirements traceability matrix

Inputs

• Project Charter:
  The project charter is used to provide the high-level project requirements and high-level product description of the project so that detailed product requirements can be developed.
• Stakeholder Register
  It is primarily concerned with authorizing the project /phase. It links project to the ongoing work of the organization

Tools and techniques

• Interviews
  An interview is a formal or informal approach to discover information from stakeholders by talking to them directly. It is typically performed by asking prepared and spontaneous questions and recording the responses.
• Focus groups 
  Focus groups bring together pre-qualified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or result.
• Facilitated Workshops
  Workshops are focused sessions that bring key cross-functional stakeholders together to define product requirements.
• Group Creativity Techniques
  Group activities can be organized to identify project and product requirements like Brainstorming, Nominal group technique, The Delphi Technique, Idea/mind mapping and Affinity diagram.
• Group Decision Making Techniques
  Group decision making is an assessment process of multiple alternatives with an expected outcome in the form of future actions resolution.
• Questionnaires and Surveys
  Questionnaires and surveys are written sets of questions designed to quickly accumulate information from a wide number of respondents.
• Observations
  Observations provide a direct way of viewing individuals in their environment and how they perform their jobs or tasks and carry out processes.
• Prototypes
  Prototyping is a method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it.

Outputs

• Requirements Documentation
  Requirements documentation describes how individual requirements meet the business need for the project.
• Requirements Management Plan
  It describes how requirements will be analyzed, documented, and managed throughout the project.
• Requirements Traceability Matrix
  The requirements traceability matrix is a table that links requirements to their origin and traces them throughout the project life cycle. It provides a structure for managing changes to the product scope.

5.2 Define Scope

Define Scope Process
Inputs	Tools & Techniques	Outputs
Project charter Requirements documentation Organizational process assets	Expert judgment Product analysis Alternatives identification Facilitated workshops	Projects scope statement Project document updates

Inputs

• Project Charter: The project charter provides the high-level project description and product characteristics.
• Requirements Documentation: Requirements documentation describes how individual requirements meet the business need for the project.
• Organizational Process Assets: Organizational process assets includes but are not limited to Policies, procedures, templates for a project scope statement, Project files and experiences learned from previous phases or projects.

Tools and Techniques

• Expert Judgment
• Expert judgment is often used to analyze the information needed to develop the project scope statement. It is available from many sources, including Other units within the organization, Consultants, Stakeholders, including customers or sponsors etc.
• Product Analysis
• Product analysis includes techniques such as product breakdown. Systems analysis, requirements analysis, systems engineering, value engineering, and value analysis.
• Alternatives Identification
• Identifying alternatives is a technique used to generate different approaches to execute and perform the work of the project.
• Facilitated Workshops
• Workshops are considered a primary technique for quickly defining cross functional requirements and reconciling stakeholder differences.

Outputs

• Project Scope Statement
• The project scope statement means the projects deliverables and the work required to create those deliverables. It may contain explicit scope exclusions that can assist in managing stakeholder expectations.
• 2. Project Document Updates
• Project documents that may be updated include, but are not limited to Stakeholder register, Requirements documentation, and Requirements traceability matrix.

5.3 Create WBS

Create WBS Process
Inputs	Tools & Techniques	Outputs
Project scope statement Requirements documentation Organizational process assets	Decomposition	WBS WBS dictionary Scope baseline Project document updates

Inputs

• 1. Project Scope Statement
• The project scope statement means the projects deliverables and the work required to create those deliverables.
• 2. Requirements Documentation
• Requirements documentation describes how individual requirements meet the business need for the project.
• 3. Organizational Process Assets
• The organizational process assets that can influence the Define Scope process include, but are not limited to Policies, procedures, templates for the WBS, Project files and Lessons learned from previous projects.

Tools and Techniques

• 1. Decomposition
• Decomposition is the subdivision of project deliverables into smaller, more manageable components until the work and deliverables are defined to the work package level.

Outputs

• 1. WBS
• The WBS is 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.
• 2. WBS Dictionary
• The WBS dictionary is a document generated by the Create WBS process that supports the WBS.
• 3. Scope Baseline
• The scope baseline is a component of the project management plan it include Project scope statement, WBS, and WDS dictionary
• 4. Project Document Updates
• Project documents that may be updated include, but are not limited to requirements documentation.

5.4 Verify Scope

Verify Scope Process
Inputs	Tools & Techniques	Outputs
Project management plan Requirements documentation Requirements traceability matrix Validated deliverables	Inspection	Accepted deliverables Change requests Project document updates

Inputs

• 1. Project Management Plan
• The project management plan contains the scope baseline, Components of the scope baseline include Project scope statement, WBS, and WBS dictionary.
• 2. Requirements Documentation
• Requirements documentation describes how individual requirements meet the business need for the project.
• 3. Requirements Traceability Matrix
• The requirements traceability matrix is a table that links requirements to their origin and traces them throughout the project life cycle. It provides a structure for managing changes to the product scope.
• 4. Validated Deliverables
• Validated deliverables have been completed and checked for correctness by the Perform Quality Control process.

Tools and Techniques

• Inspection
• Inspection includes activities such as measuring, examining, and verifying to determine whether work and deliverables meet requirements and product acceptance criteria.

Outputs

• 1. Accepted Deliverables
• Deliverables that meet the acceptance criteria are for many signed out and approved by the customer or sponsor.
• 2. Change Requests
• The change requests are processed for review and disposition through the Perform Integrated Change Control process.
• 3. Project Document Updates
• Project documents that may be updated as a result of the Verify Scope process include any documents that define the product or report status on product completion.

5.5 Control Scope

Control Scope Process
Inputs	Tools & Techniques	Outputs
Project management plan Work performance information Requirements traceability matrix Organizational process assets	Variance analysis	Work performance measurements Organizational process assets updates Change requests Project management plan updates Project document updates

Inputs

• 1. Project Management Plan
• The project management plan can be defined as a formal, approved document that defines how the project is executed, monitored and controlled. It contains Scope baseline, Scope management plan, Change management plan, Configuration management plan, and Requirements management plan to control scope:
• 2. Work Performance Information
• Information about project progress, such as which deliverables have started, their progress and which deliverables have finished.
• 3. Requirements Documentation
• Requirements documentation describes how individual requirements meet the business need for the project.
• 4. Requirements Traceability Matrix
• It is a table that links requirements to their origin and traces them throughout the project life cycle. It provides a structure for managing changes to the product scope.
• 5. Organizational Process Assets
• The organizational process assets that can influence the Control Scope process Include but are not limited to existing formal and informal scope control-related policies, procedures, and guidelines.

Tools and Techniques

• 1. Variance Analysis
• Project performance measurements are used to assess the magnitude of variation from the original scope baseline.

Outputs

• 1. Work Performance Measurements
• Measurements can include planned vs. actual technical performance or other scope performance measurements. This information is documented and communicated to stakeholders.
• 2. Organizational Process Assets Updates
• Organizational process assets that may be updated include, but are not limited to causes of variances, corrective action chosen and the reasons.
• 3. Change Requests
• Analysis of scope performance can result in a change request to the scope baseline or other components of the project management plan.
• 4. Project Management Plan Updates
• Scope Baseline Updates. If the approved change requests have an effect upon the project scope, then the scope statement the WBS, and the WBS dictionary are revised and reissued to reflect the approved changes.
• Other Baseline Updates. If the approved change requests have an effect on the project scope, then the corresponding cost baseline and schedule baselines are revised and reissued to reflect the approved changes.
• 5. Project Document Updates
• Project documents that may be updated include, but are not limited to requirements documentation, and requirements traceability matrix.