Free PGMP Practice Test

Projects within a program are initiated on an as-needed basis throughout the program's life cycle to achieve its strategic objectives. The initiation of components is a key activity within the Program Benefits Delivery phase, which is iterative. As the program progresses and delivers incremental benefits, new projects may be authorized and started to build upon previous results or address emerging requirements. This dynamic process continues until the program has delivered its intended benefits and is ready to transition into the Program Closure phase. Therefore, project initiation is not a single event but occurs whenever necessary during the active delivery stages of the program.

B: "Program execution" is a general term. The specific PMI phase is Program Benefits Delivery, where projects are initiated iteratively, not as a single execution event. C: The Program Initiation phase focuses on authorizing the program itself and developing the program charter, not on initiating its individual component projects. D: Program Planning involves developing the program management plan and roadmap, which identifies components, but the formal authorization and initiation of projects occur later.

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 1.5.3.2, Program Benefits Delivery Phase, p. 21. "During this phase, program components are initiated, planned, executed, and transitioned..."

2. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Figure 1-6, Program Management Performance Domains and Program Life Cycle Phases, p. 20. This figure illustrates that component initiation and planning are activities that occur within the Program Benefits Delivery phase.

3. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 3.4.3, Program Benefits Delivery Phase, p. 50. "During this phase, the program manager and the program governance board provide oversight and integrate the work being performed by the program components... New components may be initiated, planned, and authorized..."

According to the Project Management Institute's (PMI) official standards, resources are the inputs required to perform program work. This includes team members, supplies, equipment, materials, and facilities. Staff members (A) and equipment (D) are explicitly defined as human and physical resources, respectively. While contracts (B) are managed within a program, they are legal instruments used in procurement to acquire resources or services, not resources themselves. However, quality (C) is fundamentally different; it is a performance characteristic, a conformance requirement, and a key performance indicator. It is a standard to be achieved, not a resource to be consumed or allocated, making it the correct exception.

A. Staff members: These are the primary human resources managed within the Program Resource Management performance domain.
B. Contracts: While not a resource, a contract is a tangible instrument for acquiring resources. Quality is a more abstract concept representing a performance standard, making it a better exception.
D. Equipment: This is a classic example of a physical resource that is identified, acquired, and managed throughout the program lifecycle.

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.).

For Correct Answer (C): The Glossary defines a resource as "Team members

supplies

equipment

materials

and facilities" (p. 208). This definition excludes 'quality'. The Program Quality Management performance domain (Section 5.4

p. 77) treats quality as a set of processes for meeting stakeholder objectives

not as a consumable resource.

For Incorrect Options (A

D): The Program Resource Management performance domain (Section 5.5

p. 83) is explicitly concerned with "processes to identify

acquire

and manage the resources

" specifically citing human and physical resources (staff and equipment).

For Incorrect Option (B): The Program Procurement Management performance domain (Section 5.6

p. 89) covers the management of contracts to acquire external results

distinguishing them from the program's internal resources.

After a feasibility analysis confirms that a program is viable and aligned with strategic objectives, the next critical step is to formally define the program's purpose and desired future state. Developing a program vision statement accomplishes this. The vision statement is a high-level, inspirational declaration of the program's long-term outcome. It provides direction, aligns stakeholders, and serves as a constant reference point throughout the program lifecycle, ensuring all subsequent planning and execution activities are focused on achieving the intended end state. This step is fundamental to the Program Definition Phase.

B. Review of strategic goals against any external environmental factors: This analysis is a key input to the business case and feasibility study itself, not a step that follows it.
C. Identification and documentation of the initial risks for ERP software implementation: High-level risks are typically identified during the feasibility study. A detailed risk register is developed later, guided by the program's defined vision and scope.
D. Mapping of the financial benefits to the ERP software's functionality: This is part of developing the business case and benefits realization plan. A high-level version is done for feasibility; detailed mapping occurs during program planning.

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.).

Page 32

Figure 3-4: This figure illustrates the program management life cycle

showing that the "Program Definition Phase" follows "Program Formulation" (where feasibility is assessed).

Section 3.2.1

Program Definition Phase Activities (Page 34): This section outlines the activities performed after a program is approved to proceed based on the business case and feasibility. It includes defining the program

which involves establishing its vision

mission

and objectives.

Appendix X3.2

Program Strategy Alignment (Page 101): This section explicitly states

"The program manager works with the sponsor and the program governance board to develop the program vision and mission statements that are aligned with the organization's strategic vision and goals." This confirms that developing the vision is a core program management activity in the early stages.

2. Serra

C. E. M.

& Kunc

M. (2015). Benefits Realisation Management and its influence on project success and on the execution of business strategies. International Journal of Project Management

33(1)

53-66.

Section 3.1: The paper discusses the process of translating organizational strategy into programs. It emphasizes that after an initiative is justified (i.e.

deemed feasible)

its objectives and vision must be clearly defined to guide the realization of benefits

reinforcing the sequence of feasibility followed by vision development. (DOI: https://doi.org/10.1016/j.ijproman.2014.03.011)

The program governance board is the primary body responsible for providing strategic direction, oversight, and decision-making authority for a program. To ensure the program's objectives, requirements, and roadmap are aligned with the enterprise's strategic plan, the program manager must work directly with this board. The board validates that the program's intended outcomes will contribute to the organization's strategic objectives and provides the necessary approvals and resources. This collaboration is a core function within the Program Strategy Alignment performance domain.

B. The program management office (PMO) provides support, standards, and methodologies but does not have the authority to approve or ensure strategic alignment.
C. The change control board (CCB) focuses on approving or rejecting changes to the program's scope, schedule, and budget at a tactical level, not overall strategic direction.
D. Project managers are responsible for delivering program components and operate within the strategic framework set by the program manager and governance board.

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 3.4

Program Governance

p. 43. This section states

"Program governance is the framework

functions

and processes that guide program management activities in order to create a unique product

service

or result to meet organizational

strategic

and operational goals."

2. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Table 4-1

Program Strategy Alignment: Inputs and Outputs of Program Manager Activities

p. 54. This table explicitly lists the "Program Governance Board" as a key stakeholder for the development and approval of the Program Roadmap and ensuring it aligns with organizational strategy.

3. Thiry

M. (2015). A Framework for Value Management Practice. In Program Management: A Life Cycle Approach (pp. 115-140). John Wiley & Sons

Inc. This chapter discusses how governance structures

such as a steering committee or governance board

are essential for linking program activities to the organization's strategic business objectives.

A Gantt chart is a specific type of bar chart used in project and program management to illustrate a schedule. It visually represents activities or tasks listed on the vertical axis against a time scale (a calendar) on the horizontal axis. The length and position of each horizontal bar correspond to the start date, end date, and duration of an activity, making it the precise tool for representing the duration of activities against a calendar.

A. A pie chart illustrates numerical proportions of a whole; it does not represent data over a time-based calendar.
B. A scatter chart is used to display the relationship between two numerical variables, not for scheduling activities over time.
D. A Pareto chart is a quality management tool that combines a bar and line graph to identify the most significant factors in a dataset (the 80/20 rule).

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 6.5.3.1 Data Representation, p. 210. "Bar charts, also known as Gantt charts, represent schedule information where activities are listed on the vertical axis, dates are shown on the horizontal axis, and activity durations are shown as horizontal bars placed according to start and finish dates."

2. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 5.3.3.2 Scheduling Tools, p. 69. This section notes that program schedules are commonly displayed as Gantt charts, which "provide a graphical representation of the schedule information."

3. Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (12th ed.). John Wiley & Sons. Chapter 12, Section 12.9, p. 428. The text defines Gantt charts as "bar charts... The length of the bar is proportional to the duration of the activity."

The process described is a weighting system, a quantitative source selection analysis method. In this technique, the program team establishes a set of evaluation criteria (the "categories") and assigns a numerical weight to each based on its relative importance. Vendors are then scored against each criterion (assigned "points"). The final score is calculated by multiplying the score by the weight for each criterion and summing the results. This provides an objective, rankable basis for comparing proposals and selecting the most suitable vendor, aligning the choice with the program's strategic objectives and priorities.

A. Benefit-cost analysis: This is a financial tool used to compare the expected benefits of an option against its costs, typically expressed as a ratio, not a multi-criteria scoring system.
B. Screening system: This is a preliminary filter that establishes pass/fail criteria to weed out vendors who do not meet minimum requirements before a more detailed evaluation.
D. Preferred vendor list: This is a list of pre-qualified suppliers from which a selection might be made; it is not the evaluation method itself. ---

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 12.2.2.5 Source Selection Analysis

p. 487. The guide explicitly defines a weighting system as a method to "assign a numerical score to each of the seller proposals" based on weighted selection criteria.

2. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 5.5

Program Procurement Management

pp. 97-100. This section discusses the need for consistent and effective procurement processes at the program level

for which tools like weighting systems are essential for making objective

benefit-oriented decisions.

3. Ho

W.

Xu

X.

& Dey

P. K. (2010). Multi-criteria decision making approaches for supplier evaluation and selection: A literature review. European Journal of Operational Research

202(1)

16–24. This academic review discusses various supplier selection methods

identifying the weighted scoring method as a fundamental and widely used multi-criteria decision-making (MCDM) approach. https://doi.org/10.1016/j.ejor.2009.05.009

Project documentation, which includes lessons learned, historical information, risk registers, and final reports, is a critical component of an organization's process assets. These documents are archived upon project or program completion. They serve as an invaluable knowledge base for future project and program managers, enabling them to leverage past successes, avoid repeating mistakes, and improve planning and execution. This practice of capturing and reusing knowledge is fundamental to organizational learning and maturing project management capabilities, directly helping future initiatives.

A. Sponsor: A sponsor is a person fulfilling a specific role for a particular project; they are not a transferable asset for all future projects.
B. Charter: A project charter is a document that authorizes a single, specific project and is not a direct tool for managing different future projects.
C. Stakeholder: Stakeholders are individuals or groups with an interest in a specific project; they are not a reusable resource for subsequent projects.

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 3.4.3.2, Knowledge Management, p. 53. This section explains that knowledge management processes are used to collect, store, and disseminate information to "improve the performance of the program and future programs."

2. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 5.6.3.2, Program Information Management, p. 111. This section states, "The program manager is responsible for ensuring that all program documentation is updated and archived in the knowledge base" as part of program closure, explicitly for future use.

3. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 2.3, Organizational Process Assets, p. 39. This section defines Organizational Process Assets as including the "corporate knowledge base," which contains "lessons learned and historical information" from previous projects to be used on future ones.

The program transition plan is the specific document that outlines the strategy and activities for handing over the program's outputs, outcomes, and benefits to the receiving operational organization. This plan details the orderly release of program-specific resources and the transfer of ongoing resources, knowledge, and responsibilities required for sustainment. It ensures a smooth handover at the end of a phase or the entire program, facilitating the continued realization of benefits by the operational entity.

A. The resource management plan details how resources are acquired, allocated, and managed during the program, not the specific process of transferring them to operations.
C. The communications management plan governs the flow of information, which is part of the transition, but it does not guide the actual transfer activities themselves.
D. The benefits management plan identifies benefits and how they will be sustained, but the transition plan provides the actionable steps for the handover to achieve that sustainment.

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 5.5, Program Transition and Closure Activities, p. 93. "The program manager develops the program transition plan... This plan describes how the program's benefits will be transitioned to the operational or sustaining organization. The transfer of resources, knowledge, and responsibility from the program to the sustaining organization is a key part of this plan."

2. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Appendix X4, Program Management Artifacts, Section X4.11 Program Transition Plan, p. 161. This section lists the contents of a transition plan, which includes "Transition scope, assumptions, constraints, and schedule," "Resources to be transferred," and "Knowledge to be transferred."

Paralingual communication refers to the vocal aspects of speech that are separate from the actual words used. This includes elements like tone of voice, pitch, volume, and inflection. These cues convey emotion, emphasis, and sincerity, adding a critical layer of meaning to verbal communication. When using text-based methods like email, these paralingual cues are completely lost. The recipient cannot hear the sender's tone or inflection, which can easily lead to misinterpretation of the message's intent and emotional context, a significant risk in complex program stakeholder communications.

A. Barriers: Barriers are obstacles that hinder effective communication (e.g., language, culture), not a component of the verbal message itself.
B. Noise: Noise is any interference in the communication channel that distorts the message, not an inherent aspect of verbal communication.
C. Nonverbal: Nonverbal communication includes body language and facial expressions. While also lost in email, it is distinct from the verbal aspects of communication, which is what the question specifically asks about.

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section 5.4, Program Communications Management, discusses the selection of communication methods. It notes that face-to-face communication is preferred for sensitive topics because it "allows for the observation of body language and tone of voice," implicitly acknowledging that text-based methods lack these paralingual elements (p. 87).

2. Mehrabian, A. (1981). Silent Messages: Implicit Communication of Emotions and Attitudes (2nd ed.). Wadsworth. This foundational work in communication studies breaks down the components of a message, attributing significant meaning to vocal cues (38%)—what is now termed paralinguistics—separate from the words themselves (7%) and nonverbal body language (55%). This highlights that paralingual cues are a distinct and critical part of communication lost in text.

3. Byron, K. (2008). Carrying too heavy a load? The communication and miscommunication of emotion by email. Academy of Management Review, 33(2), 309–327. https://doi.org/10.5465/amr.2008.31193163. This peer-reviewed article details how text-based media like email are "lean" because they filter out crucial paralinguistic cues (e.g., tone of voice, volume, inflection) and nonverbal cues, increasing the likelihood of miscommunicating emotional intent (p. 311).

The phrase "the degree to which a set of inherent characteristics fulfills requirements" is the official definition of quality according to the Project Management Institute (PMI) and the International Organization for Standardization (ISO). In program management, quality is not about perfection but about ensuring that the program's outputs and outcomes meet the specified requirements and are fit for their intended purpose, thereby contributing to the realization of program benefits. The program manager establishes the overarching quality policy and framework to be applied across all component projects.

A. Scope defines the boundaries and the work to be performed, not the measure of how well that work meets its requirements.
B. A project phase is a collection of logically related activities, representing a division of the project lifecycle, not a measure of fulfillment.
C. A regulation is a mandatory requirement imposed by a governmental body; it is a type of requirement, not the degree of fulfillment.

1. Project Management Institute. (2017). The Standard for Program Management (4th ed.). Section X3

Glossary

p. 213. Newtown Square

PA: Project Management Institute.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 8

Project Quality Management

p. 274; and Appendix X1

Glossary

p. 718. Newtown Square

PA: Project Management Institute.

3. International Organization for Standardization. (2015). ISO 9000:2015: Quality management systems — Fundamentals and vocabulary. Section 3.6.2. Geneva

Switzerland: ISO.