PMI Updated CAPM Exam Questions and Answers by lea

According to the PMBOK® Guide and the Standard for Project Management, the Business Case is a critical input to the Develop Project Charter process. It provides the necessary information from a business standpoint to determine whether or not the project is worth the required investment.

As per PMI standards, the Business Case is typically created as a result of one or more of the following:

Market demand (e.g., a car company authorizing a project to build more fuel-efficient cars).

Organizational need (e.g., a training company authorizing a project to create a new curriculum).

Customer request (e.g., an electric utility authorizing a project to build a new substation for a new industrial park).

Legal requirement (e.g., a hospital authorizing a project to comply with new health data privacy laws).

The Business Case, along with the Benefits Management Plan, makes up the Business Documents category of inputs. These documents are usually developed outside the project but are used as a basis for project authorization.

The other options are incorrect based on their placement in the project lifecycle:

Activity list: This is an output of the Define Activities process, which occurs much later during the Planning Phase.

Project management plan: This is the primary output of the Develop Project Management Plan process. It cannot be an input to the Charter because the Charter must exist before the Project Management Plan can be developed.

Cost forecast: This is an output of the Control Costs process. It is a monitoring and controlling tool used to predict future cost performance based on actual work, not an initiating document.

As per the PMI Lexicon of Project Management Terms, the Business Case describes the objectives and reasons for initiating the project and helps the sponsor and the project manager align the project ' s success criteria with the organization ' s strategic goals.

According to the PMBOK® Guide, specifically within the Manage Team process, conflict is inevitable in a project environment. While Collaborate/Problem Solve is generally considered the most effective technique as it leads to a win-win situation, it is not always possible or appropriate.

Avoid/Withdraw: This technique involves retreating from an actual or potential conflict situation or postponing the issue to be better prepared or to be resolved by others. It is the specific technique a project manager uses when a collaborative approach is not possible, such as when the issue is trivial, the project manager has no power to resolve it, or when others can resolve the conflict more effectively.

Conflict Management Context: The PMBOK® Guide identifies five general techniques for resolving conflict:

Withdraw/Avoid: Retreating or postponing.

Smooth/Accommodate: Emphasizing areas of agreement rather than differences.

Compromise/Reconcile: Searching for solutions that bring some degree of satisfaction to all parties.

Force/Direct: Pushing one ' s viewpoint at the expense of others (win-lose).

Collaborate/Problem Solve: Incorporating multiple viewpoints and insights from differing perspectives (win-win).

Comparison with other options:

A. Coaching: This is a leadership and team development skill used to help team members develop their competencies. It is not a formal conflict resolution technique listed in the PMBOK® Guide.

C. Consensus: Consensus is a group decision-making technique where everyone agrees to support the outcome. While it is related to collaboration, it is a goal of the decision-making process rather than a fallback technique used when collaboration is impossible.

D. Influencing: This is an interpersonal skill used to share power and rely on interpersonal skills to get others to cooperate towards common goals. While useful in preventing conflict, it is not categorized as a primary conflict resolution method in the same way Avoidance is.

According to the PMBOK® Guide, the Request for Proposal (RFP) is a specific type of Bid Document used in the Conduct Procurements process.

Bid Documents: These are the formal documents used to solicit proposals from prospective sellers. The term " bid documents " is an umbrella term that includes the Request for Information (RFI), Request for Quotation (RFQ), and Request for Proposal (RFP).

Purpose of an RFP: An RFP is used when there is a problem in the project and the solution is not easy to determine. It allows the buyer to describe the problem and ask the sellers to propose a solution, a technical approach, and a price.

Solicitation Process: The project manager uses the RFP to communicate the project ' s needs to the vendors (sellers) so they can provide a structured response that the project team can then evaluate against the source selection criteria.

Why other options are incorrect:

Option B: Statement of Work (SOW): The Procurement SOW is an input to the bid documents. It describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products or services. The RFP contains the SOW, but they are not the same thing.

Option C: Source selection criteria: These are the standards developed by the buyer to rate or score seller proposals. They are used to evaluate the responses received from the RFP, but the RFP itself is the solicitation document, not the criteria.

Option D: Independent cost estimate: Also known as a " should-cost " estimate, this is a tool used by the buyer to provide a benchmark for evaluating the reasonableness of the prices submitted by the sellers. It is an internal document, not the solicitation document sent to vendors.

According to the PMBOK® Guide, specifically within the Collect Requirements process, the Delphi Technique is a specific group creativity technique (and a form of expert judgment) used to reach a consensus among a group of experts.

Process and Methodology: In the Delphi technique, a facilitator uses a questionnaire to solicit ideas about the project requirements from a selected group of experts. The responses are summarized and then recirculated to the experts for further comment.

Anonymity: A key characteristic of this technique is that the experts participate anonymously. This prevents any single participant from unduly influencing the others (the " bandwagon effect " ) and encourages honest, unbiased feedback.

Iterative Rounds: The process typically involves several rounds of questionnaires and feedback until a consensus is reached. This is highly effective for reducing bias in the data and ensuring that the requirements are not skewed by a dominant personality in a face-to-face setting.

Analysis of other choices:

Choice B (Nominal group technique): This technique enhances brainstorming with a voting process used to rank the most useful ideas for further brainstorming or for prioritization. It usually involves face-to-face interaction or direct collaboration.

Choice C (Affinity diagram): This is a tool used to allow a large number of ideas to be classified into groups for review and analysis. It is a categorization tool, not a feedback/consensus-gathering method.

Choice D (Brainstorming): This is a general technique used to generate and collect multiple ideas related to project and product requirements. It lacks the formal, iterative, and anonymous structure of the Delphi technique.