In accordance with the PMBOKGuide, particularly within the Collect Requirements and Define Scope processes, the definition of the product scope is fundamentally driven by the customer ' s needs and expectations.
* The Client/Customer (Choice A): The client is the primary stakeholder who defines the requirements and the ultimate scope of the product. They provide the business need and the functional/non-functional requirements that the project is intended to fulfill. While the project team facilitates the discovery and documentation of these requirements, the " what " of the product-its features and functions-is defined by the client.
* The Project Manager (Choice B): The PM is responsible for managing the project scope (the work required to deliver the product). While the PM facilitates the Define Scope process and ensures the scope statement is documented, they do not " define " the product features; they translate the client ' s needs into a manageable plan.
* The Team (Choice C): The project team (or technical experts) provides input on the technical feasibility and the " how " of the product. In Agile environments, the team may help refine the backlog, but the direction of the product scope remains with the customer or their representative (the Product Owner).
* The Program Manager (Choice D): A program manager provides high-level oversight and ensures strategic alignment across multiple related projects. They are too far removed from individual project deliverables to define the specific product scope.
The Product Scope refers to the features and functions that characterize a product, service, or result. Its successful completion is measured against the product requirements, which are owned and defined by the Client.

In accordance with the PMBOKGuide and the standard practices for Earned Value Management (EVM), Schedule Variance (SV) is a measure of schedule performance expressed as the difference between the earned value and the planned value.
* The Formula:
$$SV = EV - PV$$
* EV (Earned Value): The measure of work performed expressed in terms of the budget authorized for that work.
* PV (Planned Value): The authorized budget assigned to scheduled work.
* Interpretation of Results:
* Positive SV ($ > 0$): Indicates that the project is ahead of schedule (more work has been earned than was planned).
* Negative SV ($ < 0$): Indicates that the project is behind schedule (less work has been earned than was planned).
* Zero SV ($= 0$): Indicates that the project is exactly on schedule.
* Comparison with Other Options:
* EV less AC (A): This is the formula for Cost Variance (CV) ($CV = EV - AC$). It measures cost performance.
* AC less PV (B): This is not a standard EVM metric used for performance measurement.
* AC less EV (D): This is essentially the inverse of Cost Variance and is not a standard project management formula.
In the Control Schedule process, SV is a critical indicator used to determine if the project is deviating from the schedule baseline and if corrective or preventive actions are required.

According to the PMBOKGuide, communication must be tailored based on the audience to ensure effectiveness. The " hierarchical focus " of stakeholder communications refers to the direction of communication relative to the project manager and the project team.
* Direction of Influence: Stakeholders occupy different positions in relation to the project. Understanding these positions helps the project manager choose the right tone, frequency, and level of detail:
* Upward: Communication with senior management (sponsors, steering committees). Requires high-level summaries and strategic focus.
* Downward: Communication with the project team or subject matter experts. Focuses on task assignments and technical details.
* Sideward: Communication with peers, such as other project managers or functional managers, who are competing for the same resources.
* Outward: Communication with stakeholders outside the project team, such as suppliers, government agencies, or the public.
* Effective Tailoring: By keeping the focus on the position of the stakeholder or group, the project manager avoids " information overload " (sending too much detail to executives) or " information gaps
" (not providing enough detail to the technical team).
* Organizational Context: This hierarchical approach ensures that the project manager respects the power dynamics and communication protocols within the organization.
Why other options are incorrect:
* Option A: Maintains the focus on project and organizational stakeholders: While true in a general sense, it does not explain the purpose of a " hierarchical " focus. Hierarchy specifically implies the relative position (rank/direction) rather than just the identity of the stakeholder.
* Option B: Preserves the focus on external stakeholders: This only addresses " outward " communication. A hierarchical focus must include internal stakeholders (upward, downward, and sideward) as well.
* Option C: Sustains the focus on general communication activities: This refers to communication methods or media (the " how " ), not the hierarchical focus (the " who " and their relative " rank " ).

According to the PMBOKGuide, specifically within the Manage Team process, there are five general techniques for resolving conflict. Smoothing (also known as Accommodating) is the specific technique that emphasizes areas of agreement rather than areas of difference.
* Definition of Smoothing/Accommodating: This technique involves de-emphasizing or avoiding the areas of conflict and instead focusing on the points where the parties agree. It is often used to maintain harmony in a relationship or when the issue is more important to the other party than to oneself.
* The Goal: The primary objective is to maintain a friendly atmosphere and reduce the emotional intensity of the conflict. It is a " conceding " position where one party may sacrifice their own concerns to satisfy the concerns of the other.
* Result: While it can provide temporary relief and keep the project moving, it is often a lose-win scenario. Because the underlying conflict is not actually addressed or solved, the issue may resurface later.
Comparison with Other Options:
* Compromising (A): Also known as Reconcile. This involves searching for solutions that bring some degree of satisfaction to all parties in order to temporarily or partially resolve the conflict. It is a " give- and-take " approach (lose-lose).
* Collaborating (B): Also known as Problem Solving. This involves incorporating multiple viewpoints and insights from differing perspectives. it requires a cooperative attitude and open dialogue that typically leads to consensus and commitment (win-win).
* Problem Solving (D): As noted above, this is synonymous with Collaborating. It treats the conflict as a problem to be solved by examining alternatives; it does not simply " smooth over " differences but works through them.

According to the PMBOKGuide and the Standard for Project Management, effective communication is a critical pillar of project success, especially when a formal leadership structure (like a dedicated project manager) is missing.
The three primary communication methods recognized by PMI are Interactive, Push, and Pull. In the scenario described:
Interactive Communication: This method involves a multidimensional exchange of information in real-time. It includes meetings, phone calls, video conferencing, and instant messaging. It is the most effective way to ensure a common understanding among all participants on a given topic. Because the team lacks a project manager to coordinate activities, the functional manager must ensure that the delegation is fully understood, expectations are clear, and the team can provide immediate feedback or ask clarifying questions.
Comparison with other options:
Push Communication: This involves sending information to specific recipients who need to know it (e.g., emails, memos, reports). While this ensures the information is distributed, it does not guarantee that it reached or was understood by the intended audience. Without a PM to follow up, " Push " communication risks leaving the team misaligned.
* Verbal/Oral Communication: These are types of communication, but they are not categorized as " methods " in the same way Interactive, Push, and Pull are in the Communication Management Plan.
Furthermore, " Verbal " and " Oral " are often used interchangeably in general conversation, but in a PMI context, Interactive is the formal method that encompasses these while focusing on the bidirectional flow of information.
In a self-managing team environment (or one where the PM role is absent), Interactive communication is essential to resolve conflicts, foster collaboration, and verify that the project ' s strategic objectives are correctly interpreted by the team members.