According to the PMBOKGuide, the Control Schedule process is the process of monitoring the status of the project activities to update project progress and manage changes to the schedule baseline to achieve the plan.
* Variance Analysis: This is a key tool and technique used in this process. It involves comparing the planned dates (the baseline) to the actual start and finish dates to determine if there is a deviation.
* Specific Metrics: In schedule control, variance analysis focuses on:
* Schedule Variance (SV): $SV = EV - PV$
* Schedule Performance Index (SPI): $SPI = EV / PV$
* Purpose: By performing variance analysis, the project manager can determine the cause and degree of variance relative to the schedule baseline and decide whether corrective or preventive action is required.
Analysis of Other Options:
* A. Performance measure: While performance measurement is the goal of the process, " Performance Reviews " or " Data Analysis " are the technical terms for the tools used.
* B. Baseline schedule: The schedule baseline is a primary input to the Control Schedule process, used as the reference point for comparison, but it is not a " technique " itself.
* C. Schedule network analysis : This is a technique primarily used in the Develop Schedule process to create the initial schedule model; it is not the primary tool for controlling it once execution begins.

According to the PMBOKGuide (Project Management Body of Knowledge), specifically within the introduction to the Project Scope Management knowledge area:
* Defining and Controlling Scope (Option C): This is the primary and fundamental purpose of Project Scope Management. It ensures that the project includes all the work required, and only the work required, to complete the project successfully. It is focused on defining the project boundaries-what is
" in scope " and what is " out of scope " -and implementing controls to prevent unauthorized changes (scope creep).
* Developing a Detailed Description (Option A): This describes the Define Scope process specifically.
While it is a critical part of scope management, it is a sub-component (producing the Project Scope Statement) rather than the primary concern of the entire knowledge area.
* Requirements Management (Option B): This describes the Plan Scope Management or Collect Requirements processes. Requirements are the foundation of scope, but scope management goes beyond documentation to include the actual execution and control of the work boundaries.
* Formalizing Acceptance (Option D): This refers specifically to the Validate Scope process. This is the closing mechanism for scope components but does not encompass the entire management philosophy of the knowledge area.
In the PMI framework, Project Scope Management is the " anchor " for the other constraints. Without a clearly defined and controlled scope, it is impossible to provide accurate estimates for schedule or cost. The Project Manager must constantly refer back to the Scope Baseline (comprised of the Scope Statement, WBS, and WBS Dictionary) to ensure the team remains focused on the authorized objectives.

According to the PMBOKGuide, the Develop Project Charter process involves high-level planning and alignment between the sponsor, the project manager, and key stakeholders. The Project Charter serves as the foundation for the project, authorizing its existence and providing the project manager with the authority to apply organizational resources to project activities.
* Why Choice A (High-level deliverables) is correct: At the initiation stage, the team does not yet have a detailed Work Breakdown Structure (WBS). Instead, the charter defines the high-level deliverables or " big-ticket items " that the project is expected to produce. This sets the boundaries for what the project will and will not include.
* Why Choice B (Success criteria) is correct: It is vital to define what " success " looks like before the project begins. Success criteria include measurable goals, such as finishing within a specific budget, meeting a technical standard, or achieving a specific ROI. This ensures that all stakeholders have a shared definition of a successful outcome.
* Why Choice C (Project objectives) is correct: Project objectives link the project to the organization ' s strategic goals. These are often broad statements (e.g., " To increase market share by 5% through a new mobile app " ) that explain why the project is being undertaken.
Analysis of other options:
* D (Phase transitions): While phase transitions are part of the project life cycle, the specific criteria and handovers for these transitions are typically detailed during the Project Management Plan development (specifically in the Life Cycle Description), rather than the high-level Project Charter.
* Cost: While a high-level budget or " summary budget " is often included in a charter, the detailed " Cost
" analysis and cost baselines are developed much later during the planning process. In a " choose three " scenario, Deliverables, Success Criteria, and Objectives represent the core strategic alignment required to authorize the project.
By focusing on these three elements, the Project Manager ensures that the project starts with a clear mandate, a defined goal, and a baseline for measuring performance from the very beginning.

According to the PMBOKGuide, the Plan Quality Management process is the process of identifying quality requirements and/or standards for the project and its deliverables, and documenting how the project will demonstrate compliance with quality requirements and/or standards.
The primary inputs for this process include:
* Project Management Plan: Specifically the requirements management plan, risk management plan, stakeholder engagement plan, and the scope baseline (which contains the project scope statement and WBS).
* Project Documents: Key documents used as inputs include the assumption log, requirements documentation, requirements traceability matrix, risk register, and stakeholder register.
* Enterprise Environmental Factors (EEF): These include governmental regulations, rules, standards, and guidelines specific to the application area.
* Organizational Process Assets (OPA): These include the organization's quality policy, procedures, and historical databases from previous projects.
Analysis of Other Options:
* A. Quality metrics, project documents, and financial performance: Quality metrics are an output of the Plan Quality Management process, not an input. Financial performance is generally not a direct input to quality planning.
* B. Quality management plan, project documents, and quality metrics: Both the Quality Management Plan and Quality Metrics are outputs of this specific process. They cannot be inputs to the process that creates them.
* D. Project management plan, quality metrics, and project documents: Again, quality metrics are an output of this process. This option incorrectly identifies an output as an input.

According to the PMBOKGuide, specifically within the Control Costs process of Project Cost Management, the To-Complete Performance Index (TCPI) is a specialized metric used to determine the efficiency required for the remaining work.
* Definition: The TCPI is a measure of the cost performance that must be achieved with the remaining resources to meet a specific management goal, such as the Budget at Completion (BAC) or the Estimate at Completion (EAC).
* The Formula: It is calculated as the ratio of the " cost to finish the outstanding work " to the " remaining budget. "
* To meet the BAC:
$$TCPI = \frac{BAC - EV}{BAC - AC}$$
* To meet the EAC:
$$TCPI = \frac{BAC - EV}{EAC - AC}$$
* Interpretation:
* If TCPI > 1.0: The remaining work must be performed more efficiently than originally planned to stay within the budget (harder to achieve).
* If TCPI < 1.0: The remaining work can be performed less efficiently than originally planned while still meeting the goal (easier to achieve).
* Purpose: It provides the project manager with a " reality check. " If the calculated TCPI is significantly higher than the current Cost Performance Index (CPI), the project goal may be unrealistic.
Comparison with other options:
* A. Budget at Completion (BAC): This is the total planned budget for the project. It is a static figure used in the TCPI calculation, not the ratio of remaining work to remaining funds.
* B. Earned Value Management (EVM): This is the overarching methodology that combines scope, schedule, and resource measurements. TCPI is a specific tool within the EVM framework.
* D. Cost Performance Index (CPI): This measures the cost efficiency of work already performed (
$$CPI = \frac{EV}{AC}$$
). While TCPI looks forward at what efficiency is required, CPI looks backward at what efficiency has been achieved.