The Project Scope Statement is a detailed description of the project's deliverables, and the work required to create those deliverables. It provides a common understanding of the project scope among all project stakeholders, and establishes the project boundaries. It also forms the basis for agreement on the project scope and future project decisions. This includes the methodologies used, the resources and activities required to accomplish the project, and any constraints or assumptions.

Requirements Management is a systematic approach to eliciting, organizing, documenting, updating, and managing the functional and non-functional requirements of a project. These requirements provide a detailed understanding of the client's needs, which the project team aims to fulfill through deliverables. Sound requirements management ensures all needs are understood, documented, and agreed upon from the onset to avoid scope creep and ensure project success.

The Scope Baseline is the approved version of a scope statement, WBS, and its associated WBS dictionary, which can be changed only through formal change management procedures and is used as a basis for comparison. It's an important concept as changes to project outcomes are often required and the scope baseline provides a level-set to understand the changes, their impacts, and what is required to implement them.

Scope Verification is the process of formalizing the acceptance of the completed project deliverables. This involves reviewing deliverables with the customer or sponsor to ensure that they are completed satisfactorily and obtain formal acceptance of deliverables by the customer or sponsor. This process helps prevent scope creep, ensures the customer's needs are met, and provides a way to resolve issues and disagreements about deliverables.

Scope Creep refers to the unexpected changes or expansion in project scope after the project has started without adjustments to time, cost, and resources. It usually happens when new features or functionalities are added to the project without proper control or review of how the changes will influence the overall project. This can be due to unclear initial requirements, lack of change control process, or lack of stakeholder engagement. If not controlled, it may result in project overruns, cost increases, and could even jeopardize the project's success.

The Change Control System is a formal process used in project scope management to ensure that any potential changes to the project scope are reviewed, approved, or rejected. It involves recording and analyzing change requests, assessing the potential impact on project objectives, and approving or denying changes. This system is also responsible for updating the relevant project documents and communicating approved changes to all stakeholders. It helps in maintaining the scope baseline and mitigating scope creep, therefore ensuring project objectives are met within the agreed-upon constraints.

Scope Control refers to the processes and techniques used to manage and control the scope of a project. This includes monitoring the status of the scope, managing changes to the scope baseline, and ensuring project work is in alignment with the scope. It involves identifying and controlling scope creep, managing scope baseline changes, and ensuring deliverables are in accordance with the agreed-upon project requirements. The goal of scope control is to ensure that the project remains within its initial scope boundaries, to avoid overruns in time and cost.

The Project Charter is a formal, usually short document that defines and authorizes the project or a phase. It includes high level information about the project such as project purpose, objectives, stakeholders, deliverables, boundaries, constraints, and assumptions. It acts as a contract between the project sponsor, key stakeholders, and the project team, by stating the common understanding about the project. The project scope statement is typically derived from the project charter. The project charter gives the project manager authority to allocate resources to the project and make decisions on behalf of the project.

Product Scope refers to the functions, features, and characteristics that define a product, service, or result within a project. It is the part of project scope that focuses specifically on the end result of the project. It encompasses all the aspects that make a product, from its design to its features and functionality. Product scope is defined based on customer or stakeholder requirements and is frequently documented using a product backlog or requirements gathering techniques. It is a critical component of project management and is vital to a project's success.

The Project Life Cycle refers to the sequence of stages a project goes through from its initiation to its closure. These stages typically include initiation, planning, execution, monitoring and control, and closure. These stages provide a framework to manage and control project activities and are an essential aspect of Project Scope Management. Understanding the project life cycle helps manage the scope of the project effectively as it provides a sequence of activities necessary to successfully deliver the project objectives within the specified parameters.

Deliverables are the unique products, results, or capabilities produced as a result of a project. These tangible outputs are developed during the execution phase and are handed over to the customer upon project completion. Deliverables could be a product, service, improvement, etc. Each deliverable comprises of one or more project activities and involves one of more project team members. Proper identification, planning, development and management of project deliverables is a key aspect of project scope management, and is critical to the project's success.

Variance Analysis in the context of Project Scope Management involves the process of quantitatively and qualitatively assessing the degree of difference between planned and actual project performance. This methodology enables the project management team to evaluate the overall impact of project risk and to compute corrective measures to align with initial project plans. Variance Analysis not only helps in scrutinizing project performance but also assists in the successful management of the project scope by identifying where performance deviates from the scope baseline and determining what is causing this variance.