PMI Updated CAPM Exam Questions and Answers by nell

According to the PMBOK® Guide (6th Edition), the Estimate Costs process is the process of developing an approximation of the monetary resources needed to complete project work. To create an accurate estimate, the project manager must pull information from various foundational sources.

The inputs for the Estimate Costs process include:

Project Management Plan: Specifically the Cost Management Plan, Quality Management Plan, and Scope Baseline (which includes the Project Scope Statement, WBS, and WBS Dictionary).

Project Documents: This is a broad category including the Lessons Learned Register, Project Schedule, Resource Requirements, and Risk Register.

Enterprise Environmental Factors (EEFs): These include market conditions, published commercial information (like price lists), and exchange rates.

Organizational Process Assets (OPAs): These include cost estimating policies, cost estimating templates, and historical information from previous similar projects.

Analysis of Distractors:

A (Work performance data): This is an input for Monitoring and Controlling processes (like Control Costs). It represents raw observations and measurements identified during activities. It is not used to estimate costs, but rather to compare actual costs against the estimates.

C (Cost baseline / Benefits management plan): The Cost Baseline is an output of the Determine Budget process. It cannot be an input to Estimate Costs because estimating must happen before the baseline is established. The Benefits Management Plan is generally an input to the business side (Initiating/Planning) rather than activity-level cost estimation.

D (Basis of estimates): This is an output of the Estimate Costs process. It provides the supporting detail for how the cost estimates were derived (e.g., how risks were considered, what range of precision was used).

According to the PMBOK® Guide (specifically the 4th and 5th editions, which use these specific process names), Define Activities and Estimate Activity Resources are core processes within the Project Time Management knowledge area (renamed to Project Schedule Management in later editions).

Define Activities: This process involves identifying and documenting the specific actions to be performed to produce the project deliverables. It takes the work packages from the WBS and breaks them down into schedule activities that provide a basis for estimating, scheduling, executing, monitoring, and controlling the project work.

Estimate Activity Resources: This process involves estimating the types and quantities of material, human resources, equipment, or supplies required to perform each activity. This is a critical step because the availability and type of resources directly impact the duration of the activities.

Knowledge Area Context: In the standard process mapping, Project Time/Schedule Management includes:

Plan Schedule Management

Define Activities

Sequence Activities

Estimate Activity Resources

Estimate Activity Durations

Develop Schedule

Control Schedule

Comparison with Other Domains:

Project Cost Management (B): Focuses on Estimate Costs, Determine Budget, and Control Costs.

Project Scope Management (C): Focuses on Collect Requirements, Define Scope, and Create WBS.

Project Human Resource Management (D): While this area (now Resource Management) deals with managing the team, the initial estimation of which resources are needed for specific tasks is traditionally housed within the Time/Schedule management processes to build the project timeline.

According to the PMBOK® Guide, specifically within the Control Quality process, the Pareto chart is a specific type of vertical bar chart used to identify the primary sources that are responsible for the majority of issues or defects.

The 80/20 Principle: The Pareto chart is based on Pareto’s Law (the 80/20 rule), which posits that a relatively small number of causes (20%) typically result in the majority (80%) of the problems or defects.

Functionality: In a Pareto chart, categories are ordered by the frequency of occurrence. This helps the project team focus their corrective actions on the " vital few " problems that are having the greatest impact, rather than the " useful many " minor issues.

Visual Representation: It usually displays both bars (representing individual frequencies) and a line graph (representing the cumulative percentage of the total).

Analysis of Other Options:

A. Ishikawa diagram: Also known as a Fishbone or Cause-and-Effect diagram. It is used to identify the root causes of a problem by mapping out various contributing factors, but it does not rank them by frequency or illustrate the 80/20 rule.

B. Control chart: Used to determine whether or not a process is stable or has predictable performance. It uses " Control Limits " to identify " Special Cause " variation.

C. Run chart: A line graph that shows data points plotted in the order in which they occur. It is used to identify trends and shifts in a process over time but does not categorize or rank causes of defects.

According to the PMBOK® Guide, the Ishikawa diagram (also known as a cause-and-effect, fishbone, or root-cause diagram) is a key tool used within the Quality Management knowledge area. Specifically, it is most frequently utilized during the Control Quality process.

Control Quality: This process involves monitoring and recording the results of executing quality activities to assess performance and ensure the project outputs are complete, correct, and meet customer expectations. When a defect or a performance issue is identified, the Ishikawa diagram is used to break down the potential causes of that specific problem into categories (such as Manpower, Methods, Machinery, Materials, Media, and Management) to find the root cause.

Root Cause Analysis: The diagram helps the project team look beyond the symptoms of a problem to identify the underlying reason why the problem occurred, which is a primary objective of the Control Quality process to prevent future occurrences.

Analysis of other options:

A. Plan Quality Management: While you might define which tools you will use during this planning phase, the actual act of using the diagram to analyze a specific problem happens during execution and monitoring.

C. Risk Management: Although root cause analysis is used in Identify Risks, the Ishikawa diagram is most formally associated with the quality tools and techniques defined by PMI.

D. Plan Scope Management: This process focuses on defining how the scope will be defined, validated, and controlled; it does not typically involve cause-and-effect modeling for defects.

In summary, per PMI standards, the Ishikawa diagram is a diagnostic tool used in Control Quality to link the observed effect (the problem) to its potential causes.