CAPM Flashcards — Free Certified Associate in Project Management CAPM Study Cards

Coach the Product Owner on the Sprint Backlog rule and the impact of changes.

The Scrum Master's primary responsibility is to ensure Scrum is understood and enacted. The Product Owner is violating the Sprint Backlog rule, which states that once a Sprint starts, the Product Owner cannot change the Sprint Backlog items; only the team can modify the Sprint Backlog to meet the Sprint Goal. By coaching the Product Owner on this rule and the impact of changes (e.g., rework, loss of focus, and potential Sprint Goal failure), the Scrum Master addresses the root cause without disrupting the team's workflow.

Limit the WIP at each stage, especially testing.

In Kanban, limiting Work in Progress (WIP) at each stage is a core practice to expose bottlenecks and improve flow. By capping the number of items allowed in testing, the team prevents work from piling up, forcing them to finish existing tasks before pulling new ones. This directly addresses the frequent bottlenecks by making the constraint visible and actionable, enabling the team to focus on completing testing rather than starting more work.

Rotate the time of the Daily Scrum so that no one is always inconvenienced.

Rotating the Daily Scrum time shares the inconvenience of time zone differences equitably across the distributed team, preserving the event's purpose of daily synchronization and inspection. The Scrum Guide requires the Daily Scrum to be held at the same time and place each day, but for distributed teams, rotating the time is an acceptable adaptation that maintains the event's time-boxed, collaborative nature without breaking the inspect-and-adapt cycle.

The project is financially viable.

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.

Submit the change request to the change control board (CCB).

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.

6.67 days

The PERT three-point estimate formula is (Optimistic + 4×Most Likely + Pessimistic) / 6. Plugging in the values: (4 + 4×6 + 12) / 6 = (4 + 24 + 12) / 6 = 40 / 6 = 6.67 days. This weighted average gives more influence to the most likely estimate, providing a realistic expected duration.

Implement critical chain project management.

Critical chain project management (CCPM) is specifically designed to protect the critical path from disruptions like unplanned work by inserting buffers (e.g., feeding buffers, project buffer) and enforcing a 'relay race' work ethic. This technique reduces multitasking and focuses the team on completing tasks in priority order, directly addressing the root cause of delays from unplanned work.

Perform a quantitative risk analysis to determine appropriate contingency reserves.

The project manager should perform a quantitative risk analysis to determine the appropriate contingency reserve based on the project's specific risk exposure, rather than relying on an arbitrary 10% figure. This aligns with the PMBOK Guide's guidance that contingency reserves should be derived from risk analysis, not sponsor preference, especially given the high degree of uncertainty.

Analyze the impact on the project constraints and submit a change request.

The correct first step is to analyze the impact on the project constraints (scope, time, cost, quality) and submit a formal change request. This follows the Integrated Change Control process, ensuring the sponsor and change control board (CCB) evaluate the trade-offs before any work begins. In software development, adding a feature without analysis risks scope creep and uncontrolled budget or schedule deviations.

Critical path method (CPM)

The Critical Path Method (CPM) is the correct tool because it calculates the longest path through the project network diagram by analyzing activity durations and dependencies, identifying which activities have zero float and thus determine the project's minimum completion time. The question specifically asks for determining the critical path, which is the core output of CPM, not just visualizing or estimating durations.

Submit a change request to the change control board

In predictive (waterfall) project management, any change that impacts scope, budget, or schedule must follow a formal change control process. The project manager first assesses the impact, then submits a change request to the Change Control Board (CCB) for approval before any action is taken. Implementing the change or updating baselines without CCB approval violates the control scope process defined in the PMBOK Guide.

Three-point estimating

Three-point estimating (C) is correct because it explicitly accounts for uncertainty by using optimistic, most likely, and pessimistic estimates. The new technology introduces unknown risks, making the triangular or PERT distribution ideal for modeling the potential delay range.

Review the enterprise's business analysis framework and adjust the requirements process to comply with it.

The project manager must first ensure the requirements gathering process aligns with the enterprise's business analysis framework. This alignment is a foundational step to reduce scope changes and rework, as the framework defines standard practices, templates, and governance for requirements management. Without compliance, any change control or documentation updates will be ineffective because the underlying process itself is non-conforming.

Context diagram

The context diagram is the most appropriate artifact for documenting the high-level boundaries and capabilities of a solution during the planning phase. It visually represents the system as a single process, its external entities (actors), and the data flows between them, clearly defining what is inside and outside the solution scope. This aligns with the business analyst's need to capture the solution's scope boundaries without detailing internal processes.

Conduct a feasibility study to evaluate trade-offs and present options.

Conducting a feasibility study allows the business analyst to objectively evaluate trade-offs between Requirement X (regulatory compliance) and Requirement Y (user efficiency) within the tight timeline. This approach provides data-driven options (e.g., scope adjustments, resource reallocation) to the project sponsor, enabling an informed decision without prematurely sacrificing either requirement or escalating unnecessarily. It aligns with the BABOK® Guide's principle of collaborative decision-making through analysis rather than assumption.

Creating a stakeholder map and validating with experts

Stakeholder mapping, when validated with experts, systematically identifies all affected parties by visually representing relationships, influence, and impact. This technique leverages expert judgment to cross-check the map against organizational knowledge, ensuring no stakeholder group is overlooked. It is more comprehensive than ad-hoc methods because it follows a structured framework (e.g., PMI's stakeholder identification process) and incorporates validation to fill gaps.