PMI Updated CAPM Exam Questions and Answers by kendall

According to the PMBOK® Guide, specifically within the Control Quality process, a Control Chart is a graphic display of process data over time and against established control limits.

Specification Limits: These are based on the requirements of the agreement (contract) or the customer ' s needs. They represent the maximum and minimum values allowed. If a product or service falls outside these limits, it is considered nonconforming (a defect).

Control Limits vs. Specification Limits:

Control Limits (Upper and Lower Control Limits - UCL/LCL) are calculated statistically (usually $\pm3$ sigma) and show the natural variation of the process. They determine if the process is " in control. "

Specification Limits (Upper and Lower Specification Limits - USL/LSL) are provided by the customer or contract. A process can be " in control " (statistically stable) but still " out of spec " if the control limits fall outside the specification limits.

Purpose: The control chart allows the project manager to identify when a process is behaving unpredictably (out of control) or when it is in danger of violating the contractual specification limits.

Comparison with other options:

B. Flowchart: This is a graphical representation of a process showing how various elements of a system relate. It is used to identify where quality problems might occur but does not track data against specification limits.

C. Checksheet: Also known as a tally sheet, this is used to organize facts in a manner that will facilitate the effective collection of useful data about a potential quality problem. It is a data collection tool, not an analytical chart for limits.

D. Pareto diagram: This is a specific type of vertical bar chart used to identify the vital few sources that are responsible for causing most of a problem ' s effects. It follows the 80/20 rule and does not incorporate upper or lower specification limits.

According to the PMBOK® Guide, specifically within the Develop Schedule process, the Critical Chain Method (CCM) is a schedule network analysis technique that modifies the project schedule to account for limited resources.

Resource Constraints: Unlike the Critical Path Method (CPM), which focuses on logical dependencies (task sequences), the Critical Chain Method accounts for both logical dependencies and resource availability. If a resource is required for two different tasks at the same time, the Critical Chain Method will adjust the schedule to resolve this conflict.

Buffers: CCM adds non-work schedule activities called buffers to manage uncertainty.

Project Buffer: Placed at the end of the critical chain to protect the target finish date.

Feeding Buffers: Placed at points where non-critical chains merge into the critical chain to protect the critical chain from slippage in the feeding tasks.

Focus on Aggregated Risk: Instead of managing the " float " of individual activities, the project manager manages the remaining buffer durations against the remaining duration of the chain of activities.

Comparison with other options:

A. Human resource planning: This is part of the Plan Resource Management process. It involves identifying and documenting project roles, responsibilities, and reporting relationships, but it is not a schedule network analysis technique that modifies the schedule itself.

B. Fast tracking: This is a schedule compression technique where activities or phases normally done in sequence are performed in parallel for at least a portion of their duration. It usually increases risk and may require more resources, but it does not inherently " modify the schedule to account for limited resources " in the way CCM does.

C. Rolling wave planning: This is an iterative planning technique where the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level. It is a form of progressive elaboration, not a resource-constrained network analysis technique.

According to the PMBOK® Guide, specifically within the Develop Team and Manage Team processes, Ground Rules are the primary tool used to set clear expectations regarding the code of conduct for project team members.

Defining Expected Behaviors: Ground rules establish acceptable behavior by the project team. They cover topics such as meeting etiquette, communication protocols, conflict resolution strategies, and general professional conduct.

Team Charter Integration: Ground rules are a key component of the Team Charter. By discussing and agreeing upon these rules early in the project, the team reduces misunderstandings and increases productivity. It allows the team to self-regulate; when a rule is broken, the team members themselves can address the behavior based on their prior agreement.

Project Manager ' s Role: While the project manager facilitates the creation of these rules, the most effective ground rules are those developed collaboratively by the team, as this increases commitment and accountability.

Analysis of other options:

Decision making (Option B): (Likely a typo for " Decision making " ). These are techniques (like voting, autocratic, or multicriteria analysis) used to reach a conclusion or select a course of action, not to govern daily behavior.

Power/influence grid (Option C): This is a tool used in Stakeholder Analysis to group stakeholders based on their level of authority (power) and their level of concern (interest) regarding project outcomes.

Stakeholder engagement assessment matrix (Option D): This is a tool used to compare the current engagement levels of stakeholders with the desired engagement levels required for project success.

Per PMI standards, implementing Ground Rules is a proactive leadership technique that helps transition a team through the " Storming " phase of the Tuckman Ladder by providing a structured framework for interaction.

According to the PMBOK® Guide (specifically the chapters regarding organizational influence and project lifecycles), the level of authority and resource availability for a project manager is dictated by the organizational structure.

The situation described—where the project manager is full-time, has full-time administrative staff, and full-time project team members—is a hallmark of a Projectized (also known as " Project-Oriented " ) organization.

In the comparison of organizational structures:

Projectized: The project manager has high to almost total authority. Resources are assigned full-time to the project, and the project manager operates with a high degree of independence.

Weak Matrix: The project manager acts more as a coordinator or expediter. Resources remain in their functional departments and are not dedicated full-time to the project.

Functional: The project manager has little to no authority. Staff are managed by functional managers, and project work is often done in addition to departmental work.

Balanced Matrix: The project manager shares authority with functional managers. While the PM is full-time, the staff and administrative support are typically not dedicated solely to one project full-time.

As per the PMI Standard for Project Management, the " Projectized " structure is the only one where the PM typically possesses a high percentage of the organization ' s resource control and a dedicated support team.