Certified Associate in Project Management CAPM (CAPM) — Questions 376–450

Option D is correct because the business case must include a cost-benefit analysis to justify the investment. Option A is a project charter element, B is a requirements artifact, C is a project management plan component.

Option D is correct. EMV = Probability * Impact = 0.8 * $50,000 = $40,000. Option A is $10,000 (0.2*50000), option B is $40,000, option C is $50,000 (full impact), option D is $80,000 (wrong multiplication).

R002 has no test case assigned, indicating a gap in traceability.

A requirement in draft status needs to be reviewed and approved by stakeholders before proceeding, so facilitating a review meeting is the appropriate action.

Pair programming (A) and test-driven development (C) are core XP practices. Retrospectives (B) and sprint review (D) are Scrum ceremonies. Product backlog grooming (E) is common in Scrum but not a defined XP practice.

The Create WBS process decomposes the project scope into manageable work packages, and its primary output is the scope baseline. The scope baseline consists of the project scope statement, the Work Breakdown Structure (WBS), and the WBS dictionary, which together define all the work required to complete the project successfully.

Carol has medium power and low interest, placing her in the 'monitor' quadrant, requiring minimal active management.

Option D is correct because when a WIP limit is exceeded, the team should swarm on the bottleneck to complete the items in that column, thereby reducing work-in-progress and restoring flow. In Kanban, exceeding a WIP limit signals a constraint that must be resolved by finishing existing work, not by adding more. This aligns with the core principle of limiting WIP to improve throughput and cycle time.

These are the five process groups in project management.

The requirements traceability matrix (RTM) is the most suitable artifact because it links each requirement to its origin, source, and corresponding deliverables throughout the project lifecycle, enabling bidirectional traceability. This allows the business analyst to capture, track, and manage changes to requirements, ensuring that all requirements are met and that no scope creep occurs. The RTM is specifically designed for this continuous tracking and management role, unlike the other artifacts which serve different purposes.

Options A, B, and D are correct. The PMBOK Guide defines five process groups: Initiating, Planning, Executing, Monitoring and Controlling, and Closing. Analyzing and Reviewing are not process groups.

The 'Communications link failure' error typically indicates a network issue between the application and database server, so network connectivity should be checked first.

A business case includes the problem statement, cost-benefit analysis, and alternatives analysis to justify the project. Risk register and stakeholder list are separate documents that inform but are not core parts of the business case.

The dependency between foundation work and framing is a mandatory dependency because it is physically required that the foundation be completed before framing can begin. In construction, this is a hard logic constraint inherent in the nature of the work, not a preference or external factor. Mandatory dependencies are often referred to as 'hard logic' and are typically based on contractual requirements or physical limitations.

The primary output of a needs assessment is the business case, which justifies the investment based on identified gaps and opportunities. Requirements documentation, stakeholder register, and project charter are produced later in the project lifecycle.

Option C is correct because developing a workaround using an alternative API or building a fallback mechanism directly reduces the probability and/or impact of the API deprecation risk. This is a classic risk mitigation strategy that proactively ensures the project can continue even if the third-party API becomes unavailable, which is a common technical risk in software projects.

Analogous (A), parametric (B), and three-point (C) are all estimating techniques. Reserve analysis (D) is used for contingency reserves, not duration estimation. Monte Carlo simulation (E) is a risk analysis technique.

A prioritized product backlog with regular refinement allows the team to adapt to changes by reprioritizing work. Fixed scope (A) and detailed upfront requirements (D) are waterfall practices. Freezing sprint backlog (B) prevents necessary changes.

In Scrum, the Development Team is self-organizing and responsible for managing its own work within the Sprint. When two members are pulled to a critical production issue, the remaining three team members have the authority to decide how to adjust the Sprint Backlog to reflect their reduced capacity. The Scrum Master should facilitate this self-management rather than imposing a solution, as option C respects the team's autonomy and the Scrum principle of self-organization.

In a predictive project, changes should be managed through the formal change control process. This ensures that the impact on scope, schedule, and cost is evaluated before taking action. Simply assigning the fix without a change request bypasses controls, removing the module changes scope without analysis, and requesting additional resources without a plan is premature.

Option C is correct because the project manager must first evaluate feasible alternatives (like a partial fix or workaround) to meet the fixed go-live date, given that the contingency reserve is exhausted and the schedule has no buffer. Escalating to the sponsor is appropriate when the issue impacts regulatory compliance and requires a decision beyond the PM's authority. This aligns with the CAPM principle of managing stakeholder expectations and seeking sponsor guidance when constraints force trade-offs.

Attractive (or 'delighter') features in the Kano model are unexpected and generate satisfaction when present, but their absence does not cause dissatisfaction.

The scope baseline is the primary output of the 'Define Scope' and 'Create WBS' processes, and it formally defines and controls what is included in the project. It consists of the project scope statement, the WBS, and the WBS dictionary, providing a comprehensive reference for scope management. By establishing the scope baseline, the project manager ensures that all required work is identified and any changes must go through formal change control.

The presence of a merge commit (a1b2c3d) with two parents indicates a merge strategy. Rebase would show a linear history, squash would show a single commit, and cherry-pick would not show a merge commit.

The project charter formally authorizes the project and the project manager. It includes the project purpose or justification (A) to establish the business need, a summary budget (B) to provide high-level financial constraints, and high-level risks (D) to identify potential uncertainties early. These are key components per the PMBOK Guide.

Option B is correct because a formal change control board (CCB) and a documented change control process provide a structured, consistent method for evaluating, approving, and implementing changes. This minimizes disruptions by ensuring that only approved, impact-assessed changes are introduced, preventing ad-hoc modifications that can destabilize the project scope, schedule, and budget.

Agile is designed for rapid iteration and adaptability to changing requirements.

Cost variance (CV) is calculated as EV minus AC. Here, EV = $45,000 and AC = $50,000, so CV = $45,000 - $50,000 = -$5,000. A negative CV indicates the project is over budget, which matches option C.

For a key stakeholder (high power, high interest), proactive management is required. Since they are disengaged, the best first step is to schedule a one-on-one meeting to understand their concerns and re-engage them. Option B is too passive (waiting), option C may escalate unnecessarily, option D is too indirect.

Option B is correct because the business analyst (BA) is responsible for ensuring that each requirement directly supports the stated business objectives and strategic goals. This alignment is a core function of requirements management within the BABOK framework, as it prevents scope creep and ensures that delivered features provide measurable business value.

The business case is missing a comparison of alternatives considered. A business case must justify why the selected approach is the best option, which requires evaluating at least one alternative (e.g., build vs. buy, different technical solutions). Without this, stakeholders cannot assess whether the recommended solution is optimal or cost-effective.

Define Scope is the process of developing a detailed project scope statement that describes the project and product boundaries.

In predictive (waterfall) project management, any change that impacts scope, budget, or schedule must follow the formal integrated change control process. The project manager's first step after evaluating the impact is to submit a change request to the change control board (CCB) for approval or rejection. This ensures that all changes are documented, assessed for risks, and aligned with the project baseline before implementation.

Kanban focuses on visualizing workflow, limiting work in progress (WIP), and managing flow. It does not prescribe fixed-length iterations (that's Scrum) nor require a dedicated team (teams can be shared).

Option D is correct because updating the communications management plan to address cultural differences and preferred communication styles is the most proactive step. Replacing team members is drastic, and adding meetings may not help.

The Delphi Technique involves anonymous voting rounds to achieve consensus. MoSCoW is a prioritization but not anonymous, Multi-criteria Decision Analysis does not involve voting, and Voting (Roman Vote) is open.

The needs assessment process results in a business case that defines the business need and recommended solution. Project Charter authorizes the project, Requirements Documentation details requirements, and Stakeholder Register lists stakeholders.

The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. This includes clearly expressing Product Backlog items and ordering them to best achieve goals and missions, which is prioritizing the Product Backlog. Managing the Product Backlog, which encompasses ensuring its visibility, transparency, and understanding, is also a core responsibility of the Product Owner as defined in the Scrum Guide.

Option C is correct because evaluating the impact on time, cost, and other constraints is the first step in integrated change control. Direct approval or rejection would be premature without impact analysis.

Option C is correct because the business analyst's primary role is to facilitate stakeholder collaboration and resolve conflicts through structured discussion, ensuring that requirements are accurate and agreed upon before development begins. This aligns with the BABOK guide's emphasis on using techniques like workshops or brainstorming to achieve consensus, which prevents costly rework later.

The correct first step is to submit the change request to the change control board (CCB) because, in formal project management, any change that impacts scope, schedule, or cost must go through the integrated change control process. Even though the change is critical for regulatory compliance, the project manager cannot unilaterally approve or reject it; the CCB has the authority to evaluate the impact analysis and make the final decision.

Surveys are a common requirements elicitation technique because they allow the business analyst to collect information from a large number of stakeholders efficiently, especially when stakeholders are geographically dispersed. They are structured and can include both closed-ended and open-ended questions to gather quantitative and qualitative data.

The ACL permits TCP traffic from the 192.168.1.0/24 network to host 10.1.1.1 on port 80 (www). All other traffic is denied.

Option A is correct because SS+2d means Start-to-Start with a 2-day lag, so the successor task starts 2 days after the predecessor starts. Option B has Finish-to-Finish, Option C has Finish-to-Start, Option D has Start-to-Start but without a lag.

The policy denies ec2:TerminateInstances when the source IP is NOT in the 10.0.0.0/8 range. Thus, it denies termination from outside that network.

The stakeholder management plan documents stakeholders' identified needs, expectations, and influence levels, which directly inform their risk tolerance thresholds. The project manager references this plan to understand how different stakeholders perceive risk and what level of risk they are willing to accept, enabling tailored risk responses in the risk management plan.

A CPI of 0.8 means the project is earning only $0.80 for every $1.00 spent, indicating it is over budget. An SPI of 1.1 means the project is earning $1.10 for every $1.00 of planned work, indicating it is ahead of schedule. Therefore, the project is over budget but ahead of schedule, making option C correct.

Mandatory dependencies are legally or contractually required or inherent in the nature of the work. For example, in a construction project, you must complete the foundation before erecting the walls. These are often referred to as 'hard logic' and cannot be changed without altering the project scope or approach.

The project is financially viable because the NPV is positive ($50,000), indicating that the present value of expected cash inflows exceeds the present value of cash outflows. Additionally, the IRR of 12% exceeds the company's required rate of return (10%), meaning the project's expected return is greater than the cost of capital. Both metrics independently confirm financial feasibility.

Pair programming is a core XP practice where two developers work together at one workstation. Sprint Review (A) is Scrum, Backlog Grooming (C) is common in Scrum, and Velocity Tracking (D) is a measurement used in various methodologies.

Breaking down user stories into smaller pieces improves estimation accuracy and reduces the risk of large unfinished items. Reducing sprint length (A) may increase overhead, increasing team size (B) can cause communication overhead, and adding buffer (D) does not address estimation quality.

Correct are A (Current state analysis), C (Business goals), and D (Problem statement). B is a solution, not needs assessment. E is a requirement detail.