The correct answer is A . Earned Value Analysis, within the earned value management family of techniques, uses integrated performance measures to determine project cost and schedule performance. It links work accomplished with the budget authorized for that work and compares it against actual cost and planned progress. This makes it more powerful than simple expenditure tracking because it shows whether the project is earning value at the expected rate. Option B describes cost variance , not EVA. Cost variance is the budget deficit or surplus at a point in time, normally calculated as earned value minus actual cost. Option C describes the cost performance index , not EVA. CPI indicates cost efficiency by comparing earned value to actual cost. EVA is the broader analytical method; CV and CPI are specific measures used within earned value analysis. PMBOK defines earned value management as a methodology combining measures of scope, schedule, and resources to evaluate project performance and progress, which supports the integrated nature of EVA. The uploaded question set lists option A as the definition choice for EVA.

Reference topics: earned value analysis, earned value management, cost performance, schedule performance, cost variance, CPI.

The correct answer is B . The project brief should include information about project duration, at least at a high level or as an initial estimate. A project brief is used to summarize the proposed project so that decision-makers can evaluate whether it should be initiated. It should provide enough information to understand the project context, objectives, rationale, high-level scope, target outcomes, key milestones, time frame, and major assumptions or constraints. Duration is especially important because it affects resource planning, cost estimation, feasibility, supplier coordination, governance decisions, and expected benefit timing. Lana included project context and objectives, but omitted duration and stated that it could not be determined. While exact duration may not be fully known at the brief stage, a preliminary time frame, assumption-based estimate, or duration range should still be provided. Her verbal statement during discussions does not replace properly documenting the duration in the project brief. A decision to initiate the project should be based on recorded information, not only informal explanation. Therefore, the omission was not acceptable. The source scenario explicitly states that duration was missing from the project brief and asks whether that omission is acceptable.

Reference topics: project brief, project duration, pre-project activities, project initiation, high-level planning, feasibility.

The correct answer is B. Reintroducing a familiar practice . Adaptive change refers to a comparatively low-complexity form of change where people are asked to return to, adjust, or apply something already familiar. It usually does not require a major shift in culture, mindset, technology, or organizational identity. Because the practice is already known, resistance may be lower than with more innovative or transformational changes, although communication, reinforcement, and stakeholder engagement are still required. Option A, introducing a practice new to the practitioners, is more disruptive because the affected people have no direct familiarity with the practice. Option C, introducing a practice that is new to the organization but not the industry, is closer to an innovative or transitional change because the organization must adopt something externally established but internally unfamiliar. Adaptive change is therefore associated with reintroducing or adjusting known practices rather than creating a radically new way of working. In project management, understanding the type of change helps determine communication, training, stakeholder engagement, transition support, and resistance-management needs. The uploaded source lists this question under the ISO 21502 question set and provides these three alternatives.

Reference topics: adaptive change, organizational change, stakeholder readiness, transition management, change complexity.

The correct answer is A . The purpose of planning quality is to define the applicable standards and quality requirements for the project and its outcomes. Quality planning establishes what “acceptable quality” means before work is performed. It identifies relevant standards, customer requirements, regulatory requirements, acceptance criteria, quality metrics, inspection needs, test approaches, responsibilities, and control methods. This allows the team to build quality into the work rather than discovering quality problems late. Option B describes quality assurance or quality management activities focused on ensuring that work is being performed in accordance with defined quality requirements and standards. Option C describes quality control, where results are checked, nonconformities are identified, and corrective action is taken to improve unsatisfactory performance. Planning quality is therefore the front-end definition phase: it clarifies the quality basis against which project work and outcomes will later be assessed. Without effective quality planning, the project team may deliver outputs that are technically complete but unacceptable to the customer or performing organization.

Reference topics: quality planning, quality standards, quality requirements, acceptance criteria, project outcomes.

The correct answer is A. Project brief . Allison created a short document that justified and summarized the key aspects of the proposed project: its nature and purpose, objectives, key milestones, expected completion time, and target audience. That description matches the purpose of a project brief. A project brief is normally prepared early to provide enough information for decision-makers to understand why the project should be initiated, what it is expected to achieve, what its high-level boundaries are, and whether it is worth authorizing. It supports the transition from an idea or need into an approved project. A project baseline, by contrast, is an approved reference point used to compare actual performance against planned scope, schedule, or cost. A project plan is more detailed and describes how the project will be executed, monitored, controlled, and closed. Allison’s document was prepared before formal approval and used to support project initiation, so it is not a baseline or a full plan. The scenario clearly states that the document justified and summarized the project and was presented before initiation approval.

Reference topics: project brief, pre-project activities, project initiation, business justification, authorization.

The correct answer is A. Informal . The communication methods described in the scenario—ad hoc discussions, notes, and text messages—are informal communication methods. Informal communication is typically flexible, rapid, conversational, and less structured than formal reports, contractual notices, approved minutes, governance submissions, or official project documents. Ross planned ad hoc discussions for complex and personal cases because direct informal interaction allows immediate clarification, natural language, and faster exchange of nuanced information. He also planned notes and text messages for simple and factual information, which supports quick transmission without the structure of formal reporting. Option B is incorrect because the scenario does not describe formal communication mechanisms such as official reports, controlled documents, steering committee papers, signed approvals, or contractual correspondence. Option C is not the best answer because both examples given are informal in nature. The communication plan is still a formal planning artifact, but the communication types selected within it are informal methods. The uploaded source scenario specifically frames the question around ad hoc discussions, notes, and text messages.

Reference topics: communication planning, informal communication, ad hoc discussion, text messages, communication methods, project information flow.

No. The project organization should be communicated to everyone involved in the project, not only to the project team. A project organization defines the roles, responsibilities, authorities, decision rights, reporting relationships, escalation routes, and interfaces needed to direct and manage the project. If this structure is communicated only to the project team, other involved parties may not understand how the project is governed, who has authority, who is accountable for decisions, how issues are escalated, or how coordination should occur. In the DND scenario, the project organization included the project office, project assurance, a customer representative, the project board, and work package leadership. These roles are not limited to the delivery team; they are part of the broader governance and management structure. Therefore, they must understand the organization model and their relationship to it. Communicating the structure only to the team creates ambiguity, weakens accountability, and may disrupt assurance, customer involvement, and governance control. The PMBOK also treats project communications as the processes required to ensure project information is planned, collected, created, distributed, stored, monitored, and disposed of appropriately.

Reference topics: project organization, communication, roles and responsibilities, stakeholder involvement, governance interfaces.

The correct answer is C. Project sponsor and project board . The project manager normally reports to the project sponsor and, where established, the project board. These governance roles provide direction, oversight, authorization, and decision-making authority for the project. The sponsor maintains the business link between the project and the sponsoring organization, while the project board may represent broader governance interests, including business, user, supplier, technical, or organizational perspectives. Reporting to these roles enables performance review, escalation, approval of significant changes, risk-based decisions, and continued justification. Option A is too narrow and too rigid because the project manager does not report only to top management in every project. Reporting arrangements depend on the project governance structure. Option B is also too broad because key stakeholders may receive information, but they are not necessarily the formal reporting authority. Stakeholder communications and governance reporting are related but not identical. A project manager may communicate with many stakeholders, but formal accountability reporting is directed to the sponsor and project board. The uploaded source question identifies sponsor and project board as the correct reporting destination.

Reference topics: project manager reporting, project sponsor, project board, governance reporting, accountability, project oversight.

The correct answer is A because, for a project that exists within a program, the program manager can act as the representative of the sponsoring organization or higher-level authority. A program coordinates related projects to obtain benefits and control that would not be available if the projects were managed separately. Therefore, a project within a program should align with program objectives, governance, benefits, dependencies, and reporting requirements. In that context, the project sponsor may report to, seek direction from, or coordinate with the program manager because the program manager represents the broader governance layer within which the project operates. Option B is incorrect because it reverses the authority relationship: the program manager usually provides higher-level coordination over program components, not subordinate reporting to an individual project sponsor. Option C is too rigid because not every project sponsor must report directly to top management; the reporting relationship depends on the organizational and governance context. PMBOK similarly distinguishes project management from program management and notes that program management seeks benefits and control not available when components are managed individually. The scenario question is recorded in the uploaded source set.

Reference topics: project within a program, program manager, sponsoring organization, project organization structure, governance hierarchy.

The correct answer is A . Project management progress evaluations should consult the project sponsor, project manager, and project team because these roles collectively hold the business, management, and delivery perspectives required to assess progress accurately. The sponsor is concerned with continued justification, business alignment, benefits, risks, funding, and stakeholder expectations. The project manager is responsible for directing and controlling the project work, integrating information, reporting performance, managing issues, and recommending corrective action. The project team provides direct insight into completed work, remaining work, quality conditions, technical problems, dependencies, assumptions, and emerging risks. Consulting only governance or assurance roles would provide oversight but may miss operational delivery realities. Consulting only work package leaders would be too narrow because it would exclude business justification and integrated project control. Progress evaluation requires evidence from the people who sponsor, manage, and perform the work. PMBOK similarly describes the project team as individuals who support the project manager in performing project work to achieve objectives. The source question set lists project sponsors, project managers, and their teams as the relevant consultation group.

Reference topics: progress evaluation, project sponsor, project manager, project team, project control, integrated reporting.