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.

Option A is correct because 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.

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.

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.

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

Option C is correct because 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.

Schedule a face-to-face meeting with the stakeholder to discuss their concerns and the project's needs

For a stakeholder with high power and high interest, proactive engagement is key. A face-to-face meeting (C) is the most effective first step to directly address disengagement, understand their concerns, and re-establish communication. Option A escalates prematurely without attempting direct engagement first, Option B ignores the risk and the stakeholder's input, and Option D is too indirect and may further alienate the stakeholder.

Analyze the schedule logic, correct any errors in dependencies or duration estimates, and recalculate the schedule.

Negative total float on a non-critical path typically indicates an error in the schedule logic, such as incorrect dependencies, misestimated durations, or a logical loop. Since the project is still in the planning phase and no baseline is set, the correct action is to analyze the schedule, identify and correct the errors in dependencies or duration estimates, and then recalculate the schedule. This resolves the negative float without unnecessary compression. Option A is incorrect because applying schedule compression (crashing or fast-tracking) to a non-critical path is inappropriate; compression should be reserved for critical paths when schedule acceleration is needed. Option C is incorrect because ignoring the negative float could propagate errors. Option D is incorrect because adding the non-critical path to the critical path artificially changes the schedule logic without addressing the underlying error.

Scalability to fit the project size and complexity

For a small project with a limited budget, the most important characteristic of a business analysis framework is scalability, because it allows the framework to be tailored to the project's size and complexity without incurring unnecessary overhead or costs. A framework that is too rigid or comprehensive would waste resources on activities that do not add value for a small project, while a scalable approach ensures that only essential analysis tasks are performed. This directly aligns with the principle of 'just enough' business analysis, which is critical when budget constraints are tight.

Facilitate a prioritization session with all stakeholders to discuss trade-offs.

The BA should first facilitate a prioritization session with all stakeholders to discuss trade-offs because this aligns with the business analysis framework's emphasis on collaborative decision-making when scope conflicts arise. By engaging stakeholders, the BA can evaluate the feature's value against budget and timeline constraints, ensuring informed trade-offs rather than unilateral rejection or escalation. This approach maintains stakeholder alignment and avoids premature scope changes without consensus.

Facilitate stakeholder negotiation to limit mid-sprint changes and reinforce the importance of the sprint goal.

Option D is correct because the Scrum Master's primary role is to protect the Scrum framework and facilitate collaboration. By negotiating with stakeholders and reinforcing the sprint goal's importance, the Scrum Master addresses the root cause—uncontrolled scope changes—without violating Scrum principles. This approach preserves the team's focus and velocity, preventing overcommitment and demotivation.

Collaborate with the Product Owner to remove or defer some Product Backlog items.

In Scrum, the development team is self-managing and responsible for committing to a Sprint Goal. If they realize they have taken on too much work, the correct action is to collaborate with the Product Owner to remove or defer Product Backlog items, as this preserves the Sprint's timebox and focus on the highest-value work. This aligns with the Scrum principle of transparency and inspection, allowing the team to adjust the Sprint Backlog without changing the Sprint duration.

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.

-$5,000

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.

Establish a change control board and process.

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.

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.

16.67 days

The PERT three-point estimate formula is (Optimistic + 4×Most Likely + Pessimistic) / 6. Plugging in the values: (10 + 4×15 + 30) / 6 = (10 + 60 + 30) / 6 = 100 / 6 = 16.67 days. This weighted average gives more influence to the most likely estimate, reflecting a beta distribution.

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.

Revise the interview questions to be more open-ended and focus on business outcomes.

Option B is correct because the BA's questions are too technical, causing stakeholders to focus on implementation details rather than their actual needs. By revising questions to be open-ended and focused on business outcomes, the BA shifts the conversation from 'how the system should work' to 'what business problem needs to be solved,' which is the core of effective requirements elicitation. This approach aligns with the BABOK's principle of understanding stakeholder needs before defining technical solutions.

The activity durations for WP-101 were estimated too aggressively.

Negative float indicates that there is insufficient schedule flexibility to meet the project deadline. The most common cause is overly optimistic activity duration estimates, which compress the schedule and eliminate float. Errors in the network diagram or critical path calculation could also cause negative float, but these are less likely if the schedule logic is sound. Resource leveling typically affects resource allocation, not float directly.

Coach the Product Owner on how to split user stories to minimize dependencies.

The Scrum Master's primary responsibility is to coach the Product Owner and the team on Scrum practices. In this scenario, the root cause is the Product Owner's inability to decompose user stories into small, independent items, which creates dependencies. By coaching the Product Owner on effective story splitting techniques (e.g., using vertical slicing, splitting by workflow steps, or by acceptance criteria), the Scrum Master directly addresses the source of the problem, enabling the team to deliver value incrementally without cross-story delays.

Analyze the impact of the change on the project constraints

Option A is correct because the change management plan requires the project manager to first analyze the impact of the proposed change on scope, schedule, and cost before any further action. This analysis provides the necessary data to determine whether the change should be submitted to the CCB for approval. Skipping this step would violate the defined change control process.

Agile framework

The Agile framework is the correct choice because it emphasizes iterative development, frequent stakeholder collaboration, and adaptive planning, which are ideal for a project with distributed stakeholders across time zones. Agile practices such as daily stand-ups, sprint reviews, and backlog refinement allow for efficient requirements elicitation and ensure all stakeholders can provide input asynchronously or during synchronized ceremonies, accommodating varying availability.

Decomposition

Decomposition is the correct technique because it is the process of subdividing project deliverables into smaller, more manageable components until the work package level is reached. This directly addresses the team's struggle with defining the lowest-level work packages, ensuring the WBS is complete and properly decomposed by breaking down deliverables iteratively.