PMI Certified Associate in Project Management CAPM Exam Questions

Answer : B, D

According to the PMBOK Guide, the Control Procurements process is the process of managing procurement relationships, monitoring contract performance, making changes and corrections as appropriate, and closing out contracts.

The two key benefits identified in the PMI standards are:

B . Ensures that contract performance meets the terms of the legal agreement: This process involves both the buyer and seller. It ensures that the seller's performance meets the project's requirements and that the buyer performs according to the terms of the legal contract (such as making timely payments). It involves reviewing and documenting how a seller is performing to ensure the desired results are achieved.

D . Assures that legal agreements guide contract closings: Control Procurements includes the administrative activities involved in finalizing a contract. It ensures that all deliverables have been accepted, all payments have been made, and all contractual obligations have been fulfilled before the contract is formally closed.

Analysis of other options:

A and E (Make-or-buy decisions and contract type selection): These are key benefits and activities of the Plan Procurement Management process. These decisions must be made during the planning phase, well before a contract is active.

C (Vendor selection): This is the primary focus of the Conduct Procurements process, which involves receiving seller responses, selecting a seller, and awarding a contract.

Per the PMI standards, Control Procurements is unique because it has a significant legal component, requiring the project team to be aware of the legal implications of the actions taken when managing the relationship with the seller.

Answer : D

According to the Agile Practice Guide and the PMBOK Guide, specifically during Backlog Refinement (Grooming), user stories must be refined until they are 'Ready' for the team to pull into an iteration.

Definition of Ready (DoR): For a team to understand the work needed to complete a story, the story must contain Detailed Acceptance Criteria. These criteria define the boundaries of the user story and provide a specific checklist that must be met for the story to be considered 'Done.'

Determining Effort: Acceptance criteria are essential for the team to estimate the effort (Story Points) required. Without these details, the team cannot know if a story is a simple task or a complex endeavor. They act as the 'test cases' that verify the functional requirements from the user's perspective.

Eliminating Ambiguity: During grooming, the team discusses the story with the Product Owner to clarify 'what' success looks like. These clarifications are documented as acceptance criteria, which directly inform the technical tasks the team will perform during the iteration.

Analysis of other options:

Team velocity (Option A): Velocity is a metric used to plan how many stories the team can take on in an iteration, but it does not describe the specific work needed to complete an individual story.

Related epics (Option B): Knowing the parent Epic provides context and the 'big picture,' but it does not provide the granular detail required to execute the specific tasks of a single story.

Product owner's priorities (Option C): Priorities determine the order in which work is done (sequence), but they do not define the technical or functional requirements needed to fulfill the story itself.

Per PMI standards, Acceptance Criteria are the primary source of detail in an adaptive environment that ensures the team has a shared understanding of the work requirements, allowing for accurate estimation and successful delivery.

Answer : C

According to the PMBOK Guide (6th and 7th Editions), Project Integration Management is the core responsibility of the project manager. While other knowledge areas (like Scope, Schedule, or Cost) can be managed by specialists or functional leads, Integration cannot be delegated. It is the specific function where the project manager acts as the 'integrator' of the project.

Key responsibilities within this domain include:

Unification and Consolidation: The project manager must pull together the outputs of all other Knowledge Areas (the subsidiary plans) to create a cohesive Project Management Plan.

Managing Interdependencies: Overseeing how a change in one area (e.g., a scope increase) impacts other areas (e.g., budget and schedule).

Resource and Objective Alignment: Ensuring that all project activities are aligned with the overall strategic goals and the Project Charter.

Balancing Competing Constraints: Making trade-offs among competing objectives and alternatives to ensure the project as a whole is successful.

Analysis of Distractors:

A (Requirements): This is the primary focus of Project Scope Management. While requirements are eventually integrated, clarifying them is a specialized task within the Scope domain.

B (Team Motivation): This is the primary focus of Project Resource Management. While vital, it describes the 'people' side of management rather than the 'integration' of the project's technical and administrative components.

D (Stakeholder Communication): This is the primary focus of Project Management. Like the other distractors, this is a specialized area that feeds into Integration but does not define the overarching integrative role of the project manager.

Answer : B

According to the PMBOK Guide, specifically the Develop Team process (formerly Develop Project Team), this process focuses on improving competencies, team member interaction, and the overall team environment to enhance project performance.

Team Performance Assessments: This is a primary output of the process. As the project manager implements various development strategies (such as training, team-building activities, and ground rules), they must evaluate the effectiveness of these efforts.

Evaluation Criteria: The success of the team development is measured against formal or informal assessments of the team's effectiveness. Criteria include:

Improvements in individual skills (technical or soft skills).

Improvements in team competencies (working better as a collective).

Reduced staff turnover rate.

Increased team cohesiveness and improved communication.

Impact on the Project: By assessing performance, the project manager can identify the specific training or coaching required to close gaps and ensure the project objectives are met.

Comparison with other options:

A . Change requests: While change requests can occur in many processes, they are typically a 'by-product' rather than the defining primary output of the Develop Team process.

C . Project staff assignments: This is an output of the Acquire Resources (Acquire Project Team) process. It identifies who is on the team before the development process begins.

D . Project documents updates: While project documents (like the resource calendar) may be updated, Team Performance Assessments is the unique, core functional output specifically associated with the 'Develop' phase of human resource management.

Answer : A

According to the PMBOK Guide and the Agile Practice Guide, projects characterized by high variability and uncertainty (such as research and development or complex construction with shifting requirements) require specialized approaches to remain within budget and on schedule. The most effective construction for this is the application of Lean methods.

Waste Elimination: Lean focuses on identifying and removing 'waste' (Muda) within the project lifecycle. This includes reducing waiting times, minimizing rework, and optimizing processes to ensure that every activity adds direct value to the final deliverable.

Controlling Costs: By eliminating waste and focusing on value-added activities, Lean methods significantly reduce unnecessary expenditures. In high-variability environments, where traditional 'fixed' planning often leads to expensive changes, Lean's focus on efficiency helps keep the budget under control.

Achieving Schedule: Lean techniques such as Just-in-Time (JIT) delivery and Small Batching allow the project to maintain a steady flow. In high-variability projects, breaking work into smaller, manageable increments prevents the 'bottleneck' effect, allowing the team to meet schedule milestones more reliably even when conditions change.

Value Stream Mapping: Project managers use Lean tools like value stream mapping to visualize the entire process and identify where delays occur, allowing for proactive schedule management.

Why other options are incorrect:

Option B: Collaborative teams: While collaboration is a core tenet of agile and adaptive environments, it is a behavioral attribute. It supports the project, but 'Lean methods' provide the actual structural methodology for controlling cost and schedule performance specifically.

Option C: Generalizing specialists: This refers to 'T-shaped' individuals who have one deep area of expertise and broad knowledge in others. While they improve team flexibility and resource management, they are a resource type, not a method for controlling overall project costs and schedules.

Option D: Knowledge sharing: This is a critical component of Manage Project Knowledge and organizational learning. While it helps avoid repeating past mistakes, it is not the primary mechanism used to control the mechanical constraints of cost and time in a high-variability execution environment.

Answer : D

According to the PMBOK Guide (Project Management Body of Knowledge), specifically within the Project Resource Management knowledge area and the Develop Team and Manage Team processes:

Influencing (Option D): This is a key interpersonal skill defined by PMI as the strategy of sharing power and relying on interpersonal skills to convince others to cooperate toward common goals. In many organizational structures (especially matrix organizations), project managers may have little or no direct authority over team members or stakeholders. Therefore, the ability to influence others---by building rapport, exercising ethical persuasion, and demonstrating competence---is essential to gain support and commitment to the project objectives.

Collaboration (Option A): This is a conflict resolution technique (also known as 'Problem Solve') where parties work together to find a 'win-win' solution. While it involves cooperation, it is a method of addressing disagreement rather than the broad power-sharing strategy used to motivate others toward a goal.

Negotiation (Option B): This is the process of reaching an agreement between parties with different interests. While influencing is often used during a negotiation, negotiation is typically more transactional or focused on specific terms (like resource allocation or scope) rather than the general strategy of power-sharing for common goals.

Decision Making (Option C): This refers to the ability to select a course of action from among different alternatives. While a PM must decide how to influence, the act of deciding is a cognitive process, not the interpersonal strategy of convincing others.

In the PMI framework, Influencing is considered a critical competency because it allows the Project Manager to navigate organizational politics and secure the necessary resources and buy-in without relying solely on formal 'legitimate' power.

Answer : A

According to the PMBOK Guide, the Lessons Learned Register is the primary project document used to record knowledge gained during a project or a phase. This document is created early in the project and is updated throughout the lifecycle as an output of the Manage Project Knowledge process.

The distinction between the choices depends on the timing and the specific document type as defined by PMI:

Lessons Learned Register (Choice A): This is a project document used to record challenges, risks, opportunities, or other content that can be used to improve performance in the current project or future phases. At the end of a project or phase, the information in this register is transferred to the Lessons Learned Repository.

Lessons Learned Repository (Choice D): This is part of the Organizational Process Assets (OPAs). While the repository is where the information is eventually stored for the entire organization's long-term use, the specific document that 'gathers' and captures these details during the execution and at the conclusion of a project phase is the register.

Choices B and C: These are not standard PMI terms. While 'lessons learned' may be referred to as assets or lists informally, they are not formal project management documents recognized in the PMBOK Guide.

In the Close Project or Phase process, the Lessons Learned Register is finalized and its contents are archived into the Lessons Learned Repository to support continuous improvement across the organization.