Which tool or technique is used in the Plan Scope Management process?

According to the PMBOK® Guide, the Plan Scope Management process is the process of creating a scope management plan that documents how the project and product scope will be defined, validated, and controlled. This process occurs early in the Planning Process Group.

Expert Judgment: This is a standard tool and technique for the Plan Scope Management process. It involves input from individuals or groups with specialized knowledge or training in similar projects, the specific industry, or the technical area. Experts help define how the scope will be managed based on organizational culture, complexity, and historical information.

Other Tools for this Process: In addition to Expert Judgment, this process utilizes Data Analysis (specifically alternatives analysis) and Meetings.

Why the other options are incorrect:

A. Document analysis: This is a tool and technique used in the Collect Requirements process, not Plan Scope Management. It involves reviewing existing documentation to identify requirements.

B. Observations: Also known as " job shadowing, " this is a tool and technique used in Collect Requirements to understand business processes or requirements that users may find difficult to articulate.

C. Product analysis: This is a tool and technique used in the Define Scope process. It involves defining the product and its requirements in more detail through techniques like systems engineering or value engineering.