Certified Associate in Project Management CAPM (CAPM) — Questions 76–150

The project charter formally authorizes the project and the project manager, and it gives the project manager authority to apply organizational resources to project activities. In a predictive project, this authorization is essential before the project manager can commit resources to the schedule and budget. It is the document the sponsor signs to empower the project manager.

Validation confirms the built product meets stakeholder needs and intended use. Demonstrating a working prototype to stakeholders and gathering their feedback tests whether the artefact is fit for purpose, which is validation rather than verification against specifications.

A cost-benefit analysis quantifies expected costs against projected benefits, yielding metrics such as net present value, ROI and payback period. This directly satisfies the stem's requirement to evaluate the proposed IT system's financial viability within the business case.

The board shows more cards in a column than that column's stated WIP limit permits, which is the violation the exhibit exposes. Exceeding the limit breaks the pull system's constraint, signalling the team must finish work before starting more.

Requirements documentation captures the agreed needs, features and constraints the product must satisfy, making it the primary source for defining product scope. The project charter authorises the project and states high-level scope, but detailed product boundaries derive from documented requirements.

The Sprint Goal gives the team focus and should not be changed arbitrarily. The Scrum Master should coach the Product Owner to refine and order new items for future Sprints, or if the new information invalidates the Sprint Goal, discuss whether the Sprint should be cancelled. This preserves empiricism and protects the team's focus.

Discounting $200,000 annually at 8% over five years gives a present value of approximately $798,542. Subtracting the $800,000 initial investment yields an NPV of about -$1,458, confirming the solution destroys value at this discount rate.

Parametric estimation multiplies the unit rate by quantity, then applies the productivity adjustment: 10 hours × 50 units = 500 hours, increased by 20% for slower new team members gives 500 × 1.2 = 600 hours. This satisfies the stem's stated productivity constraint.

A responsibility assignment matrix maps each work package or activity to the person accountable and responsible, typically using RACI notation. It is the document that makes role and responsibility assignments explicit, satisfying the need for the team to understand who does what.

The schedule management plan is a subsidiary component of the project management plan, describing how the schedule is developed, monitored and controlled. Project documents, by contrast, include items such as the schedule baseline's supporting activity lists and duration estimates.

Activity attributes are a documented output of Define Activities, extending the activity list with details such as predecessor relationships, leads and lags, resource requirements and imposed dates. They satisfy the stem's requirement for a Define Activities output rather than an input or tool.

The Daily Scrum is one of the five Scrum events defined in the Scrum Guide: a 15-minute daily inspection and adaptation by the Developers. This satisfies the stem's requirement to identify genuine Scrum events, distinguishing it from non-events such as backlog refinement.

The stakeholder register identifies everyone with an interest in the project, supplying the perspectives needed to surface risks during identification. It satisfies the input requirement by revealing external and internal parties whose objectives, concerns or influence may generate project threats and opportunities.

Re-estimating against the reduced capacity quantifies the schedule impact before any stakeholder communication, satisfying Alex's need to determine the delivery-date effect. Losing two developers lowers velocity, so revised estimates convert that lost throughput into a concrete forecast the product owner requires.

A negative net present value means discounted future cash inflows are worth less than the initial and ongoing outflows, so total costs exceed total benefits across the project's life. The project therefore destroys value at the required rate of return and should not proceed as analysed.

Daily integration into a shared trunk forces small, frequent merges, directly eliminating the long-lived branch divergence causing conflicts and integration delays. This is the defining practice of continuous integration, and it addresses the stem's constraint of frequent merge conflicts.

The Kano model classifies requirements by their effect on customer satisfaction, distinguishing basic, performance, delighter, indifferent and reverse attributes. It satisfies the stem's prioritisation requirement by revealing which features disproportionately raise satisfaction versus merely avoiding dissatisfaction.

Interviews are a direct way to gather requirements from stakeholders.

Test-driven development is a core XP engineering practise: tests are written before production code, then code is refactored to pass them. This satisfies the stem's requirement for a characteristic XP practise, distinguishing XP's technical discipline from Scrum's process focus.

Process modeling visually represents the sequence of activities, decision points, inputs, and outputs of a business process. It helps the business analyst capture the current state of the billing process, identify inefficiencies, and communicate requirements for the future state. This technique is specifically designed to analyze workflows and decision logic.

The Scrum Master is one of the three accountabilities defined in the Scrum Guide, serving the Scrum Team by coaching, removing impediments and fostering empiricism. This satisfies the stem's requirement for a formally defined Scrum role, alongside the Product Owner and Developers.

The lessons learned register is the living document updated throughout the project to capture knowledge gained during each phase. Recording these entries at phase closure lets the project manager feed validated insights into later phases, satisfying the stem's requirement to preserve lessons for future work rather than waiting until project closure.

The activity list is the primary output of Define Activities, enumerating all scheduled activities required to complete the project work. It satisfies the process output requirement by documenting activities that feed subsequent sequencing and estimation processes.

Project management is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements. Projects are temporary and produce unique deliverables. Operations management, in contrast, is concerned with the ongoing production of goods or services. This distinction is fundamental and is explicitly defined in the PMBOK Guide.

Lead time allows a successor task to begin before its predecessor completes, overlapping the two by two days. This satisfies the schedule constraint described in the stem, where the task starts early rather than waiting. It contrasts with lag, which imposes a delay between activities.

Revising questions to be open-ended and outcome-focused shifts elicitation from technical detail to business need, which is precisely the constraint the stem identifies: stakeholders cannot articulate requirements when questioned technically. Open-ended prompts let them describe goals and value in their own language, yielding clearer, more complete requirements.

The project charter is the document that formally authorises the project's existence and grants the project manager authority to apply organisational resources to project activities. It is issued by the sponsor, satisfying the stem's requirement for formal authorisation and resource authority.

The risk report is a documented output of Identify Risks, presenting overall risk exposure, prioritised individual risks and sources of uncertainty. It satisfies the process output requirement because it consolidates risk data for subsequent analysis and planning.

An RTM provides bidirectional linkage, mapping each requirement to its source, design, build and test artefacts. This satisfies the stem's need to track requirements from identification through delivery and testing, exposing gaps, gold-plating and unverified scope across the project lifecycle.

A data flow diagram (DFD) graphically represents the flow of data through a system, including external entities, processes, data stores, and data flows. It is specifically designed to show how data moves, where it is transformed, and where it is stored. In this scenario, the BA needs to depict the payroll system's data movement and transformations, making a DFD the most suitable model. DFDs are a core technique for documenting functional requirements.

Velocity is an empirical measure, so planning against the observed 30 points replaces the optimistic 40-point estimate. This aligns sprint scope with demonstrated capacity, prevents overcommitment, and gives the Product Owner a realistic forecast without punishing the team for learning the technology.

Surveys reach many dispersed stakeholders simultaneously at minimal cost, satisfying the limited budget and timeline constraint. Responses are collected asynchronously, avoiding travel and scheduling overhead that workshops, interviews or focus groups would impose across multiple locations.

In agile, changes are welcomed and managed through the product backlog. The product owner is responsible for prioritizing backlog items, and the team pulls work based on capacity. Adding the feature to the backlog allows it to be considered alongside other work, and the product owner can reprioritize based on value. This approach respects agile principles and the product owner's role.

Operations are ongoing, repetitive activities delivering the same product or service continuously, such as helpdesk support or manufacturing. This contrasts with projects, which are temporary and unique, satisfying the stem's requirement to distinguish the two.

High power with low interest maps to the Keep Satisfied quadrant, so the analyst engages enough to prevent the stakeholder blocking the project without overloading them with detail. This matches the grid's prescribed strategy for that power/interest combination.

Prioritisation with all stakeholders exposes the budget and timeline trade-offs, letting the group decide whether the email automation feature displaces other scope. This directly addresses the constraint conflict between the project manager, product owner and agreed baseline before any scope change is accepted.

Backlog refinement is an ongoing, continuous activity in Agile, not a phase-gated event. Performing it throughout the project keeps the backlog ordered, estimated and ready for upcoming sprints, directly satisfying the stem's Agile framework constraint. This continuous cadence ensures the team always has sufficient refined items to pull into the next iteration.

Acceptance means acknowledging the risk and choosing to take no proactive action, retaining the potential 20% cost increase should it occur. Because the probability is low, the project manager deliberately tolerates the risk without mitigation, transfer or avoidance, matching the stem's stated decision.

In a weak matrix, the project manager lacks formal authority over functional staff, so legitimate, reward and coercive power are unavailable. Expert power derives from technical knowledge and credibility, which earns voluntary cooperation from team members who respect the manager's competence.

Used to compare actual vs planned.

All requirements have associated test cases.

Establishing entry and exit criteria ensures that the review has a clear purpose and measurable outcomes. Entry criteria might include that requirements are documented and internally consistent, while exit criteria might be that all critical issues are resolved or logged. This structure prevents the review from becoming a free-form discussion and helps the BA measure its success. It is a key technique for effective requirements validation.

A control chart plots data over time with control limits to distinguish common cause variation from special cause variation. It reveals whether a process is stable and highlights unusual patterns such as trends or points outside limits. This directly matches the need to assess process stability and detect anomalies in defect counts.

Setting explicit pairing expectations and rotating driver/navigator roles addresses the discomfort by distributing control and reducing constant correction. The navigator reviews strategy rather than seizing the keyboard, so feedback becomes collaborative. Regular rotation satisfies the stem's need to foster a positive pairing experience within XP practice.

Realigning the requirements process with the enterprise's business analysis framework addresses the root cause of the scope changes and rework. Reviewing the framework and adjusting the process to comply restores consistency with organisational standards before further requirements work proceeds, which is the appropriate first corrective action.

The WBS decomposes scope downward until reaching work packages, the lowest-level components where cost and duration can be reliably estimated and work assigned. This satisfies the structural characteristic that work packages sit at the bottom of the hierarchy.

Purchasing insurance transfers the financial consequence of the risk to a third party, satisfying the high-probability, high-impact threat in this predictive construction project. Unlike mitigation, which reduces probability or impact, transfer shifts ownership of the loss to the insurer while the risk itself remains.

Scrum favors empirical, incremental improvement. By selecting only one or two actions and placing them in the Sprint Backlog, the team makes the improvement work visible alongside product work, and reviewing status at the next Retrospective closes the inspect-and-adapt loop. This is exactly how the Sprint Retrospective is meant to produce a tangible change rather than a wish list.

Progressive elaboration means project details are developed and refined iteratively as understanding grows, rather than fully defined at initiation. This distinguishes projects from routine operations, which follow stable, repeatable processes, and satisfies the characteristic of incremental planning under uncertainty.

Technical feasibility evaluates whether the organization has the technical resources, expertise, and infrastructure to build and maintain the proposed system. The scenario explicitly asks about evaluating technology and skills, which are core aspects of technical feasibility. The BA is assessing if the online ordering system can be developed with current capabilities, making technical feasibility the correct focus.

A business case documents the justification for a project, linking expected benefits, costs and risks directly to strategic objectives. It satisfies the stem's alignment constraint by evidencing how the proposed project delivers organisational goals, giving decision-makers the rationale to approve, reject or reprioritise the investment.

Analogous estimating uses historical data from comparable past projects to estimate current costs, typically at a summary level. It satisfies the predictive approach's need for a top-down, less detailed technique when limited information exists, though it is less accurate than bottom-up methods.

Sizing each story to fit within a single sprint keeps it independently deliverable and testable, satisfying the INVEST criterion of small size. This directly addresses the stem's best-practice requirement for well-formed stories, preventing stories that sprawl across iterations and stall feedback.

Objective success criteria must be measurable and verifiable against defined standards. Linking acceptance to specific compliance test results and target dates allows independent verification after closure rather than relying on subjective impressions. This approach ties the project's outcome to documented evidence, such as audit findings or test reports, which is exactly what an independent reviewer would examine to confirm the upgrade achieved its intended regulatory purpose.

Cost variance equals earned value minus actual cost: $25,000 − $40,000 = −$15,000. The negative result signals the project is over budget by $15,000 at month 2. Planned value is irrelevant to this calculation, so the $30,000 figure is excluded.

MoSCoW's Should-have category covers requirements that are important and valuable but not vital; they can be deferred to a later release without breaking core functionality. This satisfies the stem's constraint of a feature that is postponable without major impact, unlike Must-have items.

In a predictive project, the approved scope baseline can only change through integrated change control. Documenting the cost and schedule impact, informing the stakeholder, and submitting a formal change request to the change control board respects that authority rather than unilaterally altering scope.

Recording assumptions preserves momentum on the aggressive timeline while flagging the security gap explicitly. The assumptions log documents that security requirements remain unvalidated, and the head of security reviews them on return, satisfying both the two-week deadline and the need for authoritative sign-off on sensitive financial data controls.

Sequence Activities sits in the Planning process group, where dependencies between activities are identified and documented using techniques such as precedence diagramming. This satisfies the stem's requirement by naming a process performed during planning rather than initiation, execution, monitoring or closing.

Purchasing insurance shifts the financial consequence of the risk to a third party, which is the defining mechanism of transfer. It satisfies the stem's constraint of a high-impact, low-probability threat, where avoidance is impractical and mitigation cannot reduce the loss exposure itself. The risk remains, but its ownership moves to the insurer.

This directly addresses the root cause and aims to recover the schedule.

The Product Backlog is a formal Scrum artifact: an emergent, ordered list of everything needed to improve the product, owned by the Product Owner. It is the single source of work undertaken by the Scrum Team.

The concrete fails the contractual strength grade, so Maria must halt affected work and require conforming material. Supplier claims about generic industry standards do not override the project specifications. Stopping work prevents rework and satisfies the fixed budget and schedule constraints.

Scope defines the boundaries of the project and is a key constraint.

Non-functional requirements describe constraints or quality attributes that the system must meet, such as security, performance, or usability. The MFA compliance mandate is a security constraint imposed by regulations, so it is a non-functional requirement. It defines a condition the system must satisfy rather than a specific behavior like transferring funds. In this scenario, the BA must document it as a non-functional requirement to ensure compliance while balancing user experience.

Agile is ideal for projects with uncertain or evolving requirements because it embraces change and delivers value incrementally. Through iterative development and frequent stakeholder feedback, the team can adapt to new insights. This approach aligns with the sponsor's desire for quick value delivery and flexibility, making it the most suitable choice for this research project.

Scope modeling is a technique used to represent the boundaries of a solution, including what is included and excluded. It helps stakeholders visualize the scope and agree on what the solution will deliver. In this scenario, the sponsor wants to avoid unnecessary features, so scope modeling directly supports defining and communicating the solution boundaries, making it the correct technique.

Adding resources to critical path tasks shortens their duration through crashing, directly reducing total project duration. Only critical path activities affect the finish date, so this addresses the schedule variance, whereas adding resources elsewhere would not recover time.

Planning is where the project management plan and its subsidiary plans—including the schedule and resource management plan—are developed. The sponsor's request for detailed scheduling and resource assignment is exactly the work of Planning. This process group establishes scope, time, cost, and resource baselines before execution, so it is the correct group for the described activities.

Facilitated workshops bring key stakeholders together in a structured session led by a neutral facilitator to define requirements collaboratively. They are specifically designed to build shared understanding, resolve conflicts, and produce a agreed-upon set of requirements. In this scenario, with diverse participants, a facilitated workshop enables cross-functional input and real-time validation, making it the most appropriate technique for capturing all perspectives and reaching consensus.

Post-implementation requirements defects directly measure how well requirements were elicited, documented and managed, since each defect traces back to a missed, ambiguous or unvalidated requirement. This satisfies the stem's demand for an effectiveness metric by quantifying escaped errors rather than activity volume, giving the analyst concrete evidence of process performance after project completion.

Facilitating a meeting lets both stakeholders articulate their needs and negotiate a mutually acceptable resolution, addressing the conflict at its source. The business analyst mediates rather than unilaterally deciding, preserving stakeholder buy-in and ensuring the requirement reflects agreed priorities.

The stakeholder register is a project document that identifies the people, groups, or organizations that could impact or be impacted by the project. It includes information such as their interests, involvement, dependencies, influence, and potential impact on project success. This is exactly what the sponsor requested, making it the correct choice.