PMI Updated CAPM Exam Questions and Answers by amayah

According to the PMBOK® Guide and the Agile Practice Guide, the choice of delivery method (development life cycle) depends heavily on the nature of the project deliverables and the stability of the requirements.

Linear (Predictive) Project Management: This method is also known as Waterfall. It is used when the scope is well-defined and the product is a physical deliverable with low levels of change expected. Building a physical structure, such as a detachable classroom, follows a clear, sequential path (design, foundation, assembly, finishing). In construction, changes are costly, so a predictive approach is standard to minimize risk.

Artifacts - Project Schedule and WBS:

Work Breakdown Structure (WBS): This is the foundational artifact for linear projects. It is a deliverable-oriented hierarchical decomposition of the work. For a classroom, the WBS would break the project down into physical components (roof, walls, electrical, etc.).

Project Schedule: In linear management, a detailed schedule (often a Gantt chart) is used to track the sequential activities and dependencies required to reach the completion date.

Why not Adaptive?: Adaptive (Agile) methods are best suited for software or intangible products where requirements evolve. Building a physical classroom requires " Big Up-Front Planning " because you cannot easily change the dimensions of a wall once it has been manufactured and delivered.

Analysis of other options:

Option A: This combines a linear method with a Project Backlog. A backlog is an Agile artifact; linear projects use a WBS and a Scope Baseline instead.

Option B: Adaptive management is typically not the primary choice for standard physical construction. Furthermore, while Adaptive projects can use a WBS, it is much more characteristic of Linear management.

Option D: This is a purely Agile (Adaptive) configuration. It is unsuitable for a construction project with a fixed, physical scope like a detachable classroom.

Per PMI standards, physical engineering and construction projects are typically managed using a Linear (Predictive) delivery method, utilizing a WBS to define scope and a Project Schedule to manage the execution of that scope.

According to the PMBOK® Guide, specifically within the Identify Stakeholders process, several classification models are used to prioritize stakeholders to ensure the efficient use of effort to communicate and manage their expectations.

The Power/Interest Grid: This specific model groups stakeholders based on their level of authority (Power) and their level of concern regarding project outcomes (Interest).

Power: The level of influence a stakeholder has over the project ' s execution or results.

Interest: The level of concern or " buy-in " the stakeholder has regarding the project ' s success or failure.

Strategic Management: This grid helps the project manager determine the appropriate engagement strategy for each group:

High Power/High Interest: Manage Closely.

High Power/Low Interest: Keep Satisfied.

Low Power/High Interest: Keep Informed.

Low Power/Low Interest: Monitor (Minimum Effort).

Comparison with other options:

A. Influence/impact grid: This model groups stakeholders based on their active involvement (influence) and their ability to effect changes to the project ' s planning or execution (impact).

B. Power/influence grid: This model groups stakeholders based on their level of authority (power) and their active involvement (influence).

D. Salience model: This is a more complex model that describes classes of stakeholders based on three variables: their power (level of authority), urgency (need for immediate attention), and legitimacy (their involvement is appropriate). It is typically represented by a Venn diagram rather than a grid.

According to the PMBOK® Guide, Project Integration Management includes the processes and activities to identify, define, combine, unify, and coordinate the various processes and project management activities within the Project Management Process Groups.

There are seven processes within this knowledge area, and Monitor and Control Project Work is one of them. Its primary function is to track, review, and report the overall progress to meet the performance objectives defined in the project management plan. It is a high-level integration process that looks across all other knowledge areas to ensure the project is on track.

Analysis of other options:

Control Scope (Option B): This process belongs to the Project Scope Management knowledge area. It focuses specifically on monitoring the status of the project and product scope and managing changes to the scope baseline.

Control Schedule (Option C): This process is part of Project Schedule Management. Its focus is strictly on monitoring the status of project activities to update project progress and manage changes to the schedule baseline.

Develop Team (Option D): This process belongs to Project Resource Management. It involves improving competencies, team member interaction, and the overall team environment to enhance project performance.

Per PMI standards, Integration Management is the unique responsibility of the project manager and cannot be delegated or departmentalized, as it provides the cohesive " glue " that links the entire project together.

In accordance with the PMBOK® Guide (Project Stakeholder Management), the Identify Stakeholders process is the process of identifying the people, groups, or organizations that could impact or be impacted by a decision, activity, or outcome of the project.

Because this process often begins as soon as the project is conceived (and is part of the Initiating Process Group), it relies on high-level documents to identify who has a " stake " in the project.

Procurement Documents as an Input: If a project is the result of a procurement activity or involves external vendors, the procurement documents (such as contracts, statements of work, or bid documents) are a primary source for identifying stakeholders. These documents list the parties involved, such as suppliers, contractors, and legal entities, who are key stakeholders from the outset.

Other Key Inputs: These include the Project Charter, Business Documents (Business Case and Benefits Management Plan), and Project Management Plan components (specifically the Communications Management Plan and Stakeholder Engagement Plan during iterative updates).

Analysis of Distractors:

A. The project management plan: While certain components of the plan (like the Communications Management Plan) become inputs in later iterations of identifying stakeholders, Procurement Documents are a more fundamental input for the initial identification of external parties.

B. The stakeholder register: This is the primary output of the Identify Stakeholders process. It is the document created to record the identification, assessment, and classification of project stakeholders.

D. Stakeholder analysis: This is a tool and technique used within the Identify Stakeholders process to systematically gather and analyze quantitative and qualitative information to determine whose interests should be taken into account throughout the project.