Download Latest CAPM Questions

According to the PMBOK® Guide (Project Management Body of Knowledge), specifically within the Project Quality Management knowledge area and the Manage Quality or Control Quality processes:

Pareto Diagram (Option D): This is a specific type of vertical histogram used to identify the vital few sources that are responsible for causing most of a problem ' s effects. It is based on the Pareto Principle (the 80/20 rule), which suggests that 80% of problems are due to 20% of the causes. In the diagram, categories are ordered by the frequency of occurrence, helping the project team prioritize their corrective actions.

Work Breakdown Structure (Option A): This is a hierarchical decomposition of the total scope of work to be carried out by the project team. It looks like an organizational chart or an outline, not a statistical bar chart.

Context Diagram (Option B): This is a visual representation of the functional scope of a system, showing the actors (people or other systems) that interact with it. It uses boxes and arrows to show data flow.

Control Chart (Option C): This is a line graph used to determine if a process is stable or has predictable performance. It features a center line, upper control limits (UCL), and lower control limits (LCL). It does not use descending bars.

In the PMI framework, the Pareto Diagram is one of the " Seven Basic Quality Tools " and is essential for focusing resources on the most significant issues to achieve the greatest improvement in quality.

According to the PMBOK® Guide and the Standard for Project Management, the entity described is the Change Control Board (CCB). This body is a formally constituted group responsible for the Perform Integrated Change Control process.

The specific roles and responsibilities of the CCB as defined in PMI study guides include:

Reviewing and Evaluating: Analyzing Change Requests (CRs) for their impact on project constraints such as scope, schedule, cost, and quality.

Decision Making: Approving, delaying (deferring), or rejecting changes to the project.

Recording and Communicating: Ensuring that all decisions are documented in the Change Log and communicated to the relevant stakeholders to ensure alignment.

The other options are incorrect based on the following PMI definitions:

Project Team: This group is responsible for performing the project work to achieve project objectives. While they may request changes or provide technical input on a change ' s impact, they do not hold the formal authority to approve or reject them against the baseline.

Focus Group: This is a data-gathering technique used in the Collect Requirements process. It brings together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product or service.

Project Stakeholders: This is a broad term for any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project. While the CCB is composed of stakeholders, the general stakeholder population does not manage the formal change control process.

As per the PMI Lexicon of Project Management Terms, the CCB’s authority is defined within the Change Management Plan, which is a subsidiary component of the Project Management Plan.

According to the PMBOK® Guide, specifically within the Monitor Risks and Implement Risk Responses processes, a project manager must act decisively when a known or unknown risk materializes into an issue.

Why Choice A is correct:

Risk Response Implementation: A professional project manager should have identified " supplier failure " as a potential risk during the planning phase. The Risk Register would contain a pre-approved Risk Response Plan (e.g., a secondary supplier, expedited shipping, or technical alternatives).

Resource Allocation: To address a three-month delay, the PM may need to utilize contingency reserves or reallocate human and material resources to perform " crashing " or " fast-tracking " once the concrete arrives to compress the schedule.

Structured Approach: Following the plan ensures that the response is calculated and authorized, rather than reactive or emotional.

Analysis of other options:

B (Consult legal/SMEs to avoid failure): While legal advice might be necessary for contract breaches, the primary goal of the PM is to " put the project back on track. " Legal action is a recovery of damages, not a schedule recovery technique. Furthermore, " avoiding failure " is proactive; the failure has already occurred, so the PM must now move to mitigation or corrective action.

C (Extend delivery and use management reserve): Management reserves are typically for " unknown-unknowns " and require senior management approval. Simply extending the deadline is a passive move that doesn ' t " overcome " the problem or put the project " back on track " —it simply moves the goalposts.

D (Accept penalties): This is a " passive acceptance " strategy. In a high-impact scenario like a three-month construction delay, passive acceptance is rarely acceptable to stakeholders. The PM is expected to explore all possible corrective actions before resigning to penalties.

Key Concept: The Project Management Institute (PMI) emphasizes that the Risk Register is a living document. When an issue occurs, the PM evaluates the effectiveness of the planned response. If the original plan is insufficient, the PM should issue a Change Request to implement more aggressive recovery measures, ensuring the project aligns as closely as possible with the original Schedule Baseline.

According to the PMBOK® Guide, the Develop Project Charter process involves internal and external influences categorized as either Enterprise Environmental Factors (EEFs) or Organizational Process Assets (OPAs).

Enterprise Environmental Factors (EEFs): These are conditions, not under the control of the project team, that influence, constrain, or direct the project. They can be internal (e.g., organizational culture, infrastructure) or external (e.g., currency rates, legal requirements).

Marketplace Conditions: This is a specific external EEF. It refers to the current state of the market, including competitor performance, market share, brand recognition, and trademarks. These factors help determine if a project is viable or necessary to maintain a competitive edge.

Other EEFs for Project Charter:

Government or industry standards (e.g., regulatory agency regulations, codes of conduct).

Legal and regulatory requirements and/or constraints.

Organizational culture and political climate.

Governance framework.

Stakeholder expectations and risk thresholds.

Comparison with other options:

A. Organizational standard processes: These are Organizational Process Assets (OPAs). They are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization.

C. Historical information: This is a component of OPAs (specifically the corporate knowledge base). It includes lessons learned and records from previous projects used to help authorize the current one.

D. Templates: These are OPAs. They are pre-formatted documents (like a Project Charter template) provided by the organization to ensure consistency across projects.