Download Full Version CAPM PMI Exam

In the PMBOK® Guide, a " traditional " project—often referred to as a Predictive or Waterfall lifecycle—is characterized by a high degree of certainty and a sequential flow of phases. These projects rely heavily on the ability to define the scope clearly at the beginning and follow a disciplined plan.

Why Choice B is correct (Few expected simple scope change requests): In a linear approach, the goal is to " lock down " the scope during the planning phase. Because the requirements are well-understood and the environment is stable, there should be very few changes once execution begins. Frequent changes are usually a sign that an adaptive (Agile) approach would have been more appropriate.

Why Choice C is correct (Routine and repetitive activities): Traditional delivery excels in projects where the work is well-known and follows a predictable pattern (e.g., construction or standard manufacturing). Because the activities are routine, the project manager can estimate time and cost with high accuracy based on historical data.

Why Choice E is correct (Use of established templates): Linear projects rely on high-level standardization. To ensure consistency and governance across the phases (Initiating, Planning, Executing, Monitoring/Controlling, and Closing), the project manager utilizes Organizational Process Assets (OPAs), such as standardized templates for project charters, risk registers, and status reports.

Analysis of other options:

A (Many expected simple scope change requests): This describes an Adaptive (Agile) environment. In Agile, change is welcomed throughout the process because the scope is expected to evolve as the customer sees incremental deliveries.

D (Collocated project teams): While collocation is a " best practice " for team communication, it is not a defining characteristic of the delivery approach itself. Both Waterfall and Agile teams can be collocated or virtual; however, Agile frameworks (like Scrum) emphasize collocation more strongly than traditional linear models do.

Key Concept: The Project Management Institute (PMI) teaches that a Linear Delivery Approach is most successful when the technical risk is low and the requirements are stable. By leveraging established templates (Choice E) and focusing on routine work (Choice C) with minimal changes (Choice B), the project manager can maximize efficiency and ensure the project is delivered on time and within the original budget.

According to the PMBOK® Guide, the relationship between the five Process Groups and the ten Knowledge Areas (noting that earlier versions focused on nine) is often visualized through a mapping matrix.

The Planning Process Group: This is the only process group that contains at least one process from every single Knowledge Area. Because planning is comprehensive, the project manager must develop subsidiary plans for Scope, Schedule, Cost, Quality, Human Resources, Communications, Risk, Procurement, and Integration.

Knowledge Area Integration:

Integration: Develop Project Management Plan

Scope: Plan Scope Management, Collect Requirements, Define Scope, Create WBS

Schedule: Plan Schedule Management, Define Activities, Sequence Activities, Estimate Activity Resources, Estimate Activity Durations, Develop Schedule

Cost: Plan Cost Management, Estimate Costs, Determine Budget

Quality: Plan Quality Management

Human Resources: Plan Human Resource Management

Communications: Plan Communications Management

Risk: Plan Risk Management, Identify Risks, Perform Qualitative Risk Analysis, Perform Quantitative Risk Analysis, Plan Risk Responses

Procurement: Plan Procurement Management

Analysis of Other Options:

A. Executing: Does not include processes from every knowledge area (e.g., it lacks specific processes for Scope or Schedule execution, which are managed via the Direct and Manage Project Work process in Integration).

B. Monitoring and Controlling: While very broad, it typically does not have a unique process for Human Resources (which is managed/developed in Executing).

D. Initiating: This group is very limited, containing only two processes: Develop Project Charter (Integration) and Identify Stakeholders (Stakeholder Management).

According to the PMBOK® Guide (Project Management Body of Knowledge), specifically within the Project Integration Management knowledge area and the Perform Integrated Change Control process:

Integrated Change Control (Option D): This scenario describes " scope creep " or an unauthorized change. The Perform Integrated Change Control process is designed to prevent exactly this type of issue. By requiring that all changes—regardless of the source—be formally documented, evaluated for their impact on all project constraints (scope, schedule, cost, quality, etc.), and approved by a Change Control Board (CCB) or the Project Manager, the team would have discovered the adverse effect on the other deliverable before the change was implemented.

Quality Assurance (Option A): This process (now called Manage Quality) focuses on the processes used to create deliverables to ensure they meet quality standards. While it helps ensure the result is correct, it is not the primary mechanism for managing the intake and approval of scope changes.

Stakeholder Management Plan (Option B): This plan identifies how to effectively engage stakeholders. While it might define who can request changes, the actual mechanism for processing those requests and analyzing their cross-functional impact is the Change Control System.

Project Team Building (Option C): This is part of the Develop Team process. While a cohesive team might communicate better, team building itself is not a procedural control for managing technical changes to project deliverables.

In the PMI framework, Integrated Change Control is critical because no change exists in a vacuum. A change to one deliverable often ripples through the project, affecting others. By following a formal process, the Project Manager ensures that the " big picture " is maintained and that the project baseline remains protected from uncoordinated modifications.

According to the PMBOK® Guide, the Plan Risk Management process defines how to conduct risk management activities for a project. The output of this process is the Risk Management Plan, which contains several specific components.

Tracking: This specific component of the Risk Management Plan documents how risk activities will be recorded for the benefit of the current project and how risk management processes will be audited. It ensures that the history of risk identified, analyzed, and responded to is captured for future reference and organizational process assets.

Audit and Documentation: Tracking defines the frequency and format for documenting risk results. It also specifies how the performance of risk management will be measured to see if the processes are effective.

Comparison with other options:

B. Scoping: While " scope " is a fundamental project constraint, it is not a standard sub-section of the Risk Management Plan used to describe the recording or auditing of risk activities.

C. Timing: This component defines when and how often the risk management processes will be performed throughout the project life cycle, and establishes risk management activities to be included in the project schedule.

D. Defining: While the plan " defines " many things (such as Risk Categories via the Risk Breakdown Structure or Probability and Impact scales), " defining " is not the formal name of the component responsible for the recording and auditing of risk activities; that is specifically " Tracking. "