In the context of change management and project management, the scope defines the specific boundaries of a change or project. It explicitly outlines all the work, deliverables, features, and resources that are included, as well as what is excluded. This detailed definition of boundaries and deliverables directly corresponds to the "extent" of the change, ensuring all stakeholders have a clear and common understanding of what the change entails from start to finish.

B. Purpose: This explains the reason or justification for the change, not its boundaries or extent.

C. Analysis: This is the process of examining the change's requirements and potential effects, not the definition of its extent.

D. Impact: This refers to the potential consequences or effects of the change on the organization, which is assessed after the scope is defined.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Section 2.2.3

"Project Scope

" defines scope as the work required to deliver a product

service

or result with specified features and functions.

2. Carnegie Mellon University Open Learning Initiative. (n.d.). Project Management for Engineers. Module 3: Defining the Project

"Defining the Scope." This courseware states

"The project scope is a written statement that defines the work or tasks to be done or the products or services to be delivered by the project."

3. University of Washington

UW-IT. (n.d.). Change Management - Key Concepts. In its official documentation on IT change management

the scope is identified as a key component of a change request

detailing "what the change is" and "what is being changed

" which directly defines its extent.