Certified Associate in Project Management CAPM (CAPM) — Questions 1–75

The critical path method calculates the longest sequence of dependent activities, determining the project's shortest possible duration and identifying float. It is a core schedule development technique in predictive projects, driving duration forecasting and schedule compression decisions.

The Ishikawa diagram maps effect back to categorised causes — people, process, tools, environment — so the team can trace defect sources before they occur. For a predictive project's quality management plan, this satisfies the requirement to identify root causes proactively, rather than detecting defects later through inspection or statistical sampling.

Monitoring and Controlling covers tracking, reviewing and regulating project progress and performance, including performing Integrated Change Control. Document changes and approvals flow through that process group, ensuring only approved revisions are baselined, which satisfies the requirement to control changes to project documents.

The sponsor cannot unilaterally override an approved strategic objective, so the analyst documents the sustainability conflict and escalates it to the steering committee, which owns such cross-cutting decisions. This preserves the analyst's objectivity and gives governance authority the evidence to resolve the inconsistency.

The Sprint Retrospective is the only Scrum event whose explicit purpose is inspecting how the team worked and adapting its process, satisfying the continuous-improvement constraint. Unlike the Daily Scrum, which inspects progress toward the Sprint Goal, it focuses on people, interactions, tools and Definition of Done, producing actionable improvements for the next Sprint.

Any change affecting cost or schedule must pass through integrated change control. Submitting the request to the CCB lets that body evaluate the 15% cost increase and three-week delay against the sponsor's budget concerns, then approve, reject or defer it formally.

Tracing requirements to business objectives ensures that every requirement contributes to the strategic goals and the business case. This alignment helps prioritize requirements and prevents scope creep by identifying requirements that do not add value. In this scenario, the BA can use tracing to confirm that CRM requirements support the organization's goals, such as improving customer retention or increasing sales.

Splitting an oversized story into smaller sprint-sized items lets the team deliver value within one Sprint while preserving the Product Owner's intent. This collaborative refinement satisfies the Sprint timebox constraint that the original story violates.

This is principle #3.

Work performance information is a Control Quality output because the process compares deliverables against quality standards and feeds results into the Monitor and Control Project Work cycle. It satisfies the stem's requirement by capturing conformance and nonconformance data, such as validated defect repairs, which supports quality control decisions and reporting.

Project constraints — such as scope, schedule, cost, quality, risk and resource limitations — are documented in the scope statement to bound what the project will deliver. Including them satisfies the stem's requirement for a typical scope statement element in a predictive project.

The Definition of Done is a shared commitment created by the Scrum Team, not imposed by one person. A workshop lets Developers, the Product Owner, and the Scrum Master agree on quality criteria that every Increment must meet. This creates transparency and a common standard, replacing individual interpretations and enabling consistent delivery of potentially releasable work.

The board reveals that work accumulates in 'In Progress' while 'Testing' is empty, indicating a bottleneck or handoff problem. Kanban emphasizes making work visible and managing flow. Analyzing the workflow to find why items are not moving to testing—such as missing test environments, unclear exit criteria, or insufficient testers—and then adjusting policies or capacity addresses the root cause and restores flow.

Analogous estimating derives cost figures from the actual costs of comparable past projects, typically using top-down judgement. It suits early planning when detailed data is scarce, matching the stem's reference to historical data from similar projects.

Scrum protects the Sprint from scope changes that would endanger the Sprint Goal. New requests are captured in the Product Backlog, where the Product Owner can order them against other items. The Developers then select work during the next Sprint Planning based on value and capacity, preserving the current Sprint's focus and the agreed Sprint Goal.

The project manager should first assess how the proposed change affects scope, schedule, cost, quality, and risk. This evaluation provides necessary information for the change control process. Without understanding the impact, the project manager cannot make informed decisions or recommendations to the change control board. This step is part of performing integrated change control, ensuring changes are managed proactively.

An SPI of 0.85 indicates that the project is only achieving 85% of the planned schedule performance, meaning it is behind schedule. A CPI of 1.10 indicates that the project is getting $1.10 of work for every $1 spent, so it is under budget. This combination is correctly interpreted as behind schedule and under budget.

The Sprint Retrospective is a formal Scrum event held at the end of each Sprint, giving the team a dedicated opportunity to inspect its process and identify improvements, satisfying the framework's requirement for a recurring inspect-and-adapt ceremony.

The critical path is the longest path through the project network diagram, and it determines the shortest possible time to complete the project. Any delay in a critical path activity will delay the project. It is calculated using the critical path method, which considers activity durations and dependencies. This is a fundamental concept in schedule management.

Projects are temporary endeavours with defined start and end dates, producing a unique deliverable, whereas operations are ongoing and repetitive, sustaining the business. This directly satisfies the stem's request to distinguish the two: temporality and uniqueness separate projects from continuous operational work.

The project charter is the document that formally authorises the project and grants the project manager authority to apply organisational resources to project activities. It satisfies the stem's authorisation constraint, distinguishing it from plans, which describe how work will be performed.

A framework supplies repeatable phases, tasks and deliverables, so analysis is performed consistently rather than ad hoc. This structured approach directly addresses the organisation's lack of an existing framework, giving the project manager a defined, governable method for eliciting, documenting and managing requirements across the lifecycle.

This is one of the four values.

The forward pass is a schedule network analysis technique that calculates the early start and early finish dates for each activity by moving forward through the network from the start. It uses duration estimates and dependencies to determine the earliest possible times. This directly matches the project manager's need to determine early start and early finish dates for the renovation activities.

Documenting the impact in the change request captures the schedule delay, cost and benefit implications before any decision. This satisfies the stem's constraint that the change is feasible but delays the schedule, giving the change control board accurate information to approve, defer or reject.

CPI of 0.8 means every unit of currency returns only 0.8 of planned value, so costs exceed the budget baseline. SPI of 1.2 means earned value outpaces planned value, so work is progressing faster than the schedule baseline. Both indices are measured against the same earned value baseline.

Prototyping builds a partial working model so stakeholders react to something concrete rather than abstract descriptions, surfacing requirements they cannot articulate verbally. This iterative feedback loop is a recognised elicitation technique in business analysis frameworks such as BABOK.

Variance analysis compares planned vs actual schedule.

The Scrum Master should help the team inspect and adapt the Definition of Done if it does not ensure value. A shared understanding of quality and value is essential. Facilitating a conversation between the Product Owner and Developers can reveal gaps and lead to an improved Definition of Done that better supports delivering valuable increments.

The project charter is the document issued by the sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It is created during the initiation phase and is essential before any project work begins. It also links the project to the strategic objectives of the organization.

In Scrum, the Sprint Backlog is owned by the Developers and can be updated as more is learned. Since the team believes the Sprint Goal remains achievable, adding the new feature is acceptable. The Sprint Goal provides focus but does not freeze the scope; the team self-manages its work to maximize value.

The critical path method calculates the longest path through the network and the earliest and latest start and finish dates for activities. Running the forward pass with no resource constraints yields the shortest possible total duration if all activities start as early as possible. This directly answers the sponsor's question about total duration under unconstrained conditions.

In a predictive waterfall project, phases run sequentially with no overlapping or fast-tracking, so a two-week design delay pushes every dependent downstream phase by the same amount. The critical path lengthens by exactly two weeks, assuming no float or compression is applied later.

Sequential dependency accurately describes this chain, where each task's start is gated by its predecessor's finish (A→B→C→D). The stem's constraint is a strict finish-to-start cascade with no branching or overlap, which is precisely what a sequential relationship defines.

The project charter formally authorizes the project's existence and grants the project manager the authority to apply organizational resources to project activities. It is issued by the sponsor or initiating entity and serves as the foundation for detailed planning. Without a charter, the project lacks official sanction and the project manager may lack the power to allocate resources effectively.

A business case documents the risk assessment, identifying uncertainties and their potential effect on benefits, costs and schedule. This satisfies the stem's requirement for a typical element, since decision-makers need this analysis to judge whether the expected value justifies proceeding with the proposed project.

Fair rotation supports team collaboration.

Transitioning the completed product to the group that will operate and maintain it is a key closing activity. It ensures the deliverable is not orphaned after the project team disbands and that support responsibilities are formally handed over. This transition, sometimes called turnover, includes communicating relevant documentation and knowledge. It aligns with the sponsor's request because closure is not complete until the product is accepted and successfully transitioned.

Creating a high-level plan early and elaborating progressively satisfies the organisation's upfront planning mandate without abandoning agile delivery. This is rolling-wave planning: the plan exists from the outset, but detail is deferred until the last responsible moment, so Scrum's empirical, iterative cycles continue while the governance requirement for an initial documented plan is met.

Prioritising individuals and interactions over processes and tools is a core Agile Manifesto value shared across Scrum, XP and Kanban. It satisfies the question's requirement for a principle common to multiple methodologies, not one specific framework.

Crashing shortens the critical path by adding resources, such as extra staff or overtime, to critical activities. It trades increased cost for reduced duration, directly addressing the behind-schedule constraint where activities sit on the critical path.

Qualitative risk analysis ranks identified risks by probability and impact, so it updates the risk register with each risk's urgency or priority rating. This satisfies the stem's requirement for a typical output of that process, since the register is the repository where prioritised risk information is recorded and maintained.

Identifying a required vendor for a critical component occurs while developing the project management plan and its subsidiary plans, such as procurement and resource management. This work sits squarely within the Planning process group, satisfying the stem's "during project planning" constraint rather than Executing, Monitoring and Controlling, or Initiating.

The power/interest grid plots stakeholders by authority over the project and their level of concern, producing tailored engagement strategies for each quadrant. It directly satisfies the stem's requirement to categorise stakeholders by influence and interest.

The PERT weighted average is (optimistic + 4 × most likely + pessimistic) ÷ 6, giving (4 + 24 + 12) ÷ 6 = 40 ÷ 6 ≈ 6.67 days. Weighting the most likely estimate fourfold accounts for expected variability in the activity's duration.

Scrum suits high uncertainty through short sprints, empirical inspection and adaptation, and a groomed backlog that absorbs changing requirements. This satisfies the uncertainty constraint by delivering increments frequently, letting the team learn and re-plan rather than committing to a fixed upfront scope.

Continuous integration shortens integration delays, a common hidden contributor to cycle time. This satisfies the stable-demand constraint: rather than adding capacity, the team removes the queueing and rework caused by deferred integration, so items flow through the board faster.

The Sprint Retrospective is the last event of the Sprint and occurs after the Sprint Review and before the next Sprint Planning. Holding it at this time allows the team to inspect the past Sprint and identify improvements before planning the next one. This sequencing is defined in Scrum and supports continuous improvement.

In a matrix organisation, functional managers retain line authority over the people in their departments, so they typically control who is assigned to project work and how that work is prioritised against departmental duties. The project manager coordinates the work but usually negotiates rather than directs resource allocation.

Capping WIP forces the team to finish work before starting more, which directly curbs multitasking and its context-switching overhead. This improves focus and shortens cycle time, satisfying Kanban's flow-efficiency constraint rather than merely tracking throughput.

Time is one of the three classic project constraints, bounding the schedule within which deliverables must be completed. Alongside cost and scope, it forms the triple constraint that project managers continuously balance, since compressing the timeline directly affects both the resources required and the scope achievable.

The project life cycle spans initiation to closure, and its defining characteristics derive from projects being temporary, with definite start and end, and unique, producing a distinct deliverable. This constraint distinguishes project work from ongoing operational activities that repeat indefinitely.

In a projectized structure, team members report directly to the project manager, who controls resources and priorities. This grants the project manager a high level of authority, distinguishing it from functional or matrix structures where power is shared with functional managers.

EMV multiplies probability by monetary impact, so 0.3 × $50,000 yields $15,000. This quantifies the risk's expected cost exposure against project objectives, giving the project manager a comparable figure for contingency reserves and risk prioritisation within the risk register.

Because functional managers control resource allocation and workload in a functional organization, the project manager must negotiate with the appropriate functional manager to obtain the extra hours. This respects the reporting structure and uses the influence and coordination skills expected of a project manager with limited authority. Securing the manager's agreement also makes the commitment more durable than an informal request to the designer.

The schedule baseline is an approved, time-phased version of the schedule, forming part of the project management plan's subsidiary plans and baselines. It satisfies the stem's requirement by being an output of schedule development that is formally incorporated into the plan, alongside scope, cost and performance measurement baselines.

Kanban boards render every work item and its stage on a shared visual surface, exposing bottlenecks, work-in-progress limits and queue build-up that hidden backlogs conceal. This directly satisfies the stem's requirement for a key benefit: making workflow state and flow constraints immediately visible to the whole team.

A hybrid approach keeps the signed-off high-level scope under change control while iterative cycles with rolling wave planning absorb evolving regulatory detail. This satisfies the stem's constraint of balancing flexibility with control given limited agile experience, avoiding full waterfall rigidity or unmanaged scope creep.

A requirements traceability matrix links each requirement to its originating need and to downstream design, development and test artifacts. When REQ-007 fails, the RTM reveals the associated design components and test cases, enabling targeted impact analysis and correction.

The stakeholder register is an input to Plan Quality Management as it identifies stakeholders who have a specific interest in or influence over quality. For the ERP project, key stakeholders such as the finance department or IT security may have quality requirements. Understanding their needs helps the project manager define quality standards and compliance approaches, so the stakeholder register is a correct input.

A needs assessment precedes all other business analysis work, establishing the current-state problems, gaps and desired outcomes before requirements are elicited. Conducting it first satisfies the stem's constraint that the initial activity must define the business need driving the new system.

A data flow diagram (DFD) visually represents the flow of data within a system, showing external entities, processes, data stores, and data flows. It focuses on data movement and transformation, not on internal processing logic, making it ideal for this scenario.

SAFe's programme increment planning synchronises multiple Scrum teams, exposing and resolving cross-team dependencies during a fixed planning cadence. This directly addresses the stem's inter-team dependency delays, providing the coordination layer that standalone Scrum lacks at scale.

The project charter is the document that formally authorises the project's existence and grants the project manager authority to commit organisational resources. Business cases and plans lack that sanctioning power, so the charter uniquely satisfies the stem's requirement for formal authorisation and resource authority.

Identifying stakeholders during initiation captures who is affected by or can influence the project, along with their expectations, interests and power. This understanding shapes engagement planning and communication, satisfying the purpose of early identification before requirements and scope are finalised.

Agile (Scrum) suits volatile requirements through iterative sprints, delivering working increments every two to four weeks so feedback reshapes the backlog continuously. This directly satisfies the stem's highly uncertain environment and frequently evolving requirements, which predictive frameworks cannot accommodate without costly change control.

The on-site customer practice in XP requires a real customer to be available full-time to the team. This person defines user stories, prioritizes them, and answers questions immediately. This continuous involvement ensures the team builds what the customer needs and receives rapid feedback, which is a core XP value.

In a matrix structure, staff report to both a functional manager and a project manager, so securing personnel requires negotiation rather than direct assignment. This dual-reporting authority split is the defining constraint that shapes resource allocation and creates competing priorities for the project manager.

Brainstorming is designed to produce a high volume of creative ideas in a short time while suspending judgment. In this workshop, it lets sales, marketing, and support contributors propose CRM features freely. The BA captures all ideas without debate, then later groups and evaluates them. This matches the goal of rapid idea generation and reduced criticism during divergent thinking.

The organisational policy makes the signed charter a mandatory precondition, so the team's authorisation to begin is gated on both signatures. Until the sponsor and functional manager sign, no project work can legitimately commence, regardless of the team's readiness or availability.

Oversized user stories commonly cause carry-over because they hide complexity and resist completion within a Sprint. Helping the team slice stories smaller improves flow and forecasting before other interventions such as process changes are considered.

Analysing cost, schedule and scope impact and presenting options at the prioritisation meeting satisfies the sponsor's requirement that requirements be finalised before design, while giving stakeholders evidence to decide the late requirement's fate. Proceeding directly to design would breach the waterfall phase gate.

When the current cost performance is expected to continue at the same rate, the estimate at completion is calculated as budget at completion divided by the cost performance index. This formula assumes that the efficiency or inefficiency observed to date will persist for the remainder of the project. It is the most common EAC formula used in earned value management for this scenario.

Following integrated change control assesses the requested feature's impact across cost, schedule, scope and quality before any rework begins, satisfying the need to minimise disruption to completed deliverables and their inter-dependencies. It routes the request through the change control board for documented approval or rejection, preventing unapproved scope creep during execution.