According to the PMBOKGuide, 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. To manage scope correctly, a project manager must follow the specific sequence of processes defined within the Scope Management Knowledge Area.
The six core processes are:
* Plan Scope Management: Creating a scope management plan that documents how the project and product scope will be defined, validated, and controlled.
* Collect Requirements: Determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
* Define Scope: Developing a detailed description of the project and product.
* Create WBS: Subdividing project deliverables and project work into smaller, more manageable components.
* Validate Scope: Formalizing acceptance of the completed project deliverables.
* Control Scope: Monitoring the status of the project and product scope and managing changes to the scope baseline.
Analysis of Other Options:
* A. Control Schedule; Control Costs: These belong to the Schedule Management and Cost Management Knowledge Areas, respectively. While related to overall project health, they are not tasks used to manage scope specifically.
* B. Develop Schedule: This is a Schedule Management process. Managing scope is the precursor to developing a schedule, but the schedule itself is not a scope management task.
* D. Control Costs; Manage Stakeholder Engagement: These are processes from other Knowledge Areas.
" Keeping budget under control " is a goal of Cost Management, not a defined process for managing Scope.

According to the PMBOKGuide, the Control Costs process is the process of monitoring the status of the project to update the project costs and managing changes to the cost baseline.
* Work Performance Information (WPI): In the Control Costs process, work performance data (raw observations) is collected and compared against the cost baseline. The resulting Work Performance Information includes a calculated assessment of how the project is performing financially, typically expressed through CV (Cost Variance) and CPI (Cost Performance Index).
* Cost Forecasts: As part of controlling costs, the project manager must determine if the project can still be completed within the approved budget. This involves calculating the Estimate at Completion (EAC) and Estimate to Complete (ETC). These values, which predict future cost performance based on current trends, are formally documented as Cost Forecasts.
* Integration: These outputs are critical because they are subsequently used as inputs to the Monitor and Control Project Work process to provide a holistic view of project health.
Comparison with other options:
* A. Estimate Costs: The primary output of this process is Activity Cost Estimates and Basis of Estimates. It focuses on predicting how much individual activities will cost before the work begins.
* B. Plan Cost Management: The primary output is the Cost Management Plan, which is a formal document describing how the project costs will be planned, structured, and controlled.
* C. Determine Budget: The primary outputs are the Cost Baseline and Project Funding Requirements.
This process aggregates the estimated costs of individual activities or work packages to establish an authorized cost baseline.

According to the PMBOKGuide, specifically regarding the Monitor Communications and Manage Stakeholder Engagement processes, the goal is to ensure that information needs are met efficiently and transparently.
* Self-Service Information (Pull Communication): In a functional organization, where lines of authority are often rigid, providing a director with direct access to existing reports is the most efficient and professional first step. This utilizes Pull Communication, which allows stakeholders to access information at their own discretion.
* Transparency and Professionalism: Directing the stakeholder to the official project reports ensures they are receiving the same verified data as everyone else. This addresses their concern with facts rather than hearsay or emotional escalation.
* Organizational Context: In a functional structure, the project manager often has limited authority. By providing a link to reports, the line manager supports the project ' s visibility without overstepping or causing unnecessary friction between departments.
Analysis of other options:
* A. Hold a face-to-face meeting and warn them: This is an aggressive and reactive approach. A " warning " assumes the project manager is at fault before the data (the reports) has even been reviewed.
It bypasses formal communication channels.
* C. Invite stakeholders to attend monthly meetings: While engagement is good, this is a future-dated solution. It does not address the director ' s immediate concern about current progress.
* D. Ask the project manager to update the distribution list: This is a Push Communication fix. While helpful for the future, the director expressed a concern now. Simply adding them to a list for next month does not provide them with the immediate clarity they are seeking.
Per PMI standards, the most effective way to manage stakeholder expectations and concerns is to ensure they have immediate access to the appropriate project performance data.

In Earned Value Management (EVM), as defined by the PMBOKGuide, the Schedule Variance (SV) is a measure of schedule performance expressed as the difference between the earned value and the planned value.
* Formula:
$$SV = EV - PV$$
* EV (Earned Value): The value of work actually performed expressed in terms of the budget assigned to that work. In this case, it is 25 days worth of work.
* PV (Planned Value): The authorized budget assigned to scheduled work. In this case, it is 13 days worth of work.
* Calculation:
$$SV = 25 - 13 = 12$$
* Analysis of the result:
* Positive SV (+12): A positive value indicates that the project is ahead of schedule because the team has completed more work than was originally planned for this point in time.
* Negative SV: A negative value would indicate that the project is behind schedule.
* Zero SV: Indicates that the project is exactly on schedule.
Analysis of other options:
* A (-12): This would occur if the team had only completed 1 day of work against 13 planned ($1 - 13$).
It represents a project that is significantly behind schedule.
* B (1.15): This does not match any direct EVM calculation for this data. (Note: The Schedule Performance Index (SPI), which is $EV / PV$, would be approximately $1.92$ in this scenario, showing extremely high efficiency).
* C (38): This is the sum of the two values ($25 + 13$), which is not a standard project management metric.
By calculating the Schedule Variance, the Project Manager can objectively report to stakeholders that the project is performing better than expected and can use this data to adjust future resource allocations or identify " lessons learned " regarding the team ' s high productivity.

According to the PMBOKGuide, the Control Quality process is the process of monitoring and recording results of executing the quality management activities to assess performance and ensure the project outputs are complete, correct, and meet customer expectations. To verify deliverables, the following tools and techniques are specifically utilized:
* Inspection: This is the examination of a work product to determine if it conforms to documented standards. The results of an inspection generally include measurements and may be called reviews, peer reviews, audits, or walkthroughs. Inspection is the primary tool used to verify that deliverables are " correct. "
* Statistical Sampling: This involves choosing part of a population of interest for inspection (e.g., selecting 10 random laptops out of a batch of 1,000 to check for defects). This is especially useful when the volume of deliverables is high or when inspection is destructive.
* Meetings: Specifically, Lessons Learned or Review Meetings are used within Control Quality to discuss the results of the quality assessments, determine if the deliverables should be accepted or rejected, and decide if rework is necessary.
Why other options are incorrect:
* Option B: While control charts are a tool for Control Quality, the Lessons learned register is a project document (often an input or output), not a tool or technique. " Product evaluation " is not a formal PMI process term; the correct term is Inspection.
* Option C: Checklists are a valid tool. However, retrospective documents are primarily used in agile
/adaptive environments during the " Manage Quality " or " Close Project " phases. Approved change requests are an input to the process (to verify they were implemented correctly), not a tool or technique itself.
* Option D: Black box tests are a specific type of inspection but are not listed as a general tool in the PMBOK Guide. Questionnaires and surveys are typically tools for the " Collect Requirements " or " Manage Stakeholder Engagement " processes, and the Lessons learned register is an output/input, not a technique.