According to the PMBOKGuide, Analogous Estimating is a technique for estimating the duration or cost of an activity or a project using historical data from a similar activity or project. It is frequently used in the Estimate Costs and Estimate Activity Durations processes.
* How it Works: It uses the values of parameters-such as scope, cost, budget, and duration-or measures of scale (size, weight, complexity) from a previous, similar project as the basis for estimating the same parameter or measure for a current project.
* When to Use: It is generally used when there is a limited amount of detailed information about the project (e.g., in the early phases of a project).
* Accuracy and Cost: Analogous estimating is generally less costly and time-consuming than other techniques, but it is also generally less accurate. It is most reliable when the previous projects are similar in fact and not just in appearance, and the project team members preparing the estimates have the needed expertise.
* Top-Down Approach: This is often referred to as a " top-down " estimating technique because it looks at the project as a whole based on past performance rather than breaking it down into minute details.
Analysis of Other Options:
* A. Estimates are created by individuals or groups with specialized knowledge: This describes Expert Judgment. While expert judgment is often used during analogous estimating to determine if a past project is a valid comparison, the definition of analogous estimating specifically hinges on the use of historical data from similar projects.
* C. Estimates are created by analyzing data: This is a broad description of Data Analysis (such as Alternative Analysis or Reserve Analysis). While estimating involves data, it is not the specific definition of the analogous technique.
* D. Estimates are created at the task level and aggregated upwards: This describes Bottom-Up Estimating, which is the opposite of analogous estimating. Bottom-up estimating is more detailed and accurate but requires a well-defined WBS.

According to the PMBOKGuide, the Perform Integrated Change Control process is the process of reviewing all change requests; approving changes and managing changes to deliverables, organizational process assets, project documents, and the project management plan; and communicating the decisions.
Role of the Project Management Plan: The Project Management Plan is a primary input because it contains the baselines (scope, schedule, and cost) and the change management plan. To evaluate the impact of a change request, the Change Control Board (CCB) or the project manager must compare the request against the established plan to see how it affects the project ' s objectives.
* Specific Components Used:
* Change Management Plan: Provides the direction for managing the change control process and documents the roles and responsibilities of the Change Control Board (CCB).
* Configuration Management Plan: Describes how the items of the project are identified and defined.
* Scope, Schedule, and Cost Baselines: Used to assess the impact of changes on the project ' s overall performance.
Comparison with other options:
A). Expert judgment: This is a Tool and Technique used during the process to evaluate the technical and management implications of the change, not an input.
* B. Seller proposals: These are typically inputs to the Conduct Procurements process, where the organization evaluates bids from potential vendors.
* C. The project charter: This is the output of the Develop Project Charter process and is used as an input to the Develop Project Management Plan and Identify Stakeholders processes. It is generally too high- level to serve as the functional baseline for Integrated Change Control.

According to the PMBOKGuide, specifically within the Control Costs process of Earned Value Management (EVM), forecasting involves estimating the future financial performance of the project based on the information available at the time of the evaluation.
When a sponsor asks for the forecast of the total project cost at completion, the metric used is the Estimate at Completion (EAC).
Definition: The EAC is the expected total cost of completing all work expressed as the sum of the actual cost to date and the estimate to complete.
* Purpose: While the Budget at Completion (BAC) tells you what you planned to spend, the EAC tells you what you are actually likely to spend by the time the project is finished, given the current performance trends (CPI and SPI).
* Calculation: There are several ways to calculate EAC depending on whether the current variances are seen as typical or atypical, but the most common " forecasting " formula is:
$$EAC = \frac{BAC}{CPI}$$
(This formula assumes that the project will continue to perform at the same cumulative Cost Performance Index encountered to date.) Analysis of other choices:
Choice A (BAC - Budget at Completion): This is the total planned budget for the project. It is a static baseline and does not account for actual performance or overruns; therefore, it is not a " forecast. "
* Choice C (ETC - Estimate to Complete): This represents the expected cost to finish all the remaining work. It is only a portion of the total cost. To get the total project cost, you would need to add the Actual Cost (AC) to this figure ($EAC = AC + ETC$).
* Choice D (WBS - Work Breakdown Structure): This is a hierarchical decomposition of the total scope of work. While it is used to build the budget, it is a planning tool, not a mathematical forecasting metric.

According to the PMBOKGuide (Project Management Body of Knowledge), specifically within the Project Integration Management knowledge area:
* Perform Integrated Change Control (Option D): This is the process of reviewing all change requests; approving changes and managing changes to deliverables, organizational process assets, project documents, and the project management plan; and communicating their disposition. PMI explicitly states that this process is conducted from project inception through completion and is ultimately the responsibility of the project manager. While a Change Control Board (CCB) may be responsible for approving or rejecting changes, the project manager oversees the entire integrated process to ensure that no change is made in isolation without considering its impact on all project constraints.
* Monitor and Control Project Work (Option B): While also performed throughout the project, this process is focused on tracking, reviewing, and reporting the overall progress to meet the performance objectives defined in the project management plan. It is the " parent " process that identifies the need for a change, but the formal management of that change happens in Perform Integrated Change Control.
* Control Quality (Option A): This process is focused on 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.
* Control Scope (Option C): This is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. It is a specialized control process, whereas Integrated Change Control covers all baselines.
In the PMI framework, Perform Integrated Change Control is the central " funnel " through which all change requests must pass, ensuring the integrity of the project ' s baselines from the day the project is chartered until the day it is closed.

According to the Agile Practice Guide (jointly developed by PMI and Agile Alliance) and the Scrum Guide, Agile projects are centered around the delivery of a Potentially Shippable Product Increment.
Why Choice B is correct: In Agile, functionality that meets the Definition of Done (DoD) and has been reviewed/accepted by the stakeholders during the Sprint Review can be released. One of the core principles of the Agile Manifesto is " Working software is the primary measure of progress. " If a specific user story or feature is complete and provides value, it should not be held back by other features that are not yet finished.
Agile allows for decoupled releases, where deployment to production can happen independently of the Sprint cycle, provided the increment is stable and valuable.
Analysis of other options:
A (Demo the incomplete feature at the sprint retrospective): This is incorrect. The Sprint Retrospective is for process improvement (team, tools, and relationships), not for product demonstrations. Demos only occur in the Sprint Review.
C (Wait to complete all user stories that are in development): This contradicts the Agile principle of iterative delivery. Waiting for all stories to be finished mimics a Waterfall " Big Bang " release and delays the realization of value.
D (Continue with sprints until the product backlog is empty): A Product Backlog is a living document and is rarely " empty. " Waiting for every possible item to be finished before deploying would prevent the team from receiving early ROI and user feedback.

The team should move the completed, reviewed items to production (or the " Done " column) and move the incomplete functionality back to the Product Backlog or into the next Sprint Backlog to be addressed in a future iteration.