CAPM Reviews Questions

According to the PMBOK® Guide, the Develop Project Management Plan process utilizes a specific set of Tools and Techniques to integrate all subsidiary plans and baselines into a comprehensive document.

Expert Judgment: This is the most critical tool for this process. It involves consulting with individuals or groups with specialized knowledge or training in project strategy, tailoring the project management process to meet the project needs, and determining the technical and management details to be included in the plan.

Data Gathering: This involves techniques such as brainstorming, checklists, focus groups, and interviews. These tools are used to collect information from stakeholders and team members regarding how the project should be managed, executed, and controlled.

Integrated Approach: While meetings and interpersonal skills (like facilitation) are also used in this process, the standard PMI documentation emphasizes Expert Judgment and Data Gathering as the foundational methodologies for synthesizing diverse requirements into a single, cohesive management plan.

Why other options are incorrect:

Option A: Meetings and data analysis: While meetings are used, " data analysis " is more commonly associated with the Monitor and Control processes (like analyzing performance data) rather than the initial creation of the management plan itself.

Option C: Interpersonal skills and change control: Interpersonal and team skills (facilitation, conflict management) are indeed used, but Change Control is a separate process (Perform Integrated Change Control) that occurs after the project management plan has been baselined.

Option D: Data analysis and expert judgment: Again, " data analysis " (such as alternatives analysis) can be used, but per the official PMI process mapping for Develop Project Management Plan, Data Gathering is a more primary and frequently cited tool for this specific stage than data analysis.

According to the PMBOK® Guide, specifically within the Plan Communications Management process, the project manager identifies the information needs of the stakeholders and defines a communication approach. The specific tools and techniques used to develop this plan are:

Communication Requirements Analysis: This technique determines the specific information needs of project stakeholders. This includes considering the number of potential communication channels using the formula $n(n-1)/2$.

Communication Technology: This refers to the specific tools, systems, or methods used to transfer information among stakeholders (e.g., conversations, written documents, online databases, or websites).

Communication Models: These are descriptions, metaphors, or graphical representations that show how communication processes are performed (e.g., the basic sender-receiver model involving encoding, transmitting, decoding, and noise).

Communication Methods: These are the systematic procedures used to share information. They are categorized into Interactive (multidirectional), Push (sent to specific recipients), and Pull (used for large volumes of information where recipients access content at their own discretion).

Comparison with Other Options:

B. methods, stakeholder register, communication technology, and communication models: The Stakeholder Register is an Input to the process, not a tool or technique.

C. requirements, communication technology, communication requirements analysis, and communication methods: " Communication requirements " is the result or an input factor, but " Communication Requirements Analysis " is the actual technique.

D. management plan, communication technology, communication models, and communication requirements analysis: The Communication Management Plan is the Output of this process, not a tool or technique used to create it.

According to the PMBOK® Guide, the Conduct Procurements process is the process of obtaining seller responses, selecting a seller, and awarding a contract. This process happens during the Executing Process Group.

Tools and Techniques of Conduct Procurements (Choice A): This list correctly identifies the formal tools and techniques used to select a vendor:

Expert Judgment: Relying on individuals with specialized knowledge in legal, financial, or technical aspects of procurement.

Bidder Conferences: Meetings between the buyer and all prospective sellers prior to the submittal of a bid or proposal to ensure all prospective sellers have a clear and common understanding of the procurement.

Proposal Evaluation: A formal process for reviewing and scoring proposals based on the weight of various selection criteria.

Advertising: Used to expand the list of potential sellers by placing notices in newspapers or online registries.

Independent Estimates: Often prepared by the buyer or an outside professional to serve as a " benchmark " to validate the reasonableness of the bids submitted by sellers.

Procurement Negotiations: The final discussions to clarify requirements and other terms to reach a mutual agreement.

Choice B: " Budgeting " is a part of the Determine Budget process, and " Seller ' s Proposal " is an Input to the Conduct Procurements process, not a tool or technique.

Choice C: " Make-or-buy decisions " is an Output of the Plan Procurement Management process. By the time you are conducting procurements, the decision to " buy " has already been made.

Choice D: " Agreements " and " Selected Seller " are the primary Outputs of the Conduct Procurements process, not the tools used to get there.

The goal of these tools is to ensure that the selection process is fair, competitive, and results in a contract that provides the best value to the organization while meeting project requirements.

According to the PMBOK® Guide, the Project Management Plan is the primary document that defines how the project is executed, monitored, controlled, and closed. It is composed of several subsidiary plans and baselines.

Subsidiary Management Plans: These include plans for Scope, Schedule, Cost, Quality, Resources, Communications, Risk, Procurement, and Stakeholder Engagement. Option A correctly identifies the Scope Management Plan and the Risk Management Plan.

Baselines: There are three primary baselines: Scope Baseline, Schedule Baseline, and Cost Baseline. Option A correctly includes the Scope Baseline.

Additional Components: The plan also includes the Configuration Management Plan, which describes how information about the items of the project (and which items) will be recorded and updated so that the product, service, or result of the project remains consistent.

Why other options are incorrect:

Option B: The Issue Log and Risk Register are Project Documents, not components of the Project Management Plan itself. The Project Schedule Network Diagram is also a project document.

Option C: While the Schedule Baseline is part of the plan, the Milestone List and Assumption Log are classified as Project Documents.

Option D: Cost Estimates, Duration Estimates, and Resource Calendars are all considered Project Documents. They support the plan but are not part of the formal Project Management Plan " package " as defined by PMI standards.