According to the PMBOK Guide, the Schedule Variance (SV) is a metric used in Earned Value Management (EVM) to determine how much a project is ahead of or behind its planned schedule at a specific point in time.
The Formula: The calculation for Schedule Variance is:
$$SV = EV - PV$$
(Where $EV$ is Earned Value and $PV$ is Planned Value).
Applying the Data:
Earned Value ($EV$): This is the work actually completed. In this scenario, it is 14 units.
Planned Value ($PV$): This is the work that was scheduled to be completed. In this scenario, it is 23 units.
The Calculation:
$$SV = 14 - 23 = -9$$
Interpreting the Result:
Because the SV is negative (-9), it indicates that the project is behind schedule. Specifically, it has " earned "
9 units less of value than what was originally planned for this date.
If the result were positive, the project would be ahead of schedule. If it were zero, the project would be exactly on schedule.
Analysis of other options:
Option B (37): This is the result of adding the two numbers ($23 + 14$). Addition is not used to find variance.
Option C (9): This is the absolute difference ($23 - 14$) but ignores the mathematical direction. In EVM, the order of the formula is critical; $EV$ must come first. A positive 9 would incorrectly suggest the project is ahead of schedule.
Option D (322): This is the result of multiplying the two numbers ($23 \times 14$). Multiplication is not used in variance calculations.
Per PMI standards, the Schedule Variance (SV) is the mathematical difference between what has been accomplished ($EV$) and what was planned ($PV$), making -9 the only correct answer.

According to the PMBOK Guide (Project Management Body of Knowledge), specifically within the Project Stakeholder Management knowledge area, the failure to recognize a stakeholder ' s needs usually stems from a breakdown in the initial identification phase:
* Identify Stakeholders (Option B): This is the process of identifying project stakeholders regularly and analyzing and documenting relevant information regarding their interests, involvement, interdependencies, influence, and potential impact on project success. A key output of this process is the Stakeholder Register, which should include their major requirements and expectations. If a project manager is unaware of a stakeholder ' s need, it most likely means that either the stakeholder was not identified at all or their specific needs and expectations were not properly captured during this initial process.
* Plan Stakeholder Engagement (Option A): This process focuses on developing approaches to involve stakeholders based on their needs, interests, and impact. You cannot plan for an engagement strategy if the underlying need has not been identified first.
* Manage Stakeholder Engagement (Option C): This is the execution process of communicating and working with stakeholders to meet their needs/expectations and foster appropriate stakeholder engagement. While this is where you might discover the missed need, the root cause of " missing " the need is a failure in the identification/analysis step.
* Monitor Stakeholder Engagement (Option D): (Note: Formerly " Control Stakeholder Engagement " in older editions). This is the process of monitoring project stakeholder relationships and tailoring strategies for engaging stakeholders. This process is used to look for variances in engagement, not for the primary collection of requirements.
In the PMI framework, Identify Stakeholders is an iterative process that should happen throughout the project.
If a new need surfaces that was " not known, " it indicates the Project Manager needs to revisit the Stakeholder Register and update the stakeholder ' s profile.

According to the PMBOKGuide, the process of Perform Integrated Change Control is the central point where all change requests are reviewed, approved, or rejected.
* Process Definition: This process is conducted from the project ' s inception through to completion. It is the only process responsible for managing changes to deliverables, project documents, and the project management plan.
* The Output: When a change request is submitted (typically as an output from various Monitoring and Controlling processes), it is processed here. The Change Request Status Updates are the formal output indicating whether the request was:
* Approved: The change is authorized and will be implemented.
* Deferred: The change is postponed for a later phase or version.
* Rejected: The change is denied.
* Communication: These status updates are then communicated to the stakeholders and used to update the Change Log, which tracks the progress and final disposition of all changes throughout the project life cycle.
Comparison with Other Options:
* Direct and Manage Project Execution (B): This process (now called Direct and Manage Project Work) is where approved changes are actually implemented. It provides " Change Requests " as an output when the team identifies a need for a change, but it does not update the " status " of the request itself.
* Close Project or Phase (C): This process involves finalizing all activities across all Process Groups to formally complete the project or phase. While it ensures all changes are closed out, it is not the process that generates status updates for active requests.
* Monitor and Control Project Work (D): This process is focused on tracking, reviewing, and reporting the overall progress to meet the performance objectives defined in the project management plan. It generates " Change Requests " as an output when variances are detected, but the decision and status update happen in Integrated Change Control.

According to the PMBOK Guide (specifically the chapters regarding organizational influence and project lifecycles), the level of authority and resource availability for a project manager is dictated by the organizational structure.
The situation described-where the project manager is full-time, has full-time administrative staff, and full- time project team members-is a hallmark of a Projectized (also known as " Project-Oriented " ) organization.
In the comparison of organizational structures:
* Projectized: The project manager has high to almost total authority. Resources are assigned full-time to the project, and the project manager operates with a high degree of independence.
* Weak Matrix: The project manager acts more as a coordinator or expediter. Resources remain in their functional departments and are not dedicated full-time to the project.
* Functional: The project manager has little to no authority. Staff are managed by functional managers, and project work is often done in addition to departmental work.
* Balanced Matrix: The project manager shares authority with functional managers. While the PM is full- time, the staff and administrative support are typically not dedicated solely to one project full-time.
As per the PMI Standard for Project Management, the " Projectized " structure is the only one where the PM typically possesses a high percentage of the organization ' s resource control and a dedicated support team.

According to the PMBOK Guide and the Agile Practice Guide, projects characterized by high uncertainty (such as those using adaptive, agile, or hybrid lifecycles) require a different approach to budgeting and estimation than traditional, predictive projects.
* Lightweight Estimation: In high-uncertainty environments, detailed, long-term estimates are often inaccurate because requirements change frequently. Instead, teams use lightweight estimation methods.
This involves high-level forecasts based on macro-level data, such as " T-shirt sizing " (Small, Medium, Large) or story points.
* Just-in-Time Planning: Rather than spending significant time upfront on a detailed budget that will likely become obsolete, lightweight estimation allows for quick, iterative updates as more information becomes available. This is often referred to as " progressive elaboration. "
* Flow and Velocity: Budgets in these environments are often based on the team ' s historical velocity or the cost per iteration, providing a flexible framework that can adapt to the " unknowns " of the project.
Why other options are incorrect:
* Option A: Detailed estimation: This is also known as " bottom-up " estimating. While highly accurate for projects with stable, well-defined scopes, it is extremely inefficient and prone to error in high- uncertainty projects where the scope is constantly evolving.
* Option C: Parametric estimation: This uses a mathematical model based on historical data and project parameters (e.g., cost per square foot). While useful for repetitive work, it lacks the flexibility needed to handle the unique uncertainties and " emergent " requirements of complex, adaptive projects.
* Option D: A mix of them: While hybrid projects do exist, the specific recommendation for the " high uncertainty " component is to move away from rigid, heavy processes toward lightweight methods to maintain agility and avoid wasted planning effort.