Certified Associate in Project Management CAPM (CAPM) — Questions 226–300

Decision Analysis compares alternatives by weighing their advantages and disadvantages against defined criteria, producing a reasoned recommendation. This satisfies the stem's requirement because listing pros and cons of each interface design option is the defining activity of that technique.

BCR measures return per unit invested, so Proposal B's 1.5 delivers greater benefit per pound than A's 1.2, directly satisfying the stated goal of maximising return on investment under limited funds. The longer four-year payback is secondary to that constraint.

A milestone represents a significant point or event, carrying no effort or duration, so it is modelled as a zero-duration task. This distinguishes it from activities, which consume time and resources, and satisfies the definition of a schedule checkpoint.

The Sprint Retrospective is the event where the team inspects how the last Sprint went with regard to individuals, interactions, processes, tools, and their Definition of Done. It is the only Scrum event specifically designed for the team to identify and address process improvements. Focusing here lets the team own follow-up actions on recurring concerns and adapt its way of working before the next Sprint begins.

Velocity is a planning constraint, not a target to exceed. The team and Product Owner renegotiate scope, removing lower-priority Product Backlog items so the Sprint Backlog fits historical capacity, preserving the Sprint Goal and sustainable pace.

Raising a request for the missing test case closes the traceability gap identified during verification, ensuring the requirement gains coverage. This is the immediate corrective step; escalating or altering the requirement comes only after the coverage shortfall is formally addressed.

The critical path method (CPM) is a schedule network analysis technique used to determine the total duration of a project by identifying the longest path of dependent activities. It calculates early start, early finish, late start, and late finish dates, and identifies the critical path, which determines the shortest possible project duration. In this scenario, the project manager needs to analyze activity sequences and dependencies to find the total duration, making CPM the appropriate technique.

Deliverables and artifacts specify what the business analysis effort will produce, such as models, specifications and matrices, giving the plan its scope. Listing them satisfies the stem's requirement for a typical business analysis plan component by defining tangible outputs.

Self-organising teams make decisions locally without waiting for managerial approval, so choices are reached faster. This satisfies the stem by naming a genuine benefit: authority to decide sits with those closest to the work, removing escalation delays and accelerating commitment to the chosen course.

The risk management plan is the sole output of Plan Risk Management, documenting methodology, roles, budget, timing and risk categories. It directly guides all subsequent risk processes, satisfying the stem's requirement for this process's key deliverable.

The schedule baseline is an approved version of the schedule model, forming part of the project management plan's baselines along with scope and cost. It provides the fixed reference against which schedule performance is measured and variances tracked.

The project manager should first document the change request and then submit it to the change control board (CCB) for evaluation. The CCB reviews the impact on scope, schedule, cost, and other constraints and decides whether to approve, reject, or defer the change. This ensures that changes are managed systematically.

The Product Owner owns the Product Backlog and prioritises items to maximise the value the Development Team delivers each Sprint. This accountability, rather than task assignment or process facilitation, is the role's defining purpose within Scrum.

Entity-relationship diagrams model logical data structures by depicting entities, their attributes and the cardinality relationships between them, directly satisfying the requirement to show how customer entities relate. Unlike physical schemas or class diagrams, ERDs are technology-agnostic and capture exactly the logical data requirements the BA must document.

A RACI matrix maps each task to who is Responsible, Accountable, Consulted and Informed, directly resolving the ambiguity the team is spending time clarifying. It assigns explicit ownership per deliverable, which is the artefact's core purpose.

A configuration management system is a subset of the project management information system that includes tools and processes to manage and control changes to project documents and deliverables. It provides version control, change tracking, and access to the latest documents. In this scenario, it ensures distributed team members access current documents and that changes are tracked, meeting the project manager's needs.

The project charter is produced during Initiating, the process group that authorises the project and formally names the project manager. It precedes Planning, where the charter's high-level scope is elaborated into baselines and subsidiary plans.

The critical path method is a schedule network analysis technique used to determine the early start and early finish dates, as well as late start and late finish dates, for all activities. It calculates the longest path through the network and identifies the critical path. This technique directly provides the early start and early finish dates required in the scenario.

Surveys let stakeholders in different time zones respond asynchronously, removing the need for simultaneous availability. This directly satisfies the conflicting-schedule constraint, whereas interviews, workshops and focus groups demand real-time participation. Surveys also scale to dispersed groups, gathering structured input efficiently when synchronous elicitation is impractical.

The work package is the lowest WBS level, where deliverables are decomposed enough to assign, estimate cost and duration, and schedule. It satisfies the stem's estimating and scheduling basis because effort and resources can be quantified per package.

Facilitating a stakeholder meeting exposes the conflicts openly, letting the group weigh trade-offs and agree priorities rather than forcing every requirement in. This resolves the conflict while preserving sponsor and stakeholder buy-in, which unilateral decisions would undermine.

The project scope statement describes the project scope, major deliverables, assumptions, and constraints. It provides the baseline for evaluating changes. In this scenario, the project manager should consult the project scope statement first to understand what is included and excluded, and to assess the impact of the proposed new feature on the project constraints.

Crashing shortens the critical path by adding resources, directly targeting the schedule constraint the stem identifies. Because only critical path activities govern total project duration, compressing them yields immediate schedule reduction, though it typically increases cost and risk. This satisfies the stem's requirement for a valid compression technique applicable to critical path activities.

A parking lot is a facilitation tool that visibly records off-topic but potentially important issues on a separate list, allowing the group to acknowledge them without derailing the current discussion. It respects stakeholder concerns while keeping the session aligned to the elicitation objectives, and the captured items can be addressed later.

The plan integrates subsidiary plans specifying how work is performed and how performance is tracked and controlled. This execution, monitoring and control definition is a core benefit, giving the project manager an approved, documented approach that satisfies the stem's requirement.

PDM establishes logical relationships between activities using nodes and precedence links such as finish-to-start, start-to-start, finish-to-finish and start-to-finish. It directly documents dependencies, satisfying the requirement to identify and record logical relationships among activities during schedule creation.

Time and cost limitations are classic project constraints. The six-month deadline and $200,000 budget restrict the team's options and require careful planning to ensure the project stays within these boundaries. Recognizing them as constraints helps the project manager prioritize and make trade-offs, such as adjusting scope if necessary, to meet these fixed limits.

MoSCoW's Should-have category covers requirements that are important and expected but not vital for the first release. This matches the stem exactly: the feature matters yet can be deferred without breaking the initial delivery, unlike Must-have items.

A context diagram places the system at the centre and depicts only its boundary plus the external entities (people, organisations, other systems) that exchange inputs and outputs with it. It deliberately omits internal processes and data stores, so it satisfies the scope-modelling constraint by showing what lies inside versus outside the system.

Defining business needs comes first in needs assessment, establishing the problem or opportunity and desired outcomes before any solution options are evaluated. Subsequent activities such as gap analysis and recommending solutions depend on this initial articulation of what the business requires.

Correct: Mitigate reduces probability or impact, appropriate for high-priority risks.

A requirements traceability matrix (RTM) is a grid that links requirements to their sources, such as business goals, stakeholder needs, and other requirements. It helps ensure that each requirement adds value and aligns with strategic objectives. In this scenario, the BA can use an RTM to demonstrate how the online banking feature's requirements support customer retention and call center reduction. This provides clear traceability from requirements to business goals.

The stakeholder engagement plan is a direct output of Plan Stakeholder Engagement, documenting strategies for involving stakeholders based on their needs, interests and influence. It satisfies the stem's requirement by providing the formal, written approach that guides how the project team will communicate and engage throughout the project lifecycle.

Scrum allows the scope of a Sprint to be clarified and renegotiated between the Product Owner and the developers as more is learned, provided the Sprint Goal is not endangered. The developers own the Sprint Backlog and can adjust it. This response keeps the goal intact while responding to new value, which is exactly the flexibility Scrum intends.

Fifteen minutes is the fixed timebox for the Daily Scrum, regardless of team size, so it directly resolves the stem's overrun constraint. The event inspects progress toward the Sprint Goal and adapts the Sprint Backlog, with discussion deferred to follow-up conversations rather than extending the meeting.

The first Kanban practice is to visualize the workflow by mapping the actual steps work takes, from request to delivery. This value stream view exposes handoffs, queues, and delays. Without an accurate map of the real process, later practices like limiting work in progress or measuring flow cannot be applied meaningfully, because the team would be optimizing a fictional workflow.

Self-organisation develops through practise, not instruction. Prompting the team to reach decisions collaboratively, while the Scrum Master removes impediments rather than directing work, shifts ownership to the team and builds the capability to act without waiting for orders.

Activity attributes are a documented output of Define Activities, recording details such as activity identifiers, codes, dependencies and resource requirements. They extend the activity list and feed subsequent schedule development processes, satisfying the stem's requirement for a genuine Define Activities output.

A Requirements Traceability Matrix links each requirement backwards to its source and forwards to the test case verifying it, providing bidirectional coverage. This satisfies the stem's mapping constraint precisely, unlike a requirements document or scope statement that lacks that paired linkage.

Nominal group technique structures group input by having participants silently generate ideas, then share them one at a time, and finally vote or rank them. This prevents dominant personalities from controlling the discussion and ensures quieter members contribute. In this scenario, it directly addresses the imbalance in participation and helps the BA gather balanced input on the contentious process change.

Control Costs is the Monitoring and Controlling process that tracks actual spend against the cost baseline, analyses variances and approves corrective action. It directly addresses the stem's constraint of actual cost consistently exceeding planned cost.

Kanban improves flow by making work and its constraints visible, and explicit WIP limits are the core mechanism for exposing bottlenecks. Limiting the Code Review column forces the team to stop starting new work there and instead swarm to finish reviews, revealing whether reviewers are the constraint. Making aging items visible adds the data needed to inspect and adapt the policy later.

The resource management plan is a component of the project management plan that describes how project resources will be acquired, developed, managed, and released. It includes roles and responsibilities, reporting relationships, and resource management processes. This document directly addresses the scenario's description.

The requirements traceability matrix maps each requirement to related artefacts — design documents, test cases, deliverables — in a grid, making dependencies and coverage visible. This satisfies the stem's demand for visual representation of relationships between requirements and other project artefacts, which a simple list cannot show.

T2's error log shows its predecessor finishing after T2's scheduled start, violating finish-to-start logic. Unlike T3, which has no predecessor constraint, T2 depends on T1's completion, so the schedule conflict confirms the dependency issue. This satisfies the stem's requirement to identify the task with a dependency problem.

Benchmarking compares an organisation's processes and performance metrics against a leading competitor's, revealing gaps and improvement opportunities. It directly satisfies the stem's constraint of comparing the sales order process with a competitor rather than analysing internally.

Prototyping helps refine requirements through iterative feedback.

Mid-sprint scope changes break the sprint goal and cause the 40% incompletion. Facilitating stakeholder negotiation protects the sprint backlog, letting the team deliver its committed increment and restoring predictable velocity, directly addressing the overcommitment caused by the Product Owner accepting urgent requests under pressure.

Continuous integration in XP means integrating and testing code many times a day, typically with every commit. This practice reduces integration problems and provides rapid feedback. Nightly builds are not frequent enough to catch issues early, which is a core XP value.

A stable velocity of 30 story points means 50 is unachievable without sacrificing quality or predictability. Coaching the Product Owner to reduce scope or extend the deadline respects the team's empirical capacity rather than imposing an arbitrary target.

Bottom-up estimating aggregates individual work-package costs, giving granular detail that analogous estimating lacks. This directly addresses the sponsor's accuracy concern by reducing reliance on historical similarity, satisfying the stem's requirement to improve estimate precision. It is the most accurate technique, though costlier in time.

A compliance-focused workshop brings together legal and finance experts who understand the regulatory landscape. This collaborative approach ensures that all relevant regulations are identified and documented early. It also creates a shared understanding and buy-in, which is critical for traceability. By involving these stakeholders from the start, the BA can establish a requirements traceability matrix that links each regulatory requirement to its source, design, and test cases, ensuring compliance throughout the lifecycle.

Historical velocity gives the team an empirical basis for forecasting capacity, directly addressing the overcommitment pattern. Coaching them to select only what past Sprints prove deliverable satisfies the stem's constraint of consistent failure to complete committed items, without the Scrum Master imposing the commitment.

Start-Stop-Continue provides a balanced framework that encourages the team to identify what to start doing, stop doing, and continue doing. This structure helps the team generate actionable improvements and prevents the meeting from becoming purely negative. It is a common agile retrospective technique.

The Sprint Review is meant to be a collaborative working session, not a demo. The Scrum Master should coach participants to inspect the Increment, elicit stakeholder feedback, and adapt the Product Backlog together. This shifts the event from a one-way presentation to a genuine feedback loop, restoring its value and aligning future work with stakeholder needs.

A facilitated workshop surfaces conflicting views simultaneously, letting the BA challenge inconsistencies and hidden agendas openly. This satisfies the sponsor's demand for a comprehensive, accurate requirement set within tight time and budget, since group elicitation resolves contradictions faster than sequential interviews.

MoSCoW analysis classifies requirements as Must, Should, Could or Won't have, forcing stakeholders to weigh value against implementation complexity. This satisfies the stem's prioritisation constraint by producing a ranked, agreed scope rather than an unranked list.

Scope changes affecting budget and schedule must pass through integrated change control. Submitting a change request to the change control board first ensures the request is formally evaluated, approved, or rejected before any baselines are modified, preserving the project's approved scope, cost, and schedule.

Brainstorming is a group creativity technique that encourages participants to generate a large volume of ideas without immediate judgement or criticism. It satisfies the workshop's constraint of generating creative ideas by deferring evaluation, allowing diverse contributions before the group filters and prioritises them.

Total float is the schedule buffer a non-critical activity can consume before it delays the project finish. Five days of slip fits within that float, so the end date is unaffected and the critical path is unchanged.

Facilitated workshops bring cross-functional stakeholders together in a structured session to define requirements collaboratively. In this scenario, the BA can guide physicians, nurses, and IT staff to discuss and resolve conflicting opinions, ensuring all perspectives are heard. This technique is specifically designed to build consensus and produce documented requirements, making it ideal for the conflicting stakeholder views described.

The scope management plan describes how completed deliverables will be formally accepted, often through a verification process. This ensures that deliverables meet requirements before acceptance and helps prevent disputes. It is a key element because it defines the validation and control mechanisms for scope.

Decomposition breaks the project scope into progressively smaller, manageable work packages, ensuring every deliverable is captured at the lowest level. This directly satisfies the stem's requirement that all deliverables be identified, since the WBS is built by subdividing scope until each component is defined and verifiable.

Focus groups bring together a small group of stakeholders to discuss specific topics, allowing the BA to explore diverse opinions and build a shared understanding. For a large, diverse group, multiple focus groups can be conducted to represent different departments. They provide richer interaction than surveys and help uncover requirements that might not emerge in individual interviews. This makes focus groups suitable for eliciting requirements from varied stakeholders in the ERP project.

The project manager should first communicate directly with the team member to identify the reasons for the delays. This could be due to lack of resources, unclear expectations, personal issues, or skill gaps. Addressing the root cause is essential for a sustainable solution and aligns with effective team management and conflict resolution.

Stakeholder analysis is a key business analysis activity.

Document analysis systematically reviews existing artefacts — project documentation, process flows and system manuals — to elicit requirements and understand the current environment. It satisfies the scenario's constraint by gathering baseline information without directly involving stakeholders, making it the appropriate technique for reviewing existing materials.

The project manager should first review the contract terms to understand the implications of the delay, including any penalties or clauses. Then, assess the impact on schedule and costs. This is part of the Control Procurements process, where the project manager manages procurement relationships and monitors contract performance. Understanding the contractual obligations is crucial before deciding on corrective actions.

Prioritising items is a core refinement activity: the Product Owner reorders the backlog so the most valuable, ready items sit at the top, keeping the team focused on what delivers value next. This satisfies the stem's requirement for a genuine refinement activity rather than a Sprint Planning or Review task.

The Sprint Review is a Scrum event held at the end of each Sprint, where the Increment is inspected and stakeholders give feedback. It is one of Scrum's five formal ceremonies, satisfying the framework-practice constraint.

Round-robin brainstorming gives every attendee a structured turn to speak, which directly counters a dominant participant. Because the recruiters are invited to contribute in sequence, their process concerns surface before the HR director can steer the conversation back to dashboards. It is a recognized facilitation technique for equalizing participation and produces more complete requirements inputs for the onboarding system.

Delphi circulates anonymous questionnaires across several rounds, feeding back aggregated responses until estimates converge. Anonymity removes seniority and personality pressure that blocks open debate, satisfying the requirement to reach consensus when stakeholder input conflicts during prioritisation.

Recurring defects during executing point to inadequate quality management, which covers quality planning, assurance and control. Without assurance auditing work against defined standards, errors pass undetected into later phases and force rework, satisfying the stem's symptom of repeated deliverable correction.