According to the PMBOKGuide, Expert Judgment is a primary tool and technique used across multiple processes within the Project Resource Management knowledge area to ensure that resource planning and estimation are based on specialized knowledge and historical experience.
* Plan Resource Management (Choice A): Expert judgment is used here to determine the best approach for identifying and managing resources. Experts provide insight into the organizational culture, the need for specialized skills, the legal requirements for labor, and the most effective ways to structure the Resource Management Plan.
* Estimate Activity Resources (Choice B): Expert judgment is critical in this process to determine the specific types and quantities of material, human resources, equipment, or supplies required for each activity. Experts with experience in similar technical work can accurately predict how many resources are needed and what specific competencies are required to complete a task successfully.
* Manage Team (Choice C): While a project manager uses interpersonal skills to manage a team, Expert Judgment is not formally listed as a primary tool/technique for the Manage Team process in the same way it is for the planning and estimation phases. Manage Team focuses more on Interpersonal and Team Skills (like conflict management and leadership).
Since both Plan Resource Management and Estimate Activity Resources officially utilize Expert Judgment as a defined Tool and Technique in the PMI framework, Choice D is the most accurate and comprehensive answer.

In the provided comic strip, the Project Manager/Product Owner (Lucia) is faced with a client (Tan) who wants to add a " new feature that will revolutionize the industry " late in the project. Even though the project is currently on track, adding a significant feature requires a disciplined approach to avoid scope creep.
* Why Choice A is correct:
* Change Control Process: In any professional project environment, a new request must go through the formal Change Control Process. This ensures the impact on time, cost, and quality is assessed before any work begins.
* Agile/Iterative Approach: By mentioning " future iterations " and " prototypes, " this choice aligns with Agile best practices. Instead of blindly adding a massive feature, the team tests the idea through small-scale models (prototypes) to validate the " revolutionary " claim before committing full resources.
* Evidence-Based: Documenting end-user feedback ensures that the decision to include or exclude the feature is based on actual data rather than just the client ' s opinion.
Analysis of other options:
* B (Have the end user write a user story): While user stories are great, simply writing one doesn ' t address the impact of the change on the current project constraints. This skips the necessary assessment and approval steps.
* C (Check with the project team... restructure timeline): This is a reactive approach that assumes the feature must be added. A Project Manager should never restructure a timeline or reduce quantities until the change has been officially analyzed and approved.
* D (Enable a stakeholder change): This is vague and doesn ' t follow standard project management terminology. " Enabling a stakeholder change " is not a standard procedure for handling new feature requests.
Key Concept: The Project Management Institute (PMI) emphasizes that the Project Manager must be a " guardian of the scope. " When a client proposes a " revolutionary " idea late in the game, the correct professional response is to funnel that enthusiasm through the Change Control System (Choice A) to protect the project ' s baseline while still being open to future innovation.

In the PMBOKGuide, the Monitor Communications (formerly known as Control Communications in earlier editions) process is the process of ensuring the information needs of the project and its stakeholders are met.
The primary outputs of this process are:
* Work Performance Information (WPI): This is a core output of any monitoring and controlling process.
It involves taking the raw Work Performance Data (status of communication activities) and comparing it against the Communications Management Plan. This provides a processed summary of how communication is actually performing, such as whether stakeholders are receiving information on time or if they are satisfied with the level of detail provided.
* Change Requests: If the monitoring process reveals that the current communication strategy is ineffective or that stakeholders ' needs have changed, a change request is generated. These requests are processed through the Perform Integrated Change Control process and may result in adjustments to the project management plan or communication protocols.
* Project Management Plan Updates: Specifically, updates to the Communications Management Plan or the Stakeholder Engagement Plan based on the findings of the monitoring activities.
* Project Document Updates: This often includes updates to the Issue Log, Lessons Learned Register, and Stakeholder Register.
Comparison with other options:
* A. Expert judgment: This is a Tool and Technique, not an output.
* C and D. Issue log: While the issue log is often updated during this process, it is considered a Project Document Update rather than a primary standalone output of the process in the same category as Work Performance Information. Furthermore, Option B represents the two most definitive and critical outputs that drive project action (analysis and formal change).

According to the PMBOKGuide, specifically within the Perform Quantitative Risk Analysis process, Expected Monetary Value (EMV) is a statistical concept that calculates the average outcome when the future includes scenarios that may or may not happen (i.e., analysis under uncertainty).
* The Concept: EMV is used to quantify risks (both threats and opportunities) to determine the overall contingency reserve or to choose between different project paths using a Decision Tree.
* The Formula:
$$EMV = \sum (P \times I)$$
Where:
* $P$ = Probability of the outcome occurring.
* $I$ = Impact (the monetary value of the outcome).
* Calculation Method: You identify every possible outcome, multiply the monetary value (Impact) of that outcome by its probability of occurrence, and then sum all the results together.
* Opportunities are expressed as positive values.
* Threats are expressed as negative values.
Analysis of Other Options:
* A. Value of each... multiplied by probability: This describes the calculation for a single risk event, but it does not account for the total EMV of a project or a decision node, which requires the sum of all potential outcomes.
* B and D. Probability of non-occurrence: These are incorrect. Risk management calculations focus on the probability of the event actually happening ($P$). While the probability of non-occurrence ($1 - P$) exists, it is not the multiplier used to determine the expected value of the risk itself.

According to the PMBOKGuide (Project Management Body of Knowledge), specifically within the Project Schedule Management and Project Cost Management knowledge areas, Parametric Estimating is an estimating technique in which an algorithm is used to calculate cost or duration based on historical data and project parameters.
* The Calculation: Parametric estimating uses a statistical relationship between historical data and other variables. In this specific scenario, the calculation is straightforward:
$$\text{Total Hours} = \frac{\text{Total Units to be Produced}}{\text{Production Rate per Hour}}$$
$$\text{Total Hours} = \frac{12,000 \text{ units}}{120 \text{ units/hour}} = 100 \text{ hours}$$
* Application (Option A): The result of 100 hours is the mathematically accurate estimate derived from the provided parameters.
* PMI Context: This technique is often used for work that is highly repetitive and standardized. It provides a higher level of accuracy than Analogous Estimating, provided that the underlying data used in the parameter (the 120 units per hour) is reliable and scalable. It is frequently applied in manufacturing, software lines of code, or construction (e.g., cost per square foot).
In the PMI framework, Parametric Estimating can be applied to an entire project or specific parts of a project, in conjunction with other estimating methods, to refine the project ' s schedule and budget baselines.