Certified Associate in Project Management CAPM CAPM Questions 151–225 | Page 3/7

151

MCQeasy

A project team is struggling with unclear roles and responsibilities, leading to duplicated work and missed tasks. Which document should the project manager create or update to resolve this issue?

A.Work breakdown structure (WBS)

B.Organizational breakdown structure (OBS)

C.Responsibility assignment matrix (RAM) in RACI format

D.Risk register

AnswerC

A RACI-format responsibility assignment matrix maps each task to who is Responsible, Accountable, Consulted and Informed, removing ambiguity about ownership. This directly resolves the duplicated work and missed tasks caused by unclear roles and responsibilities across the project team.

Why this answer

The Responsibility Assignment Matrix (RAM), particularly in RACI format, is the correct document to resolve unclear roles and responsibilities because it explicitly maps project tasks to team members, defining who is Responsible, Accountable, Consulted, and Informed. This eliminates ambiguity, prevents duplicated work, and ensures no tasks are missed by providing a clear, traceable assignment of duties.

Exam trap

PMI often tests the distinction between the WBS (what work is done) and the RAM (who does the work), leading candidates to incorrectly choose the WBS when the question specifically asks about roles and responsibilities.

How to eliminate wrong answers

Option A is wrong because the Work Breakdown Structure (WBS) decomposes project deliverables into smaller, manageable components but does not assign roles or responsibilities to individuals or teams. Option B is wrong because the Organizational Breakdown Structure (OBS) shows the hierarchical reporting structure of the organization, not the assignment of specific tasks to specific people. Option D is wrong because the Risk Register documents identified risks, their probability, impact, and response plans, but it does not address role clarity or task ownership.

Full explanation →

152

MCQmedium

During a sprint review, the team demonstrates a new feature to stakeholders. One stakeholder says, 'This isn't what we wanted. We need a completely different approach.' The product owner is upset because the feature took two weeks to build. The team is frustrated because they followed the product owner's specifications exactly. The Scrum Master observes that the product owner did not involve stakeholders during the sprint and based the user stories on assumptions. The product owner wants to add the rework to the next sprint. However, the team's capacity is already full. The Scrum Master needs to help the team and product owner recover. What should the Scrum Master do first?

A.Remove the product owner from the project to prevent future miscommunication

B.Blame the team for not clarifying requirements during the sprint

C.Coach the product owner to collaborate with stakeholders during the sprint to validate assumptions early

D.Add the rework to the next sprint and ask the team to work overtime

AnswerC

The root cause is that the product owner built user stories on assumptions without stakeholder validation. Coaching collaboration during the sprint lets assumptions be tested early, preventing costly rework and aligning delivered features with actual stakeholder needs before capacity is consumed.

Why this answer

The Scrum Master should first coach the product owner to collaborate with stakeholders throughout the sprint so assumptions are validated early, preventing late-surfacing misalignment. This addresses the root cause — the product owner built user stories on unvalidated assumptions without stakeholder involvement — rather than treating the symptom of rework. Coaching the product owner is a core Scrum Master responsibility and a servant-leadership action.

Exam trap

CAPM/Scrum questions often bait candidates into 'fixing' the symptom (adding rework, overtime, or removing people) instead of addressing the root cause through coaching and stakeholder collaboration, which is the Scrum Master's proper first action.

How to eliminate wrong answers

Option A is wrong because removing the product owner is a punitive, non-Scrum action that ignores the Scrum Master's role of coaching and facilitating, and it does not fix the underlying collaboration gap. Option B is wrong because blaming the team contradicts Scrum's self-managing, blameless culture and misattributes the failure — the team followed the specifications they were given. Option D is wrong because adding rework to an already-full sprint and demanding overtime violates sustainable pace, ignores capacity limits, and does not address the process failure that caused the rework.

Full explanation →

153

MCQhard

A Kanban team notices that their cumulative flow diagram (CFD) shows a widening band for the 'In Progress' column over several weeks, while the 'Done' band remains relatively flat. What is the most likely interpretation of this pattern?

A.The team has too few items in the backlog and should pull more work into the system.

B.The team is experiencing a bottleneck in the 'In Progress' stage, causing work to accumulate.

C.The team is delivering value at a steady rate and should maintain the current process.

D.The team is effectively limiting WIP and should continue as is.

AnswerB

A widening 'In Progress' band on a CFD indicates that more items are entering that stage than leaving it. This accumulation signals a bottleneck, where work is piling up because the stage cannot keep up with demand. The flat 'Done' band confirms that throughput is not increasing, so the team should investigate and address the constraint.

Why this answer

A cumulative flow diagram visualizes the amount of work in each stage over time. A widening 'In Progress' band with a flat 'Done' band means work is entering that stage faster than it is leaving, which is the classic signature of a bottleneck. The team should analyze the constraint and consider adjusting WIP limits or improving the process.

Exam trap

The trap here is misreading a widening band as a sign of increased productivity, when it actually indicates accumulating work and a bottleneck.

Full explanation →

154

MCQmedium

During requirements elicitation, a stakeholder suggests a feature that is out of scope and would significantly increase project cost. What is the best action for the business analyst?

A.Immediately update the project scope statement

B.Reject the idea and explain it is out of scope

C.Ask the project sponsor for approval to include the feature

D.Record the suggestion in the issue log and continue with planned elicitation

AnswerD

Recording the suggestion in the issue log preserves the out-of-scope request without expanding scope or cost, satisfying the constraint that the feature would significantly increase project cost. Elicitation then continues against the approved requirements, and the logged item is escalated later through integrated change control for a formal decision.

Why this answer

The business analyst should document out-of-scope suggestions in the issue log for future consideration, keeping the focus on the current scope and avoiding disruption of the elicitation session. Option A is incorrect as it prematurely changes scope without proper assessment; Option B is too dismissive and may discourage stakeholder input; Option C is premature because the sponsor should only be involved after a proper evaluation.

Full explanation →

155

MCQeasy

A project manager is using a predictive approach to manage a project. During the execution phase, the team is working on deliverables. Which process group involves tracking, reviewing, and regulating progress against the plan?

A.Monitoring and Controlling Process Group

B.Planning Process Group

C.Executing Process Group

D.Initiating Process Group

AnswerA

Monitoring and Controlling tracks, reviews and regulates project performance against the plan, comparing actual progress with baselines and initiating change requests. It spans execution, giving the predictive project its mechanism for measuring deliverable progress and correcting deviations.

Why this answer

The Monitoring and Controlling Process Group involves tracking, reviewing, and regulating progress against the plan. Option A is correct because this process group ensures that project objectives are met by measuring performance and applying corrective actions. The Planning Process Group (B) establishes the scope and plan; the Executing Process Group (C) involves completing the work; and the Initiating Process Group (D) defines the project.

Therefore, only Monitoring and Controlling fits the described activities.

Full explanation →

156

MCQeasy

In Scrum, what is the purpose of the Sprint Retrospective?

A.To inspect and adapt the team's process.

B.To review the product increment with stakeholders.

C.To plan the work for the next sprint.

D.To update the product backlog.

AnswerA

The Sprint Retrospective exists to inspect how the last Sprint went regarding individuals, interactions, processes, tools and Definition of Done, then adapt those elements. This directly satisfies the stem's focus on process improvement, distinguishing it from the Daily Scrum's daily inspection or the Sprint Review's product increment focus.

Why this answer

The Sprint Retrospective is the Scrum event specifically designed for the team to inspect how they worked during the Sprint and identify improvements to their processes, tools, and interactions. It occurs after the Sprint Review and before the next Sprint Planning, and its output is typically one or more actionable improvement items added to the next Sprint Backlog. Its focus is on the 'how' (process and people), not the 'what' (product).

Exam trap

CAPM often tests the confusion between the four Scrum events — candidates frequently mix up the Sprint Review (product inspection with stakeholders) and the Sprint Retrospective (process inspection by the team).

How to eliminate wrong answers

Option B is wrong because reviewing the product increment with stakeholders is the purpose of the Sprint Review, not the Retrospective. Option C is wrong because planning the work for the next sprint is the purpose of Sprint Planning. Option D is wrong because updating the Product Backlog is an ongoing Product Owner responsibility and is not the defined purpose of the Retrospective.

Full explanation →

157

Multi-Selectmedium

Which THREE of the following are typical components of a business case?

Select 3 answers

A.Project Charter

B.Work Breakdown Structure

C.Alternative Analysis

D.Financial Analysis

E.Risk Assessment

AnswersC, D, E

A business case compares viable options to demonstrate the chosen approach delivers best value, so Alternative Analysis is a standard component. It records the options considered, their relative costs and benefits, and the rationale for selection, satisfying the stem's requirement for typical business case content.

Why this answer

A business case typically includes an Alternative Analysis (C), which compares viable options (e.g., build vs. buy vs. do nothing) against criteria such as cost, benefit, and feasibility to justify the recommended solution. It also includes a Financial Analysis (D), covering metrics like ROI, NPV, payback period, and cost-benefit analysis that quantify the investment's value. A Risk Assessment (E) is likewise a standard component, identifying potential risks, their probability and impact, and mitigation strategies that affect the decision.

By contrast, the Project Charter (A) is a separate authorization document created after the business case is approved, and the Work Breakdown Structure (B) is a project-planning deliverable that decomposes scope into work packages, not a business case element.

Exam trap

CAPM often tests the distinction between pre-project documents (business case) and project authorization documents (project charter), so candidates who pick the charter as a business case component fall for the sequencing trap.

Full explanation →

158

MCQeasy

A project manager is leading a team in a matrix organization where team members report to both a functional manager and the project manager. The project is in the planning phase. What is the primary responsibility of the project manager during this phase?

A.Managing team conflicts

B.Assigning daily tasks to team members

C.Closing out the project

D.Developing the project management plan

AnswerD

In a matrix organisation, the project manager owns the project management plan, integrating scope, schedule, cost and risk baselines. During planning, producing this plan is the primary responsibility, while functional managers handle resource allocation and technical supervision of shared staff.

Why this answer

During the planning phase, the project manager's primary responsibility is to develop the project management plan, which integrates all subsidiary plans and baselines. This is a core PMBOK process. In a matrix organization, the project manager still owns this deliverable, though resource assignments may involve functional managers.

Exam trap

CAPM often tests the confusion between planning and executing responsibilities, so candidates must remember that developing the project management plan is a planning phase activity, while assigning tasks and managing conflicts are executing activities.

How to eliminate wrong answers

Option A is wrong because managing team conflicts is primarily an executing and monitoring/controlling activity, not the primary planning phase responsibility. Option B is wrong because assigning daily tasks is an executing activity, and in a matrix organization, functional managers often handle task assignments. Option C is wrong because closing out the project occurs in the closing phase, not planning.

Full explanation →

159

MCQmedium

During project execution, a key stakeholder requests a change that would add a new feature to the product. The project manager evaluates the impact on scope, schedule, and cost. According to the change management plan, which step should the project manager take first?

A.Analyze the impact of the change on the project constraints

B.Submit the change request to the change control board (CCB) for approval

C.Implement the change and document it later

D.Reject the change because it was not part of the original scope

AnswerA

Evaluating the impact on scope, schedule, and cost is the documented first step before a change request reaches the change control board. The change management plan requires this impact analysis so the board can make an informed approve, reject, or defer decision.

Why this answer

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.

Exam trap

The trap here is that candidates often jump to 'submit to CCB' (Option B) because they know changes need approval, but they forget that the impact analysis must be completed first to provide the CCB with the necessary information for decision-making.

How to eliminate wrong answers

Option B is wrong because submitting the change request to the CCB for approval should only occur after the impact analysis has been completed and documented; the CCB needs the impact data to make an informed decision. Option C is wrong because implementing the change without prior approval and documentation bypasses the formal change control process and risks uncontrolled scope creep, budget overruns, and schedule delays. Option D is wrong because rejecting a change solely because it was not part of the original scope ignores the possibility that the change could add value and be accommodated through proper change control procedures.

Full explanation →

160

MCQmedium

A construction project is underway. The project manager receives a report that the concrete supplier will deliver late, causing a two-week delay. The project has no schedule reserve. What is the best course of action?

A.Inform the sponsor and request a schedule extension

B.Immediately crash the schedule by adding resources to critical path activities

C.Fast-track the remaining activities to recover the delay

D.Analyze the impact on the critical path and evaluate options

AnswerD

Analysing the critical path determines whether the two-week concrete delay genuinely extends project completion, since only critical activities drive the finish date. With no schedule reserve available, the project manager must then evaluate recovery options such as crashing, fast-tracking or resequencing. This satisfies the stem's constraint by quantifying impact before committing to corrective action.

Why this answer

When a delay occurs and there is no schedule reserve, the project manager must first understand the actual impact before taking action. Analyzing the critical path reveals whether the two-week delay directly extends the project finish date or whether float exists elsewhere. Only after this analysis can the PM evaluate recovery options such as crashing, fast-tracking, or negotiating scope.

Jumping straight to escalation or compression without impact analysis is premature and may waste resources.

Exam trap

CAPM often tests the reflex to escalate or compress immediately when a delay is reported, but the PMBOK-aligned answer is always to analyze impact first before selecting a response.

How to eliminate wrong answers

Option A is wrong because informing the sponsor and requesting an extension is a last resort, not the first step — the PM must analyze impact and evaluate alternatives before escalating. Option B is wrong because crashing is a compression technique that should only be applied after confirming the delay affects the critical path and after weighing cost/benefit; blindly adding resources may not help and increases cost. Option C is wrong because fast-tracking increases risk and should only be chosen after impact analysis shows it is a viable recovery option, not as an immediate reflex.

Full explanation →

161

MCQhard

A business analyst is preparing a business case for a project with intangible benefits. How should the intangible benefits be presented to support the business case?

A.List intangible benefits without explanation to keep the business case concise

B.Quantify intangible benefits using the cost-benefit ratio

C.Assign a monetary value to each intangible benefit

D.Provide a qualitative description with supporting evidence such as customer surveys

AnswerD

Intangible benefits resist reliable monetary quantification, so a qualitative description backed by evidence such as customer surveys supports the business case without fabricating financial figures. This satisfies the stem's requirement to present intangible benefits credibly, letting decision-makers weigh non-financial value alongside measurable returns.

Why this answer

Intangible benefits cannot be reliably quantified in monetary terms, so the business case should present them qualitatively with supporting evidence such as customer surveys, market research, or expert opinions. This provides decision-makers with context without forcing false precision. The PMBOK Guide and CAPM emphasize that intangible benefits are described, not monetized.

Exam trap

CAPM often tests the misconception that all benefits must be monetized; candidates may incorrectly choose to assign monetary values to intangibles rather than describing them qualitatively.

How to eliminate wrong answers

Option A is wrong because listing intangible benefits without explanation fails to communicate their value and weakens the business case. Option B is wrong because the cost-benefit ratio requires monetary values for benefits, which cannot be accurately assigned to intangibles. Option C is wrong because assigning a monetary value to intangibles is subjective and can mislead stakeholders; it is not a recommended practice.

Full explanation →

162

Drag & Dropmedium

Drag and drop the steps for managing project communications in the correct order.

Drag or tap steps into the slots.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

Communications management: plan (including requirements and technology), manage, and monitor.

Full explanation →

163

MCQeasy

During project execution, a key stakeholder requests a new feature that was not included in the approved scope. What should the project manager do first?

A.Perform a change impact analysis

B.Escalate to the project sponsor for decision

C.Inform the stakeholder that the scope is frozen

D.Add the feature to the next iteration

AnswerA

Change impact analysis evaluates how the requested feature affects scope, schedule, cost, and risk before any decision. It is the prerequisite step that gives the project manager and change control board the information needed to approve, defer, or reject the request, rather than immediately altering the approved baseline.

Why this answer

When a stakeholder requests a change to approved scope, the project manager should first perform a change impact analysis to assess the effect on scope, schedule, cost, quality, and risk. This analysis informs the change control process and provides the Change Control Board (CCB) or sponsor with the necessary information to make a decision. It is the first step before escalation or approval.

Exam trap

CAPM often tests the sequence of change control, causing candidates to select escalation or rejection before performing the necessary impact analysis.

How to eliminate wrong answers

Option B is wrong because escalating to the sponsor before performing an impact analysis is premature; the sponsor needs the analysis to make an informed decision. Option C is wrong because informing the stakeholder that scope is frozen is incorrect; changes can be considered through the change control process. Option D is wrong because adding the feature to the next iteration without analysis bypasses the change control process and may cause scope creep.

Full explanation →

164

MCQmedium

An organization is transitioning from a traditional project management approach to Scrum. The project manager has been reassigned as a Scrum Master but continues to assign tasks to team members and track individual progress. The team is becoming demotivated. What should the Scrum Master do differently?

A.Coach the team to self-organize and take ownership of their work

B.Continue assigning tasks but explain that it is necessary for accountability

C.Switch to Kanban to reduce process overhead

D.Ask the team to write daily status reports to increase visibility

AnswerA

A Scrum Master must coach self-organisation, not direct work. Assigning tasks and tracking individuals sustains command-and-control, which demotivates the team. Coaching ownership satisfies the transition constraint by shifting authority to the team, letting them pull and manage their own work.

Why this answer

A Scrum Master is a servant-leader who coaches the team toward self-organization and cross-functionality, not a task-assigning manager. By continuing to assign tasks and track individual progress, the project manager is preserving command-and-control behaviors that undermine the team's ownership and intrinsic motivation. The correct shift is to coach the team to pull work from the Sprint Backlog, self-organize around the Sprint Goal, and hold each other accountable as a collective.

Exam trap

CAPM often tests the misconception that a Scrum Master is a renamed project manager who assigns work, so candidates pick options that preserve task assignment or status reporting instead of coaching self-organization.

How to eliminate wrong answers

Option B is wrong because continuing to assign tasks — even with an accountability rationale — perpetuates the very anti-pattern causing demotivation; Scrum explicitly rejects individual task assignment by a manager. Option C is wrong because switching to Kanban is a process change that does not address the root cause (the Scrum Master's command-and-control behavior) and is not a Scrum Master's call to make unilaterally. Option D is wrong because daily status reports increase management visibility and overhead, reinforcing the reporting-to-manager dynamic rather than fostering team self-management.

Full explanation →

165

MCQmedium

A project manager is developing the project charter for a new marketing campaign. The sponsor asks which document formally authorizes the project and gives the project manager authority to apply organizational resources. What is the correct answer?

A.Project charter

B.Project management plan

C.Business case

D.Benefits management plan

AnswerA

The project charter formally authorizes the project and gives the project manager authority to apply organizational resources to project activities. It is issued by the sponsor or initiating entity. For the marketing campaign, the charter is the document that officially starts the project and empowers the project manager.

Why this answer

The project charter is the document 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 typically issued by the sponsor or a senior manager. Without a charter, the project manager may lack the necessary authority to proceed effectively.

Exam trap

The trap here is assuming that the business case or benefits management plan authorizes the project, when only the charter grants formal authority.

Full explanation →

166

Multi-Selectmedium

A Scrum Team is preparing for its first Sprint. The Product Owner has a prioritized Product Backlog, and the team is defining its Definition of Done. Which two characteristics are essential for a useful Definition of Done? (Choose two.)

Select 2 answers

A.It is a shared understanding among the Scrum Team.

B.It is created solely by the Product Owner without team input.

C.It includes quality criteria that the Increment must meet.

D.It is a fixed document that cannot be changed once the Sprint begins.

E.It is kept confidential from stakeholders to avoid scope creep.

AnswersA, C

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It must be shared and understood by the entire Scrum Team—Product Owner, Scrum Master, and Developers—so everyone agrees on what 'done' means. This shared understanding prevents disputes about completeness and ensures transparency.

Why this answer

A useful Definition of Done is a shared understanding across the Scrum Team and includes the quality criteria the Increment must meet. It is not created solely by the Product Owner, is not kept confidential from stakeholders, and is not an unchangeable document. These characteristics ensure transparency, alignment, and consistent quality.

Exam trap

The trap here is assuming the Definition of Done is a fixed document owned exclusively by the Product Owner, when it is actually a shared team agreement that can evolve.

Full explanation →

167

MCQeasy

A project manager is leading a predictive project to develop a new software system. The project sponsor asks for a document that formally authorizes the project and provides the project manager with the authority to apply organizational resources to project activities. Which document should the project manager reference?

A.Benefits management plan

B.Project management plan

C.Project charter

D.Business case

AnswerC

The project charter is the document issued by the project initiator or 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 a key input to the Develop Project Charter process and is essential for initiating a predictive project. This directly matches the scenario's requirement.

Why this answer

The project charter is the formal document that authorizes the project and gives the project manager the authority to use organizational resources. It is created during the project initiation phase and is essential for predictive projects. The business case and benefits management plan are inputs to the charter, while the project management plan is developed later and does not serve as the authorization document.

Exam trap

The trap here is confusing the project charter with the project management plan, as both are key documents, but only the charter formally authorizes the project and grants authority.

Full explanation →

168

MCQmedium

A project manager is leading a marketing campaign project for a regional retailer. The sponsor asks the project manager to classify the effort. The work involves producing a one-time series of promotional videos and launching them by a fixed holiday deadline, after which the team is released. Which characteristic best supports classifying this as a project rather than ongoing operations?

A.The work is performed by a cross-functional team using established organizational processes.

B.The work is temporary and produces a unique deliverable with a defined start and end.

C.The work consumes a budget and requires coordination across several departments.

D.The work is repeated annually for each seasonal promotion to sustain ongoing revenue.

AnswerB

Temporariness and uniqueness are the defining characteristics of a project. The promotional video campaign has a clear beginning and end tied to the holiday launch, and the resulting campaign deliverable is unique rather than repetitive. Because the team is released after the deadline, the effort does not continue indefinitely, which is exactly what distinguishes a project from ongoing operational work.

Why this answer

A project is a temporary endeavor undertaken to create a unique product, service, or result. The campaign has a fixed holiday deadline, a unique set of promotional videos, and a team that is released afterward, satisfying both temporariness and uniqueness. Budgets, coordination, and cross-functional staffing exist in operations too, so they cannot by themselves justify the project classification.

Exam trap

The trap here is assuming that any funded, cross-departmental effort must be a project, when budget and coordination also describe routine operations.

Full explanation →

169

MCQeasy

A business analyst is facilitating a requirements workshop. Which technique is best for generating a large number of ideas in a short time?

A.Multi-voting

B.Nominal group technique

C.Affinity diagram

D.Brainstorming

AnswerD

Brainstorming is a group creativity technique designed to generate many ideas rapidly by encouraging free contribution without immediate criticism. It directly satisfies the goal of producing a large volume of ideas within a short workshop timeframe.

Why this answer

Brainstorming is specifically designed to generate a large volume of ideas quickly by encouraging free-form contributions without immediate criticism or evaluation. It is the standard technique for divergent thinking in a requirements workshop. Other listed techniques are used for organizing, ranking, or refining ideas after they have been generated.

Exam trap

CAPM often tests the distinction between divergent techniques (brainstorming) and convergent techniques (multi-voting, affinity diagrams), catching candidates who pick a prioritization tool for an idea-generation question.

How to eliminate wrong answers

Option A is wrong because multi-voting is a convergent technique used to narrow down and prioritize an existing list of ideas, not to generate new ones. Option B is wrong because nominal group technique is a structured variant that includes silent idea generation followed by discussion and ranking — it is slower and more controlled than brainstorming. Option C is wrong because an affinity diagram is used to group and organize ideas into themes after generation, not to produce them.

Full explanation →

170

MCQmedium

A Scrum Team is struggling with its Daily Scrum. Team members give detailed status updates to the Scrum Master, and the meeting often runs 30 minutes. The Scrum Master wants to improve the event. Which action best aligns with Scrum?

A.Ask each team member to prepare a detailed report for the Scrum Master to review after the Daily Scrum.

B.Coach the Developers to focus on progress toward the Sprint Goal and re-plan the day's work, keeping the event to 15 minutes.

C.Extend the Daily Scrum to 30 minutes officially so the team can cover all details without feeling rushed.

D.Have the Scrum Master collect written status updates before the meeting and share them, cancelling the Daily Scrum.

AnswerB

The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. The Scrum Master should coach the team to self-manage the event, focus on the Sprint Goal, and avoid status reporting to the Scrum Master, which improves collaboration and keeps the event time-boxed.

Why this answer

The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. The Scrum Master should coach the team to focus on the Sprint Goal, self-manage the event, and avoid status reporting. This improves collaboration and keeps the event within its time-box.

Exam trap

The trap here is treating the Daily Scrum as a status meeting for the Scrum Master rather than a self-managed inspect-and-adapt event for the Developers.

Full explanation →

171

MCQeasy

In business analysis, what is the purpose of a stakeholder analysis?

A.Determine the communication needs and influence of stakeholders.

B.Create a project schedule.

C.Identify all project risks.

D.Assign team roles and responsibilities.

AnswerA

Stakeholder analysis maps each party's interest, influence and impact on the project, which directly determines their information requirements and preferred communication channels. This lets the BA tailor engagement and reporting to the constraint of differing stakeholder power, rather than treating all parties identically.

Why this answer

Stakeholder analysis is a core business analysis technique used to identify stakeholders, assess their interests, influence, and expectations, and determine how to engage them effectively. Option A is correct because understanding communication needs and influence is the primary purpose, enabling the business analyst to tailor engagement strategies and ensure stakeholder requirements are captured and managed.

Exam trap

PMI often tests the distinction between stakeholder analysis (which focuses on influence and communication needs) and other planning processes like risk identification or role assignment, tempting candidates to confuse stakeholder analysis with broader project planning activities.

How to eliminate wrong answers

Option B is wrong because creating a project schedule is a project management activity under Time Management, not a purpose of stakeholder analysis. Option C is wrong because identifying all project risks is the purpose of risk management processes, not stakeholder analysis, though stakeholder analysis can inform risk identification. Option D is wrong because assigning team roles and responsibilities is part of Human Resource Management or project team planning, not the direct output of stakeholder analysis.

Full explanation →

172

MCQmedium

A project manager is leading a software development project. The sponsor has requested a new feature that was not part of the original scope. The project manager assesses that adding this feature will require additional resources and will extend the timeline by two weeks. What should the project manager do first?

A.Refuse the request because it is out of scope.

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

C.Instruct the team to implement the feature and track extra time as overtime.

D.Immediately update the project schedule and budget.

AnswerB

The project manager must first perform integrated change control by assessing how the added feature affects scope, schedule, cost and resources. Only then can a formal change request be submitted to the change control board for approval or rejection.

Why this answer

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.

Exam trap

The trap here is that candidates confuse a sponsor's authority with the need for formal change control, assuming the sponsor can bypass the change request process, but the PM must still follow the defined change management procedures regardless of who makes the request.

How to eliminate wrong answers

Option A is wrong because refusing a sponsor request outright bypasses the formal change management process; the project manager should assess and document the impact first. Option C is wrong because instructing the team to implement the feature without a change request violates scope control and can lead to unauthorized work, budget overruns, and schedule compression issues. Option D is wrong because immediately updating the schedule and budget without a formal change request and approval ignores the need for impact analysis and CCB authorization.

Full explanation →

173

Multi-Selectmedium

Which TWO are benefits of creating a Work Breakdown Structure (WBS)?

Select 2 answers

A.Identifies project risks

B.Defines the total scope

C.Provides a basis for cost estimates

D.Assigns resources to activities

E.Shows dependencies between activities

AnswersB, C

The WBS decomposes all project deliverables into work packages, so nothing required by the scope statement is omitted and nothing outside it is included. This complete hierarchical decomposition is what defines and confirms the total scope baseline.

Why this answer

Option B is correct because the WBS decomposes the entire project deliverable into progressively smaller work packages, thereby defining and confirming the total scope of the project and preventing scope creep. Option C is correct because these work packages provide the granular level at which costs can be estimated, budgeted, and later controlled, making the WBS the foundation for cost estimating. Option A is not a WBS benefit because risk identification is performed through risk management processes such as risk identification workshops, not through scope decomposition.

Option D is not a WBS benefit because resource assignment occurs in schedule and resource planning activities (for example, using a RACI chart or resource histogram), not in the WBS itself. Option E is not a WBS benefit because activity dependencies are determined through sequence activities techniques such as precedence diagramming, which is part of schedule development rather than scope decomposition.

Exam trap

CAPM often tests the confusion between WBS benefits and other project management artifacts, such as risk identification or activity sequencing, leading candidates to select incorrect options.

Full explanation →

174

MCQmedium

A business analyst is evaluating the success of a recently completed project. The project delivered all requirements on time and within budget, but end-users are dissatisfied with the functionality. Which business analysis technique should the analyst use to assess this discrepancy?

A.SWOT analysis

B.Lessons learned

C.Root cause analysis

D.Cost-benefit analysis

AnswerC

Root cause analysis investigates why delivered requirements failed to satisfy users despite meeting scope, schedule and budget, exposing gaps between stated requirements and actual needs. This technique directly assesses the discrepancy between project outputs and user expectations.

Why this answer

Root cause analysis is the technique used to dig past the symptom (user dissatisfaction) to the underlying causes — such as poorly elicited requirements, missing stakeholder validation, or a gap between stated and actual needs. Since the project met time and budget but missed the actual business need, the discrepancy is a quality/requirements problem, and RCA (e.g., 5 Whys, fishbone) is the correct diagnostic tool.

Exam trap

CAPM often tests the confusion between lessons learned (documenting for the future) and root cause analysis (diagnosing the present problem), so candidates pick 'lessons learned' because it sounds like the natural post-project activity.

How to eliminate wrong answers

Option A is wrong because SWOT analysis assesses strategic Strengths, Weaknesses, Opportunities, and Threats of an organization or initiative — it is a planning tool, not a post-mortem diagnostic for requirement failures. Option B is wrong because lessons learned captures what went well and what did not for future projects, but it does not systematically identify the causal chain behind this specific discrepancy. Option D is wrong because cost-benefit analysis evaluates whether the investment was financially justified; here the project was on budget, so cost is not the issue — the functionality gap is.

Full explanation →

175

Multi-Selecthard

A project manager is developing the project management plan for a complex software development project. The project manager needs to ensure that the plan includes all necessary subsidiary plans and baselines. Which three of the following are components of the project management plan? (Choose three.)

Select 3 answers

A.Cost baseline

B.Schedule baseline

C.Project statement of work

D.Scope management plan

E.Business case

AnswersA, B, D

The cost baseline is a time-phased budget that is used to measure, monitor, and control overall cost performance on the project. It is a component of the project management plan and is developed as part of the Cost Management knowledge area.

Why this answer

The project management plan integrates and consolidates all subsidiary plans and baselines. Key components include the scope management plan, which outlines how scope will be managed; the cost baseline, which is the approved time-phased budget; and the schedule baseline, which is the approved schedule used for performance measurement. The project statement of work and business case are inputs to project charter development, not components of the plan.

Exam trap

The trap here is confusing project inputs like the business case and statement of work with components of the project management plan.

Full explanation →

176

MCQmedium

During a predictive project, a team member reports that a critical path activity is behind schedule by two days. To recover the schedule, the project manager should first:

A.Perform schedule compression analysis

B.Fast-track the project

C.Add resources to the critical path

D.Accept the delay and update the baseline

AnswerA

Schedule compression analysis evaluates crashing and fast-tracking against the critical path, directly addressing the two-day slippage while protecting the project end date. It is the prescribed first response because it quantifies viable recovery options before committing resources, satisfying the stem's requirement to recover the schedule without prematurely altering scope or baseline.

Why this answer

The project manager should first perform schedule compression analysis because it is the analytical technique used to evaluate options for recovering a delayed schedule. Schedule compression includes both crashing and fast-tracking, so it allows the PM to compare alternatives and choose the best recovery approach rather than committing prematurely to one method. This aligns with the PMBOK Guide's emphasis on analysis before action in the Control Schedule process.

Exam trap

CAPM often tests the distinction between analytical techniques and specific actions, so candidates may jump to a concrete solution like fast-tracking or crashing instead of first performing the broader analysis of schedule compression options.

How to eliminate wrong answers

Option B is wrong because fast-tracking is only one specific schedule compression technique and may introduce rework risk; the PM should not select it before analyzing all compression options. Option C is wrong because adding resources is a form of crashing, which is another specific compression technique that may increase cost and risk; it should not be the first action without analysis. Option D is wrong because accepting the delay and updating the baseline is a last resort after all recovery options have been evaluated and rejected, not an initial response to a two-day slip.

Full explanation →

177

MCQmedium

A business analyst is creating a requirements traceability matrix. Which purpose does this serve?

A.Link requirements to business objectives and deliverables.

B.Track the status of requirement approval.

C.Document the rationale for requirement changes.

D.Ensure each requirement maps to a test case.

AnswerA

A requirements traceability matrix maps each requirement to its originating business objective and the deliverables that satisfy it, ensuring scope alignment and preventing orphaned requirements. This directly fulfils the purpose of linking requirements to business objectives and deliverables throughout the project lifecycle.

Why this answer

The requirements traceability matrix (RTM) is a tool used to trace requirements throughout the project lifecycle. Its primary purpose is to link requirements to business objectives and deliverables, ensuring that every requirement contributes to the project's goals and can be traced forward to deliverables and backward to origin. Option A correctly identifies this purpose.

Option B is incorrect because tracking the status of requirement approval is a function of a requirements status report, not the RTM. Option C is incorrect because documenting the rationale for requirement changes is typically done in a change log or requirements management plan. Option D is incorrect while mapping requirements to test cases is a common use of the RTM, it is not its primary purpose.

Full explanation →

178

MCQeasy

A BA is conducting a feasibility study. Which factor is assessed to determine if the project aligns with strategic goals?

A.Technical feasibility

B.Schedule feasibility

C.Organizational feasibility

D.Economic feasibility

AnswerC

Organizational feasibility examines whether the project supports the company's strategic objectives, available resources and stakeholder alignment. This directly satisfies the stem's requirement to assess alignment with strategic goals, distinguishing it from technical or economic feasibility, which address capability and cost instead.

Why this answer

Organizational feasibility assesses whether the project aligns with the strategic goals of the organization by evaluating factors such as management support, stakeholder buy-in, and cultural fit. This ensures the project supports the overall business strategy and has the necessary organizational commitment to succeed.

Exam trap

The trap here is that candidates often confuse economic feasibility (cost-benefit analysis) with strategic alignment, but economic feasibility focuses on financial viability, not whether the project supports the organization's strategic direction.

How to eliminate wrong answers

Option A is wrong because technical feasibility evaluates whether the required technology and technical resources exist to implement the solution, not alignment with strategic goals. Option B is wrong because schedule feasibility assesses whether the project can be completed within the required timeframes, not strategic alignment. Option D is wrong because economic feasibility (cost-benefit analysis) determines if the project provides financial value, but does not directly assess alignment with strategic goals.

Full explanation →

179

MCQmedium

A project manager is leading a software development project using a predictive life cycle. The team has completed the requirements documentation and is now breaking down the work into smaller, manageable components. The project manager wants to ensure that the work is decomposed to the level where it can be reliably estimated and controlled. Which technique should the project manager use?

A.Estimate Activity Durations

B.Create WBS

C.Define Activities

D.Sequence Activities

AnswerB

The Create WBS process involves subdividing project deliverables and project work into smaller, more manageable components called work packages. This decomposition allows for better estimation, scheduling, and control. It is performed during the planning phase and results in a WBS that defines the total scope of the project. The work packages at the lowest level can be estimated and managed effectively.

Why this answer

The Create WBS process is used to decompose project deliverables and work into smaller, manageable work packages. This decomposition is essential for accurate estimation, scheduling, and control. The other processes listed are subsequent steps that rely on the WBS and activity list, so they do not address the need to break down the work initially.

Exam trap

The trap here is confusing the decomposition of deliverables (Create WBS) with the decomposition of work packages into activities (Define Activities), or assuming that estimating durations is part of the breakdown process.

Full explanation →

180

MCQmedium

A Scrum team's Sprint Review is scheduled for Friday afternoon. The team has completed all but two Product Backlog items. The Product Owner asks the Scrum Master whether the incomplete items should be demonstrated during the Sprint Review. What is the most appropriate guidance the Scrum Master should provide?

A.Cancel the Sprint Review because the Sprint Goal was not fully met and the Increment is incomplete.

B.Ask the Product Owner to move the incomplete items to the next Sprint and exclude them from any discussion during the Sprint Review.

C.Demonstrate only the items that meet the Definition of Done, and discuss the incomplete items as part of the review's inspection of the Increment.

D.Demonstrate all items, including the incomplete ones, to show stakeholders the team's full effort during the Sprint.

AnswerC

The Sprint Review inspects the Increment, and only work meeting the Definition of Done is considered part of the Increment. The Scrum Master should guide the team to demonstrate completed items and use the review to inspect progress, adapt the Product Backlog, and gather stakeholder feedback, rather than presenting unfinished work as done.

Why this answer

The Sprint Review inspects the Increment and adapts the Product Backlog. Only work meeting the Definition of Done counts as part of the Increment, so completed items are demonstrated, while incomplete items are discussed to inform adaptation. The Scrum Master should guide the team toward transparency and empiricism rather than hiding or misrepresenting progress.

Exam trap

The trap here is assuming the Sprint Review is a status presentation where all work, finished or not, must be shown to stakeholders.

Full explanation →

181

MCQhard

A geographically distributed agile team using Scrum is experiencing frequent integration issues and delays caused by incompatible code changes. Which Extreme Programming (XP) practice would best address this problem?

A.Pair programming

B.Continuous integration

C.Test-driven development (TDD)

D.Refactoring

AnswerB

Continuous integration requires developers to merge code into a shared repository frequently, with automated builds and tests detecting incompatibilities early. This directly resolves the distributed team's integration issues and delays caused by incompatible code changes, a specific XP practice addressing exactly that constraint.

Why this answer

Continuous integration (CI) is an XP practice where team members integrate their code changes into a shared repository multiple times a day, with each integration verified by an automated build and test suite. For a geographically distributed Scrum team, CI directly addresses integration issues by catching incompatible changes early, reducing the time and effort required to resolve conflicts. It ensures that code from different developers is continuously merged and validated, preventing the accumulation of divergent changes that cause delays.

Exam trap

CAPM often tests the distinction between XP practices, and candidates may confuse continuous integration with test-driven development or pair programming, overlooking that CI specifically targets integration frequency and automation.

How to eliminate wrong answers

Option A is wrong because pair programming improves code quality and knowledge sharing but does not automatically detect or resolve integration conflicts between separate code branches. Option C is wrong because test-driven development (TDD) focuses on writing tests before code to drive design and ensure correctness, but without continuous integration, tests may not be run against the latest integrated codebase, so integration issues can still persist. Option D is wrong because refactoring improves internal code structure without changing external behavior, but it does not address the coordination and merging of changes from multiple developers, which is the core of integration problems.

Full explanation →

182

Multi-Selecteasy

Which TWO are benefits of using an iterative approach in agile projects?

Select 2 answers

A.Ability to adapt to changing requirements

B.Less documentation is needed

C.Faster feedback from stakeholders

D.Reduced overall project cost

E.Postponed testing until the end of the project

AnswersA, C

Iterative delivery produces working increments each cycle, so stakeholder feedback and newly discovered requirements can be incorporated into subsequent iterations rather than frozen at project start. This directly satisfies the stem's demand for adaptation to changing requirements, which predictive waterfall planning cannot accommodate once baselined.

Why this answer

Option A is correct because iterative development delivers working increments each iteration, allowing the team to incorporate changing requirements between iterations rather than being locked into an upfront specification. Option C is correct because each iteration produces a demonstrable increment that stakeholders can review, generating frequent and early feedback that guides subsequent work. Option B is not a defining benefit, since agile values working software over comprehensive documentation but does not eliminate necessary documentation.

Option D is not guaranteed, as iterative approaches can increase cost through rework and continuous involvement. Option E is incorrect because testing is continuous within each iteration, not postponed to the end.

Exam trap

The trap is assuming that iterative approaches automatically reduce documentation or cost, or that testing is postponed, when in fact iterative methods emphasize continuous testing and may not reduce cost.

Full explanation →

183

MCQmedium

You are a project manager in a functional organization managing a software upgrade project. The functional managers control resources and priorities. Your project requires a senior developer from the IT department for two weeks starting next Monday. The IT functional manager informs you that the developer is assigned to an urgent operational issue and cannot be released until further notice. The project has a fixed deadline in four weeks, and any delay will impact the next phase. You have already used your influence and escalated to senior management, but the functional manager insists on keeping the developer. What should you do next?

A.Update the project schedule to reflect the delay and inform stakeholders

B.Escalate the issue to the CEO to override the functional manager

C.Negotiate with the functional manager for partial release of the developer or a qualified replacement

D.Direct the developer to work on the project despite the functional manager's order

AnswerC

In a functional organisation the functional manager controls resource allocation, and escalation has already failed. Negotiating partial release or a qualified replacement secures some capacity without further confrontation, protecting the fixed four-week deadline while respecting that manager's authority over operational priorities.

Why this answer

In a functional organization, the project manager has limited authority over resources. Since the functional manager controls the developer's assignments, negotiating for a partial release (e.g., part-time work) or a qualified replacement is the most realistic next step to minimize project delay. Updating the schedule (A) would be premature without exhausting negotiation.

Escalating to the CEO (B) may bypass the functional manager and damage relationships, and ordering the developer to work (D) is beyond the PM's authority in this structure.

Full explanation →

184

MCQhard

You are a business analyst on a project to replace the legacy inventory system with a cloud-based solution. The project is using a predictive lifecycle, and the requirements specification has been baselined. During the design phase, the vendor informs you that a key feature (real-time reporting) cannot be implemented within the current budget because it requires additional licensing. The feature is critical to the business case's expected cost savings. The project manager wants to descope the feature to stay within budget. As the business analyst, what is the most appropriate action?

A.Escalate the issue to the program manager and ask for a decision.

B.Agree to descope the feature and update the requirements document accordingly.

C.Request additional budget from the sponsor to cover the extra licensing cost.

D.Perform a cost-benefit analysis of including the feature versus descoping it, and present options to the sponsor.

AnswerD

With baselined requirements and a critical feature at risk, the business analyst must evaluate the trade-off rather than silently descope. A cost-benefit analysis comparing inclusion against descoping, presented to the sponsor, preserves the business case's cost savings and lets the authority decide.

Why this answer

As a business analyst in a predictive lifecycle with baselined requirements, any change to scope must go through formal change control. The most appropriate action is to perform a cost-benefit analysis that evaluates the impact of including the feature versus descoping it, and present the options to the sponsor for a decision. This ensures that the business case's expected cost savings are considered and that the sponsor, who owns the budget, makes an informed choice.

Exam trap

The trap is assuming the business analyst should simply escalate or agree to descope without performing analysis; the exam tests whether you recognize the need for a cost-benefit analysis before a scope change decision.

How to eliminate wrong answers

Option A is wrong because escalating to the program manager bypasses the sponsor's authority over budget and scope decisions; the sponsor is the correct stakeholder. Option B is wrong because unilaterally agreeing to descope a critical feature without analyzing the impact on the business case violates change control and could undermine the project's benefits. Option C is wrong because requesting additional budget without first providing a cost-benefit analysis and options is premature and does not give the sponsor the necessary information to decide.

Full explanation →

185

MCQeasy

A project team encounters this error during deployment. Which project document should be updated first?

A.Change log

B.Issue log

C.Lessons learned register

D.Risk register

AnswerB

The issue log records problems, their owners, and resolution status, so a deployment error should be documented there first to track and escalate it. This satisfies the stem's requirement to identify which project document is updated first when an error occurs.

Why this answer

An error during deployment is an issue that has already occurred, so it should be logged in the issue log for tracking and resolution. Option A is wrong because the change log is for approved changes, not for unexpected errors. Option C is wrong because the lessons learned register is updated after the project or phase, not immediately.

Option D is wrong because the risk register is for uncertain events that may occur, but this error has already happened.

Full explanation →

186

MCQmedium

A government IT project is being managed using a predictive lifecycle. The project must comply with numerous regulatory standards, including data privacy and security. The project manager developed a comprehensive quality management plan that includes regular quality audits by an independent team. At the first milestone quality audit, the auditor identifies three non-conformances related to documentation and testing procedures. The project manager is under pressure from the sponsor to stay on schedule. The project manager needs to address the non-conformances effectively while minimizing schedule impact.

A.Immediately halt all work until the non-conformances are resolved.

B.Ignore the non-conformances and proceed with the schedule, as they are minor.

C.Perform root cause analysis and implement corrective actions for the non-conformances.

D.Re-baseline the quality management plan to eliminate the problematic requirements.

AnswerC

Root cause analysis identifies why documentation and testing non-conformances arose, then corrective actions eliminate the source rather than the symptom. This satisfies the regulatory compliance requirement while preventing recurrence, and targeted fixes limit schedule impact better than halting work.

Why this answer

Performing root cause analysis and implementing corrective actions directly addresses the non-conformances while allowing the project to continue, minimizing schedule impact. This approach aligns with quality management principles in predictive projects, where non-conformances must be corrected to meet regulatory and quality standards. It also avoids unnecessary work stoppage and re-baselining, which would have larger schedule and cost implications.

Exam trap

CAPM often tests the tendency to choose extreme actions like halting work or re-baselining, when the correct answer is to apply root cause analysis and corrective actions.

How to eliminate wrong answers

Option A is wrong because halting all work is an overreaction that would severely impact the schedule and is not required for documentation and testing non-conformances. Option B is wrong because ignoring non-conformances violates regulatory compliance and quality standards, and could lead to project failure or legal issues. Option D is wrong because re-baselining the quality management plan to eliminate requirements is unethical and would not address the actual non-conformances; it would also likely violate regulatory standards.

Full explanation →

187

MCQmedium

A business analyst is working on a project to develop a new inventory management system. The project sponsor wants to ensure that all requirements are testable and verifiable. Which characteristic of effective requirements is most directly supported by writing requirements in a structured, consistent format with clear acceptance criteria?

A.Verifiability

B.Traceability

C.Atomicity

D.Prioritization

AnswerA

Verifiability means that a requirement can be tested or measured to confirm it has been met. Writing requirements with clear acceptance criteria and a structured format directly supports verifiability by providing objective conditions for testing. In this scenario, the BA can ensure that each requirement for the inventory system includes specific criteria, such as performance thresholds or functional outcomes, that can be verified during testing.

Why this answer

Verifiability is the characteristic that ensures a requirement can be tested or measured. By writing requirements in a consistent format with clear acceptance criteria, the BA provides the means to verify that the solution meets the requirement. This directly addresses the sponsor's concern for testable and verifiable requirements in the inventory management system project.

Exam trap

The trap here is confusing verifiability with traceability or atomicity, but acceptance criteria specifically enable testing, which is the essence of verifiability.

Full explanation →

188

MCQeasy

A business analyst is defining the scope of a project to develop a new employee onboarding system. The project sponsor asks for a high-level view of the solution's features and their relationships. Which business analysis technique should the business analyst use to provide this view?

A.Use case diagram

B.Feature model

C.Organizational chart

D.Mind map

AnswerB

A feature model is a hierarchical diagram that decomposes a solution into features and sub-features, showing their relationships and optionality. It provides a high-level view of the solution's capabilities, which directly addresses the sponsor's request for features and their relationships.

Why this answer

A feature model is specifically designed to show a solution's features in a hierarchical structure, including mandatory, optional, and alternative features. It gives the sponsor a clear, high-level view of what the system will do and how features relate to each other, which is ideal for scope definition and communication.

Exam trap

The trap here is confusing a use case diagram with a feature model; use cases describe interactions, while feature models describe the decomposition of solution capabilities.

Full explanation →

189

MCQmedium

A project manager is developing the WBS for a large construction project. She has identified the major deliverables and decomposed them into work packages. Which of the following BEST describes the next step in the WBS creation process?

A.Estimate the cost of each work package

B.Assign resources to each work package

C.Decompose work packages into activities

D.Obtain stakeholder approval of the WBS

AnswerC

Work packages represent the lowest WBS level and describe deliverables, not scheduled work. The next step decomposes each work package into activities, which then feed schedule development. This satisfies the stem's request for the step immediately following work package identification.

Why this answer

After the WBS is created down to the work package level, the next step in project planning is to further decompose those work packages into individual activities. This is done in the 'Define Activities' process, which is part of the Planning Process Group and specifically under Project Schedule Management. The WBS focuses on deliverables, while activities represent the work needed to produce those deliverables.

Therefore, decomposing work packages into activities is the logical next step before estimating durations, costs, or resources.

Exam trap

CAPM often tests the distinction between WBS decomposition (deliverable-oriented) and activity definition (work-oriented), so candidates may incorrectly choose cost estimation or resource assignment as the next step, forgetting that activities must be defined first.

How to eliminate wrong answers

Option A is wrong because cost estimation occurs after activities are defined, as you need to know the activities to estimate their costs accurately. Option B is wrong because resource assignment also follows activity definition, since you need to know what activities exist before assigning resources. Option D is wrong because stakeholder approval of the WBS typically happens after the WBS is fully developed, but the question asks for the next step in the creation process, which is decomposition into activities, not approval.

Full explanation →

190

MCQeasy

At the daily stand-up meeting, a team member consistently arrives 10 minutes late, causing the meeting to start late. What is the best agile practice to address this?

A.Impose a fine for lateness to discourage the behavior.

B.Have the team discuss the issue and agree on a new start time, with a commitment to start promptly.

C.Escalate the issue to management to enforce punctuality.

D.Cancel the daily stand-up until the team member arrives on time.

AnswerB

Having the team discuss the lateness and agree a new start time, with a commitment to punctuality, lets the team self-organise and own the solution. This satisfies the stem's constraint by addressing the behaviour collaboratively rather than imposing a manager's fix.

Why this answer

Agile teams are self-organizing and address impediments through open team discussion and collective agreement rather than external enforcement. Having the team discuss the lateness issue and agree on a start time with a commitment to start promptly respects the team's autonomy and addresses the root cause collaboratively. This is consistent with Scrum values of openness, respect, and courage.

Exam trap

CAPM often tests agile mindset vs. traditional management — candidates pick escalation or punitive measures because they seem 'decisive,' but agile always favors team self-organization and collaborative problem-solving.

How to eliminate wrong answers

Option A is wrong because imposing fines is a punitive, command-and-control approach that undermines self-organization and psychological safety, and it is not an agile practice. Option C is wrong because escalating to management to enforce punctuality bypasses the team's ownership of its own process and violates the principle of self-management. Option D is wrong because canceling the Daily Scrum removes a core Scrum event and harms transparency and inspection; the event should be held regardless of individual attendance.

Full explanation →

191

MCQhard

A project is being executed in a highly regulated industry. The quality management plan requires extensive documentation. During a quality audit, the auditor finds that some test results are missing. What is the MOST appropriate action for the project manager?

A.Issue a change request to update the quality management plan

B.Request that the team repeat the tests immediately

C.Update the lessons learned register

D.Log the issue in the issue log and develop a corrective action

AnswerD

Missing test results breach the quality management plan, so the project manager records the nonconformity in the issue log and initiates corrective action to close the documentation gap. This restores compliance with the regulated quality requirements rather than merely reporting or ignoring the defect.

Why this answer

The missing test results represent a nonconformance with the quality management plan, which is a project issue that must be documented and addressed through the Manage Quality process. The correct action is to log the issue in the issue log and develop a corrective action to bring performance back in line with the plan. This follows the PMBOK® Guide's recommended flow: identify the problem, document it, and then determine the appropriate response.

Simply repeating tests or updating the plan without addressing the root cause would not properly resolve the nonconformance.

Exam trap

CAPM often tests the distinction between immediate corrective action and documentation, and candidates may mistakenly choose to repeat tests or update the plan without first logging the issue and analyzing the cause.

How to eliminate wrong answers

Option A is wrong because a change request to update the quality management plan is premature; the plan itself may be adequate, and the problem is that it wasn't followed. Option B is wrong because repeating the tests immediately is a reactive action that doesn't address the underlying process failure or document the issue, and it may not be the most appropriate first step without analyzing the cause. Option C is wrong because updating the lessons learned register is a good practice but is not the immediate action to resolve the current nonconformance; it is typically done at the end of the project or phase.

Full explanation →

192

MCQhard

During requirements elicitation, a business analyst (BA) observes that key stakeholders are reluctant to share information due to a previous project's failure. The BA needs to build trust. Which technique should the BA use to encourage open communication?

A.Facilitate a workshop with ground rules to ensure respectful dialogue.

B.Conduct one-on-one interviews to gather individual perspectives.

C.Distribute a survey to collect anonymous feedback.

D.Organize a brainstorming session to generate ideas freely.

AnswerA

A facilitated workshop with agreed ground rules creates a psychologically safe, structured setting where stakeholders can speak without fear of blame, directly addressing the distrust left by the earlier failed project. This satisfies the need to encourage open communication during requirements elicitation.

Why this answer

Facilitating a workshop with ground rules establishes a structured, respectful environment that directly addresses trust issues. Ground rules create psychological safety by setting clear expectations for behavior, which encourages reluctant stakeholders to share information openly. This technique is specifically designed to rebuild trust in a group setting after a project failure.

Exam trap

PMI often tests the distinction between techniques that gather information (like surveys or interviews) versus those that build trust and collaboration (like facilitated workshops with ground rules) in sensitive stakeholder situations.

How to eliminate wrong answers

Option B is wrong because one-on-one interviews, while useful for gathering individual perspectives, do not actively rebuild group trust or address the collective reluctance stemming from a previous failure. Option C is wrong because distributing an anonymous survey collects feedback without fostering open dialogue or trust-building interaction among stakeholders. Option D is wrong because a brainstorming session, though free-flowing, lacks the structured ground rules needed to manage sensitive dynamics and ensure respectful communication after a trust breakdown.

Full explanation →

193

MCQeasy

A project manager is determining the sequence of activities for a construction project. Which tool is best suited for this purpose?

A.Resource breakdown structure

B.Work breakdown structure

C.Gantt chart

D.Network diagram

AnswerD

A network diagram maps activity dependencies, showing which tasks must precede others and where parallel paths exist. This directly satisfies the stem's requirement to determine sequence, unlike a Gantt chart (which displays duration and schedule) or a work breakdown diagram (which decomposes scope). It exposes the critical path through the logical order of activities.

Why this answer

A network diagram is the best tool for determining the sequence of activities because it visually maps the logical dependencies and order in which project activities must be performed. It explicitly shows predecessor-successor relationships, which are essential for sequencing. Unlike other tools, it directly supports techniques like the critical path method (CPM) and precedence diagramming.

Therefore, it is the correct choice for sequencing activities.

Exam trap

CAPM often tests the confusion between tools that display schedule (Gantt chart) and tools that determine sequence (network diagram), so candidates must remember that sequencing is about dependencies, not time bars.

How to eliminate wrong answers

Option A is wrong because a resource breakdown structure (RBS) categorizes project resources (people, equipment, materials) by type, not by activity sequence. Option B is wrong because a work breakdown structure (WBS) decomposes project deliverables into smaller components, but it does not show the order or dependencies between activities. Option C is wrong because a Gantt chart displays activities over time (schedule), but it does not inherently show logical dependencies or the optimal sequence; it is a output of scheduling, not a sequencing tool.

Full explanation →

194

MCQmedium

You are a business analyst on a project to replace a legacy claims processing system. Executive management wants to understand the expected benefits and costs before authorizing the project. Which document should you prepare to present the justification for the investment?

A.Business case

B.Requirements traceability matrix

C.Project charter

D.Work breakdown structure

AnswerA

A business case is the formal document that justifies initiating a project by comparing expected benefits, costs, risks, and strategic alignment. Executive management uses it to decide whether to authorize funding. It directly addresses the need to evaluate financial viability and expected value before project approval, making it the appropriate deliverable for this scenario.

Why this answer

A business case is the standard artifact for justifying a project investment. It captures the problem or opportunity, expected benefits, cost estimates, risks, and alignment with organizational strategy. Executives rely on it to make an informed go/no-go decision.

The other artifacts serve different purposes: authorizing work, tracing requirements, or decomposing scope, and none replaces the business case for investment justification.

Exam trap

The trap here is confusing the project charter, which authorizes the project, with the business case, which justifies the investment before authorization.

Full explanation →

195

MCQhard

A project manager is assigned to a project that is in the planning phase. The sponsor asks the project manager to include a 10% contingency reserve in the budget. The project manager knows that the project has a high degree of uncertainty. What should the project manager do?

A.Explain that contingency reserves are not allowed in the project budget.

B.Refuse the request because it is unethical.

C.Perform a quantitative risk analysis to determine appropriate contingency reserves.

D.Add the 10% contingency reserve as requested.

AnswerC

Quantitative risk analysis models uncertainty numerically, typically via Monte Carlo simulation, producing a defensible contingency figure rather than an arbitrary 10%. This satisfies the stem's high-uncertainty constraint by deriving the reserve from the project's actual risk exposure and confidence level.

Why this answer

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.

Exam trap

The trap here is that candidates may assume the sponsor's request is always correct or that a fixed percentage is standard practice, but the CAPM exam tests the principle that contingency reserves must be justified by risk analysis, not arbitrary figures.

How to eliminate wrong answers

Option A is wrong because contingency reserves are a standard and allowed component of project budgets, as defined in the PMBOK Guide's cost baseline and budget processes. Option B is wrong because adding a contingency reserve is not inherently unethical; the ethical issue would be if the reserve is misused or not based on risk analysis, but the request itself is not unethical. Option D is wrong because blindly accepting a sponsor's arbitrary 10% without risk analysis violates the project manager's responsibility to base reserves on objective risk data, potentially leading to insufficient or excessive funding.

Full explanation →

196

MCQmedium

A project manager is developing a work breakdown structure (WBS) for a software development project. The team is struggling with defining the lowest-level work packages. Which technique should the project manager use to ensure the WBS is complete and properly decomposed?

A.Decomposition

B.Critical path method

C.Expert judgment

D.Rolling wave planning

AnswerA

Decomposition subdivides project deliverables into progressively smaller, manageable work packages until each can be estimated, scheduled and assigned. It is the specific technique that produces the lowest-level WBS components, resolving the team's difficulty defining adequately sized work packages.

Why this answer

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.

Exam trap

The trap here is that candidates often confuse decomposition with rolling wave planning, thinking that progressive elaboration is the same as breaking down the WBS, but decomposition is a distinct, structured technique applied upfront to create a complete WBS, not a phased planning approach.

How to eliminate wrong answers

Option B is wrong because the critical path method is a schedule network analysis technique used to determine the longest path through the project and calculate float, not for defining WBS work packages. Option C is wrong because expert judgment, while useful for many planning activities, is a general technique for applying expertise and does not provide the structured, step-by-step decomposition process required to ensure completeness at the work package level. Option D is wrong because rolling wave planning is a progressive elaboration technique where near-term work is planned in detail and future work is planned at a higher level; it does not directly address the need to decompose the entire WBS to the lowest level work packages.

Full explanation →

197

MCQeasy

A business analyst has completed elicitation for a customer portal project and now has a long list of raw stakeholder statements. Before the statements can be used as requirements, the analyst must distinguish which are true requirements. Which characteristic must a well-formed requirement exhibit?

A.It must describe a capability or condition the solution needs to satisfy.

B.It must be approved by every stakeholder who attended the elicitation session.

C.It must specify the technology platform on which the capability will be delivered.

D.It must be traceable to a specific line item in the project budget.

AnswerA

A requirement states a capability or condition that the solution must meet to deliver value to stakeholders. This distinguishes genuine requirements from opinions, background information, and design decisions collected during elicitation. Applying this characteristic lets the analyst separate statements that constrain the solution from commentary that merely describes the current environment or a stakeholder preference for the portal project.

Why this answer

The defining test of a requirement is that it expresses a capability or condition the solution must satisfy to deliver value. Raw elicitation notes mix true requirements with opinions, context, and design ideas, so the analyst filters statements through this characteristic. Traceability, unanimous approval, and platform prescription are either governance artifacts or design constraints, not properties that make a statement a requirement.

Exam trap

The trap here is confusing governance or design attributes, such as budget linkage or platform choice, with the fundamental nature of a requirement as a needed capability or condition.

Full explanation →

198

MCQmedium

After a change request is approved, a business analyst must update the requirements documentation. What is the most important step to ensure traceability?

A.Update the requirements traceability matrix

B.Revise the project schedule to reflect the change

C.Communicate the change to the development team

D.Archive the previous version of the requirements document

AnswerA

Updating the requirements traceability matrix directly satisfies the traceability constraint by linking the approved change to its originating requirement, affected deliverables and test cases. The matrix is the designated artefact for recording these relationships, so revising it after approval keeps the audit trail complete and verifiable.

Why this answer

The requirements traceability matrix (RTM) is the artifact that links each requirement to its source, design, code, and test cases, so updating it after an approved change is what preserves end-to-end traceability. Without updating the RTM, the change would be invisible to downstream verification and impact analysis. This is the BA's primary mechanism for maintaining traceability across the requirements lifecycle.

Exam trap

CAPM often tests the confusion between updating the RTM (the traceability artifact) and other valid but non-traceability actions like scheduling, communication, or archiving.

How to eliminate wrong answers

Option B is wrong because revising the schedule addresses timing and effort, not traceability of requirements to their sources and downstream artifacts. Option C is wrong because communicating the change to developers is a coordination step, not a traceability control — it does not record the linkage between the changed requirement and its origin or tests. Option D is wrong because archiving the previous version supports version control and audit history but does not establish traceability links; the RTM is the tool that actually maps requirements to their sources and deliverables.

Full explanation →

199

MCQeasy

A key stakeholder requests a new feature after the project requirements have been formally approved and the scope baseline has been set. What is the first process the project manager should follow?

A.Validate Scope to confirm the new feature

B.Submit a change request through Perform Integrated Change Control

C.Control Scope to update the scope baseline

D.Direct and Manage Project Work to incorporate the feature

AnswerB

Once the scope baseline is approved, new features cannot be added informally; the request must enter Perform Integrated Change Control, where it is documented, evaluated and approved or rejected. This satisfies the governance constraint protecting the approved baseline.

Why this answer

When a change is requested after the scope baseline is set, the formal process is to submit a change request through Perform Integrated Change Control. Option A (Validate Scope) is about formal acceptance of deliverables, not handling changes. Option C (Control Scope) monitors scope status but does not approve changes.

Option D (Direct and Manage Project Work) executes work, not manages change requests.

Full explanation →

200

MCQeasy

In a predictive project, the project manager needs to estimate the cost of each work package with a high level of accuracy. Which technique is most appropriate?

A.Bottom-up estimating

B.Parametric estimating

C.Expert judgment

D.Three-point estimating

AnswerA

Bottom-up estimating aggregates detailed estimates prepared for each work package or activity, producing the greatest accuracy and supporting the work breakdown structure. It suits this scenario because the project manager requires high accuracy at work-package level rather than the rough order-of-magnitude figures of analogous or parametric methods.

Why this answer

Bottom-up estimating involves estimating the cost of individual work packages or activities at the lowest level of the WBS and then aggregating them upward to obtain the total project cost. Because it builds from detailed, granular estimates, it provides the highest level of accuracy and is the preferred technique when the project manager needs precise cost figures for each work package. It is most reliable when the WBS is well-defined and the scope is stable, which is typical in predictive projects.

Exam trap

CAPM often tests the trade-off between accuracy and effort in estimating techniques, so the trap is confusing parametric estimating (fast, less accurate) with bottom-up estimating (slow, most accurate).

How to eliminate wrong answers

Option B is wrong because parametric estimating uses statistical relationships (e.g., cost per square foot) and is faster but less accurate at the individual work-package level. Option C is wrong because expert judgment is a supporting input used across many estimating techniques, not a standalone method that delivers high accuracy per work package. Option D is wrong because three-point estimating (PERT) addresses uncertainty by using optimistic, pessimistic, and most-likely values, but it is typically applied at the activity level and does not by itself guarantee the highest accuracy for each work package the way bottom-up does.

Full explanation →

201

MCQeasy

Which of the following is NOT a purpose of the project charter?

A.Define the detailed project schedule.

B.Identify the project sponsor.

C.Authorize the project manager.

D.Provide high-level project requirements.

AnswerA

The project charter authorises the project and names the project manager, but detailed scheduling belongs to later planning artefacts such as the schedule baseline. Defining the detailed project schedule is therefore not a charter purpose, making it the exception sought.

Why this answer

The project charter is a high-level document that authorizes the project, identifies the sponsor, and provides high-level requirements. It does not include a detailed project schedule; that is developed later in the project planning process group, specifically within the Develop Schedule process. Therefore, option A is correct because defining the detailed project schedule is not a purpose of the project charter.

Exam trap

The trap here is that candidates confuse the high-level milestones listed in the charter with the detailed schedule, leading them to incorrectly think the charter defines the full project timeline, when in fact the detailed schedule is created later in the planning phase.

How to eliminate wrong answers

Option B is wrong because identifying the project sponsor is a key purpose of the project charter; the charter formally names the sponsor who provides authority and resources. Option C is wrong because authorizing the project manager is a primary purpose of the charter, as it grants the PM the authority to apply organizational resources. Option D is wrong because providing high-level project requirements is a standard component of the project charter, which outlines business needs and key deliverables at a summary level, not detailed specifications.

Full explanation →

202

MCQmedium

A project team is working on a software development project. The project manager notices that the team is spending too much time on unplanned work, resulting in delays to the critical path. What technique should the project manager use to reduce unplanned work and improve focus?

A.Apply crashing to the critical path activities.

B.Perform resource leveling to smooth resource usage.

C.Use fast tracking to overlap activities.

D.Implement critical chain project management.

AnswerD

Critical chain project management buffers tasks and removes multitasking, directly reducing unplanned work that delays the critical path. It satisfies the stem's constraint by protecting the schedule through resource-levelled buffers rather than padding individual task estimates.

Why this answer

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.

Exam trap

The trap here is that candidates confuse schedule compression techniques (crashing, fast tracking) with schedule protection techniques, failing to recognize that unplanned work requires a buffer-based approach like CCPM rather than simply accelerating planned activities.

How to eliminate wrong answers

Option A is wrong because crashing adds resources to critical path activities to compress schedule duration, but it does not reduce unplanned work or improve focus—it only accelerates planned tasks. Option B is wrong because resource leveling adjusts start/finish dates to resolve resource over-allocation, but it does not prevent unplanned work or protect the critical path from interruptions. Option C is wrong because fast tracking overlaps sequential activities to shorten the schedule, but it increases risk and rework potential, not reducing unplanned work or improving team focus.

Full explanation →

203

MCQeasy

A Scrum Team is struggling with unclear requirements. The Product Owner wants to ensure the team has a shared understanding of a user story before development begins. Which of the following is the most appropriate technique?

A.Hold a backlog refinement session to discuss and split the user story.

B.Wait until the Sprint starts and let developers ask questions during the Daily Scrum.

C.Ask the Scrum Master to write detailed technical specifications for the story.

D.Conduct a Sprint Review to clarify requirements with stakeholders.

AnswerA

Backlog refinement is the ongoing process of reviewing and updating the Product Backlog, including breaking down large items into smaller, clearer ones. It gives the Product Owner and Developers a shared understanding of the story before Sprint Planning. This directly addresses unclear requirements and helps ensure the team can estimate and implement the story effectively.

Why this answer

Backlog refinement is the Scrum practice for reviewing and updating the Product Backlog, including clarifying and splitting user stories. It provides the shared understanding the team needs before development begins. Sprint Review, Scrum Master-authored specifications, and Daily Scrum discussions occur too late or violate Scrum roles, so they do not adequately address unclear requirements.

Exam trap

The trap here is assuming the Scrum Master should create detailed specifications or that clarification can wait until the Daily Scrum, rather than using backlog refinement to build shared understanding.

Full explanation →

204

MCQhard

A project manager is executing a predictive project with a cost baseline of $500,000. At the end of the third month, the project has completed 40% of the work, and the actual cost incurred is $220,000. The project manager needs to forecast the total cost at completion. Which earned value management (EVM) estimate should the project manager use if the current cost performance is expected to continue?

A.To-complete performance index (TCPI) using the formula (BAC - EV) / (BAC - AC)

B.Estimate to complete (ETC) using the formula BAC - EV

C.Estimate at completion (EAC) using the formula AC + (BAC - EV)

D.Estimate at completion (EAC) using the formula BAC / CPI

AnswerD

The estimate at completion (EAC) using BAC / CPI assumes that the current cost performance will continue at the same rate for the remainder of the project. Here, CPI = EV / AC = (40% of $500,000) / $220,000 = $200,000 / $220,000 ≈ 0.909. EAC = $500,000 / 0.909 ≈ $550,000. This forecast is appropriate when the project manager expects the same cost efficiency trend to persist, making it the correct choice for the scenario.

Why this answer

The correct forecast is the estimate at completion (EAC) calculated as BAC / CPI, because it assumes the current cost performance will continue. With EV = $200,000 and AC = $220,000, the CPI is approximately 0.909, yielding an EAC of about $550,000. This method is used when the project manager believes the existing cost efficiency trend will persist.

Other formulas either assume atypical variances, calculate remaining cost, or measure required performance, none of which forecast total cost under the stated assumption.

Exam trap

The trap here is selecting a formula that assumes atypical variances or calculates the remaining cost instead of the total forecasted cost, even though the scenario states that the current performance is expected to continue.

Full explanation →

205

Multi-Selectmedium

Which TWO are outputs of the Initiating process group?

Select 2 answers

A.Project scope statement

B.Work breakdown structure

C.Stakeholder register

D.Project charter

E.Risk register

AnswersC, D

The stakeholder register is created during Initiating through stakeholder identification and analysis, so it qualifies as an Initiating output. It records each stakeholder's interests, influence and engagement needs, distinguishing it from Planning documents such as the communications management plan.

Why this answer

The Initiating process group produces the project charter (D) via the Develop Project Charter process, which formally authorizes the project and names the project manager; it is the key output that launches the project. It also produces the stakeholder register (C) via the Identify Stakeholders process, which records stakeholder identification, assessment, and classification information. The project scope statement (A) is an output of the Planning process group (Define Scope), not Initiating.

The work breakdown structure (B) is created in Planning (Create WBS). The risk register (E) is also a Planning output (Identify Risks).

Exam trap

CAPM often tests process-group-to-output mapping, tricking candidates into selecting Planning outputs like the scope statement, WBS, or risk register as Initiating outputs.

Full explanation →

206

MCQeasy

You are a business analyst on a project to develop a new online banking portal. The project is using a hybrid approach with both predictive and adaptive elements. The requirements have been documented in a functional specification, but during development, the product owner requests significant changes based on user feedback. The change control board (CCB) is slow to approve changes, causing delays. The project manager wants to minimize rework while still incorporating valuable feedback. As the business analyst, what is the best course of action?

A.Implement a stricter change control process requiring more documentation.

B.Use requirements traceability to evaluate the impact of each change and prioritize accordingly.

C.Freeze the requirements and defer all changes to a future release.

D.Allow the product owner to approve changes directly to speed up the process.

AnswerB

Traceability links each requested change to affected requirements, designs and tests, so the business analyst can quantify rework and dependencies before the CCB decides. This directly satisfies the stem's constraint of minimising rework while still incorporating valuable user feedback.

Why this answer

Requirements traceability allows the business analyst to assess the impact of each requested change on existing requirements, test cases, and deliverables. This enables informed prioritization, minimizing rework while incorporating valuable feedback. Option A (stricter change control) would further slow down the process, contrary to the goal.

Option C (freezing requirements) ignores user feedback and may lead to a product that doesn't meet needs. Option D (allowing the product owner to approve directly) bypasses governance and could introduce uncontrolled changes, causing rework.

Full explanation →

207

MCQeasy

An agile team is using a burndown chart for the first time. After six days of a two-week sprint, the burndown chart shows that the remaining work has increased compared to the previous day. The team is confused. They had completed several tasks, but new tasks were added to the sprint backlog after the sprint started. The product owner says the additions were urgent and necessary. The development team is frustrated because they feel the sprint goal is at risk. The Scrum Master must address this situation. What should the Scrum Master do?

A.Instruct the team to ignore the burndown chart and focus on delivering the original sprint goal

B.Explain to the product owner that the sprint backlog is frozen once the sprint starts and cannot be changed

C.Ask the product owner and team to renegotiate the sprint scope, either removing some planned work or deferring the new work to the next sprint

D.Manually adjust the burndown chart to show the completed tasks and hide the additional work

AnswerC

Scope added mid-sprint inflates remaining work, breaking the burndown and risking the sprint goal. Renegotiating scope with the product owner restores a realistic forecast, either by removing equivalent planned work or deferring the new items to the next sprint.

Why this answer

The Scrum Master should facilitate a negotiation between the product owner and the development team to re-evaluate the sprint backlog. In Scrum, the sprint backlog can be clarified or renegotiated with the product owner, but the sprint goal must remain achievable. By asking the team and product owner to either remove planned work or defer the new tasks, the Scrum Master protects the sprint goal and maintains team focus, which is the core responsibility of the Scrum Master in an agile framework.

Exam trap

The trap here is that candidates often assume the sprint backlog is completely frozen once the sprint starts, but Scrum allows changes as long as the team and product owner agree and the sprint goal remains viable.

How to eliminate wrong answers

Option A is wrong because instructing the team to ignore the burndown chart disregards a key agile metric for tracking progress and transparency; the burndown chart is a tool for visibility, not a distraction. Option B is wrong because the sprint backlog is not frozen; the product owner can influence the backlog, but the team must agree to any changes that affect the sprint goal—this option incorrectly states an absolute rule that contradicts Scrum's flexibility. Option D is wrong because manually adjusting the burndown chart to hide additional work violates the principle of transparency in Scrum and would mislead the team and stakeholders about the true state of the sprint.

Full explanation →

208

MCQmedium

A project team is conducting cost estimation for a project that uses a predictive lifecycle. They have historical data from similar projects. Which estimation technique is MOST appropriate?

A.Three-point estimating

B.Analogous estimating

C.Parametric estimating

D.Bottom-up estimating

AnswerB

Analogous estimating uses historical data from comparable past projects to derive cost figures, which suits a predictive lifecycle with limited detail. It satisfies the stem's constraint of available historical data from similar projects, delivering a quick top-down estimate, though less accurate than bottom-up or parametric methods.

Why this answer

Analogous estimating uses historical data from similar past projects to estimate the current project's cost or duration, which is exactly what the team has available. It is a top-down, expert-judgment-based technique that is fast and inexpensive, making it well suited to predictive lifecycles where scope is relatively stable and comparable projects exist.

Exam trap

The trap is confusing 'historical data from similar projects' (analogous) with 'historical data and a statistical relationship' (parametric); the presence of a unit rate or formula is the tell for parametric.

How to eliminate wrong answers

Option A is wrong because three-point estimating (optimistic/most likely/pessimistic) is used to build a weighted PERT estimate and requires activity-level uncertainty data, not just historical project comparables. Option C is wrong because parametric estimating uses a statistical relationship between historical data and variables (e.g., cost per square foot), which requires a scalable unit rate — not merely 'similar projects.' Option D is wrong because bottom-up estimating aggregates estimates from individual work packages, which is far more detailed and costly than what the scenario implies.

Full explanation →

209

MCQeasy

During the planning phase of a predictive project, the project manager notices that the project schedule does not include all required deliverables. What is the most appropriate action to address this gap?

A.Update the schedule to include the missing deliverables directly.

B.Request a change to the project charter to accommodate the missing deliverables.

C.Review the scope statement and add more resources to the project.

D.Review the work breakdown structure (WBS) to ensure all deliverables are represented.

AnswerD

The WBS decomposes the total project scope into deliverables, so any missing deliverable indicates an incomplete WBS. Reviewing and correcting it ensures every required output is captured before the schedule is baselined, closing the gap at its source rather than patching the schedule.

Why this answer

The WBS decomposes the project scope into deliverables and work packages; if the schedule is missing deliverables, the root cause is likely an incomplete WBS. Reviewing the WBS ensures all deliverables are identified and represented before updating the schedule. This aligns with the PMBOK principle of verifying scope before schedule development.

Exam trap

CAPM often tests the principle that the WBS is the foundation for schedule and cost planning — the trap is jumping to fix the schedule or charter directly instead of tracing the gap back to the WBS.

How to eliminate wrong answers

Option A is wrong because directly updating the schedule without verifying the WBS may perpetuate the gap and bypass proper scope validation. Option B is wrong because the project charter is a high-level authorization document, not the place to add deliverables; changes to deliverables belong in scope planning. Option C is wrong because adding resources does not address missing deliverables — it conflates resource allocation with scope completeness.

Full explanation →

210

MCQmedium

A business analyst is assigned to a project that aims to streamline the supply chain process in a manufacturing company. The project has a tight deadline, and the project sponsor wants to use a proven framework to ensure efficiency. During the initial analysis, the analyst finds that the current process has many manual handoffs and inconsistent data formats. Several cross-functional teams have conflicting priorities. The sponsor asks for a recommendation that balances structure with flexibility. As the business analyst, which approach should you recommend?

A.Adopt a Six Sigma DMAIC approach to reduce defects and standardize processes.

B.Use the BABOK guide as a framework to define business analysis activities and deliverables.

C.Follow the Prince2 methodology for project management and business analysis.

D.Implement a pure Waterfall approach with strict phase gates.

AnswerB

The BABOK guide provides a structured knowledge framework covering elicitation, requirements analysis and stakeholder engagement, letting the analyst define activities and deliverables while adapting techniques to conflicting cross-functional priorities. This satisfies the sponsor's demand for a proven framework that still balances structure with flexibility under a tight deadline.

Why this answer

The BABOK (Business Analysis Body of Knowledge) guide is the definitive framework for business analysis, providing a flexible structure of knowledge areas, tasks, techniques, and competencies that can be tailored to any project context. It directly addresses the analyst's need to define business analysis activities and deliverables while balancing structure with flexibility, as it is methodology-agnostic and can be adapted to tight deadlines and cross-functional conflicts. Unlike Six Sigma, PRINCE2, or Waterfall, BABOK is specifically designed for the business analysis role, making it the most appropriate recommendation for the sponsor.

Exam trap

CAPM often tests the distinction between business analysis frameworks and project management or quality methodologies, trapping candidates who confuse Six Sigma or PRINCE2 with business analysis standards like BABOK.

How to eliminate wrong answers

Option A is wrong because Six Sigma DMAIC is a quality improvement methodology focused on reducing defects and process variation, not a business analysis framework; it would not address conflicting priorities or define analysis deliverables. Option C is wrong because PRINCE2 is a project management methodology, not a business analysis framework, and it does not provide guidance on business analysis tasks such as elicitation, requirements analysis, or solution evaluation. Option D is wrong because a pure Waterfall approach with strict phase gates is a project management lifecycle that lacks the flexibility needed to handle evolving requirements and cross-functional conflicts, and it does not offer business analysis-specific guidance.

Full explanation →

211

MCQhard

A business analyst is performing a cost-benefit analysis for a proposed system upgrade. The upgrade costs $50,000 upfront and saves $15,000 per year in operational costs. The project has a 5-year horizon. What is the payback period in years?

A.5.00 years

B.4.00 years

C.3.33 years

D.0.33 years

AnswerC

Payback period divides the initial outlay by the annual net saving: $50,000 ÷ $15,000 = 3.33 years. The 5-year horizon is irrelevant to this calculation, since payback measures only the time required to recover the upfront investment from cumulative savings.

Why this answer

The payback period is the upfront cost divided by the annual savings: $50,000 ÷ $15,000 = 3.33 years. This is the time required for cumulative savings to equal the initial investment. It is a simple, undiscounted measure that ignores the time value of money and any cash flows beyond the payback point.

Exam trap

The trap is the distractor 0.33, which is the reciprocal of the correct answer — candidates who invert the formula (savings ÷ cost) instead of cost ÷ savings will pick it.

How to eliminate wrong answers

Option A is wrong because 5.00 years is the full project horizon, not the break-even point — the investment is recovered well before the horizon ends. Option B is wrong because 4.00 years would require annual savings of $12,500, not $15,000. Option D is wrong because 0.33 years is the reciprocal of the correct answer (15,000/50,000), which represents the fraction of the investment recovered per year, not the payback period.

Full explanation →

212

MCQhard

During project execution, a stakeholder requests a new feature that was not in the original scope. The project manager determines that the feature can be accommodated without affecting the critical path, but will increase costs. According to the predictive plan-based methodology, what should the project manager do NEXT?

A.Approve the change to improve stakeholder satisfaction

B.Inform the stakeholder that the change cannot be accepted

C.Submit the change request to the change control board

D.Update the project management plan to include the feature

AnswerC

Any scope addition altering cost must pass through integrated change control before work begins. The change control board evaluates, approves or rejects the request and authorises corresponding baseline updates. Proceeding without approval bypasses governance, regardless of critical path impact.

Why this answer

In a predictive (plan-based) methodology, any change to the project scope, schedule, or cost must go through the formal Integrated Change Control process. Since the requested feature was not in the original scope and will increase costs, it constitutes a change request. The project manager's next step is to submit this change request to the Change Control Board (CCB), which is the designated body responsible for reviewing, approving, or rejecting changes that impact project baselines.

The project manager does not have the authority to unilaterally approve changes that affect cost baselines, even if the critical path is unaffected.

Exam trap

CAPM often tests the misconception that a project manager can approve changes that do not affect the critical path or that stakeholder satisfaction justifies bypassing formal change control; the trap is forgetting that any change affecting baselines requires CCB approval.

How to eliminate wrong answers

Option A is wrong because the project manager cannot approve a change that impacts the cost baseline without proper authority; doing so bypasses the Integrated Change Control process and violates governance. Option B is wrong because the project manager should not outright reject the change without evaluation; the correct process is to submit it to the CCB for a decision. Option D is wrong because updating the project management plan to include the feature is premature; changes to the plan can only be made after the change request is approved through the formal change control process.

Full explanation →

213

MCQeasy

A business analyst needs to document the relationships between requirements, design, and test cases. Which artifact is best for this purpose?

A.Use Case Diagram

B.Work Breakdown Structure

C.Business Requirements Document

D.Requirements Traceability Matrix

AnswerD

A Requirements Traceability Matrix (RTM) is a formal document (often a table) that links each requirement to its source, design specification, test case, and verification status, making it the ideal artifact for tracking relationships throughout the project lifecycle.

Why this answer

A Requirements Traceability Matrix (RTM) is specifically designed to map requirements to design elements, test cases, and other artifacts, ensuring bidirectional traceability. It documents relationships and helps verify that all requirements are covered by tests and design. This directly matches the business analyst's need.

Exam trap

CAPM often tests confusion between documents that capture requirements (BRD) and the matrix that traces them — candidates may pick BRD thinking it covers traceability, but only the RTM provides the mapping.

How to eliminate wrong answers

Option A is wrong because a Use Case Diagram models interactions between actors and a system, not traceability between requirements, design, and tests. Option B is wrong because a Work Breakdown Structure decomposes project deliverables, not requirement relationships. Option C is wrong because a Business Requirements Document captures requirements but does not provide the traceability mapping across design and test cases.

Full explanation →

214

MCQhard

During a requirements workshop, two key stakeholders disagree on a critical requirement. The project manager asks the business analyst to facilitate a resolution. Which approach is most effective?

A.Ask the project sponsor to decide.

B.Document both requirements and proceed with both.

C.Hold a vote among all stakeholders.

D.Use a prioritization matrix to evaluate trade-offs.

AnswerD

A prioritisation matrix scores competing requirements against agreed criteria such as value, cost and risk, exposing trade-offs objectively. This lets the two stakeholders see which requirement delivers most benefit, resolving their disagreement on evidence rather than opinion or escalation.

Why this answer

A prioritization matrix enables objective comparison of requirements based on predefined criteria such as value, cost, and urgency, facilitating a data-driven consensus. Option A is wrong: asking the sponsor to decide bypasses stakeholder collaboration and may not address the underlying disagreement. Option B is wrong: proceeding with both requirements can lead to scope creep and resource conflicts.

Option C is wrong: a vote may not resolve deep disagreements and can alienate minority stakeholders.

Full explanation →

215

MCQmedium

During the project kickoff meeting, a key stakeholder expresses concerns about the project scope. What should the project manager do first?

A.Proceed as planned since the scope was already approved.

B.Review the requirements documentation with the stakeholder.

C.Update the project charter to reflect the stakeholder's concerns.

D.Escalate the issue to the project sponsor.

AnswerB

Reviewing the requirements documentation with the stakeholder clarifies what is actually in scope before any change is considered. This addresses the concern at its source, satisfying the need to understand the stakeholder's specific issue before deciding whether scope adjustment is warranted.

Why this answer

When a stakeholder raises scope concerns at kickoff, the PM should first understand the concern by reviewing the requirements documentation with the stakeholder. This clarifies what was agreed, identifies any misunderstanding, and determines whether a formal change is warranted. It is a collaborative, information-gathering step before any escalation or change.

Exam trap

CAPM often tests the 'escalate first' trap — candidates pick 'escalate to the sponsor' because it sounds decisive, but PMI methodology requires the PM to investigate and attempt resolution before escalating.

How to eliminate wrong answers

Option A is wrong because proceeding as planned ignores a legitimate stakeholder concern and risks building the wrong product — PMs must engage stakeholders, not dismiss them. Option C is wrong because the project charter is a high-level authorization document, not a place to record detailed scope concerns; updating it is inappropriate and premature. Option D is wrong because escalation to the sponsor should occur only after the PM has investigated the issue and determined it cannot be resolved at the project level — escalating first violates the 'assess before escalate' principle.

Full explanation →

216

MCQhard

During a Scrum sprint, the development team discovers that a critical dependency on another team's API cannot be resolved until the next sprint. The product owner insists on delivering the current sprint goal without adjusting scope. The team is struggling to meet the definition of done. What should the Scrum Master do first?

A.Order the team to work overtime to complete the remaining work

B.Ignore the dependency and ask the team to do their best

C.Escalate the issue to the program manager for resolution

D.Facilitate a discussion between the product owner and team to renegotiate the sprint goal

AnswerD

The dependency cannot be resolved until the next sprint, so the definition of done is unattainable within the current goal. Facilitating product owner and team discussion to renegotiate the sprint goal addresses the impediment collaboratively, which is the Scrum Master's servant-leadership responsibility before escalation.

Why this answer

The Scrum Master's first action should be to facilitate a discussion between the product owner and the development team to renegotiate the sprint goal, because the dependency cannot be resolved within the sprint. The Scrum Master serves the team by removing impediments and fostering collaboration, not by dictating or escalating prematurely. Re negotiating the sprint goal with the product owner is the appropriate agile response to a significant impediment.

Exam trap

CAPM often tests the Scrum Master's role by offering escalation or overtime as quick fixes, catching candidates who forget that facilitation and collaboration come before escalation in agile frameworks.

How to eliminate wrong answers

Option A is wrong because ordering overtime is a command-and-control approach that violates agile principles and ignores the root cause (unresolvable dependency). Option B is wrong because ignoring the dependency and hoping for the best is irresponsible and does not address the impediment. Option C is wrong because escalating to the program manager should be a last resort after the team and product owner have attempted to resolve the issue within the Scrum framework.

Full explanation →

217

MCQmedium

Refer to the exhibit. The team wants to pull a new item into In Progress. What should they do first?

A.Ignore the WIP limit and pull the item.

B.Move an item from In Progress to Done.

C.Increase the WIP limit for In Progress.

D.Add the item to To Do.

AnswerB

Kanban is a pull system: a new card may enter In Progress only when capacity frees up. Since the column sits at its WIP limit, the team must first complete an existing item and move it to Done, creating the slot.

Why this answer

In a Kanban system, WIP limits are constraints that must be respected — the team cannot simply pull a new item into In Progress when the column is already at its limit. The correct first action is to finish existing work by moving an item from In Progress to Done, which frees a slot and allows the new item to be pulled. This preserves flow, exposes bottlenecks, and honors the pull-based discipline central to Kanban.

Exam trap

CAPM often tests the misconception that WIP limits are optional guidelines that can be overridden when urgency strikes, when in fact they are a disciplined constraint whose violation undermines the entire Kanban method.

How to eliminate wrong answers

Option A is wrong because ignoring the WIP limit defeats the purpose of Kanban, hides bottlenecks, and leads to multitasking and reduced throughput. Option C is wrong because raising the WIP limit to accommodate new work is a policy change that should be deliberate and data-driven, not a reflexive workaround — and it does not address the underlying capacity issue. Option D is wrong because adding the item to To Do does not free capacity in In Progress; the item would still be blocked from being pulled until a slot opens.

Full explanation →

218

MCQmedium

A project is in the execution phase. The earned value analysis shows a Cost Performance Index (CPI) of 0.8 and a Schedule Performance Index (SPI) of 0.9. What is the best interpretation of these metrics?

A.The project is over budget and behind schedule.

B.The project is under budget but behind schedule.

C.The project is over budget but ahead of schedule.

D.The project is under budget and ahead of schedule.

AnswerA

A CPI below 1.0 means earned value is less than actual cost, so the project is spending more than planned and is over budget. An SPI below 1.0 means earned value lags planned value, so the project is behind schedule.

Why this answer

CPI is calculated as EV/AC, and SPI as EV/PV. A CPI of 0.8 means the project is earning only 80 cents of value for every dollar spent, indicating it is over budget. An SPI of 0.9 means the project is progressing at 90% of the planned schedule rate, indicating it is behind schedule.

Therefore, the project is both over budget and behind schedule.

Exam trap

The trap is misreading the direction of the indices — candidates sometimes think CPI < 1 means under budget or SPI < 1 means ahead of schedule, but both below 1.0 are unfavorable.

How to eliminate wrong answers

Option B is wrong because a CPI below 1.0 indicates over budget, not under budget — under budget would require CPI > 1.0. Option C is wrong because an SPI below 1.0 indicates behind schedule, not ahead of schedule — ahead of schedule would require SPI > 1.0. Option D is wrong because both indices are below 1.0, so the project cannot be under budget and ahead of schedule; that would require CPI > 1.0 and SPI > 1.0.

Full explanation →

219

MCQhard

In a predictive project, the project sponsor requests a scope change that will significantly increase the project cost. The project manager should FIRST:

A.Reject the change as it impacts budget

B.Evaluate the impact of the change on the project constraints

C.Update the project charter

D.Implement the change immediately

AnswerB

Assessing the change's effect on scope, schedule, cost, and risk before any decision gives the sponsor and change control board the data needed to approve, reject, or defer. This satisfies the predictive constraint of controlling changes through integrated change control.

Why this answer

When a scope change is requested, the project manager must first evaluate the impact on project constraints (cost, schedule, quality, etc.) before proceeding. Updating the charter or rejecting the change without evaluation is premature.

Full explanation →

220

MCQmedium

An agile team is using Extreme Programming (XP). A developer wants to refactor a complex module but is concerned about breaking existing functionality. Which XP practice should the developer rely on to safely make changes?

A.Continuous Integration

B.Test-Driven Development

C.Collective Code Ownership

D.Pair Programming

AnswerB

Test-Driven Development (TDD) requires writing automated tests before writing the code. These tests form a safety net that verifies behavior remains correct during refactoring. In XP, TDD is a core practice that enables developers to improve design confidently. By running the tests after each change, the developer can detect regressions immediately and refactor safely.

Why this answer

Test-Driven Development provides an automated test suite that acts as a safety net, allowing developers to refactor with confidence. Continuous Integration, Pair Programming, and Collective Code Ownership support quality and collaboration but do not by themselves verify that refactoring preserved existing behavior. TDD directly addresses the risk of breaking functionality.

Exam trap

The trap here is choosing a collaborative or integration practice like Pair Programming or Continuous Integration when the specific need is a regression safety net for refactoring.

Full explanation →

221

Multi-Selectmedium

A BA is prioritizing a large number of requirements. Which TWO techniques are best suited for this scenario?

Select 2 answers

A.Benchmarking

B.Focus group

C.Kano model

D.MoSCoW analysis

E.Observation

AnswersC, D

The Kano model classifies requirements by how their presence affects satisfaction: basic, performance, delighter, indifferent and reverse. With a large backlog, it identifies which requirements genuinely drive customer satisfaction, letting the BA prioritise by value impact rather than by stakeholder volume alone.

Why this answer

The Kano model (C) is correct because it classifies requirements by their effect on customer satisfaction (must-be, performance, attractive, indifferent, reverse), which directly supports prioritization by revealing which features deliver the greatest satisfaction impact. MoSCoW analysis (D) is correct because it sorts requirements into Must have, Should have, Could have, and Won't have categories, giving a clear, stakeholder-agreed ranking for large requirement backlogs. Benchmarking (A) is not a prioritization technique; it compares organizational practices or performance against competitors or best-in-class standards.

A focus group (B) is an elicitation technique that gathers qualitative feedback from selected participants, not a method for ranking requirements. Observation (E) is also an elicitation technique used to watch users perform tasks and uncover tacit requirements, not to prioritize them.

Exam trap

CAPM often tests the confusion between elicitation techniques (focus groups, observation) and prioritization techniques (Kano, MoSCoW), catching candidates who pick a data-gathering tool for a ranking task.

Full explanation →

222

MCQeasy

A project manager has just been assigned to lead a new product launch. Before detailed planning can begin, the sponsor asks what formal document authorizes the project and gives the project manager authority to apply organizational resources. Which document should the project manager reference?

A.The stakeholder engagement plan

B.The project charter

C.The project management plan

D.The benefits management plan

AnswerB

The project charter formally authorizes the existence of the project and provides the project manager with the authority to apply organizational resources to project activities. It is typically issued by the sponsor or initiating entity and names the project manager. Because the scenario asks what authorizes the project and empowers the manager before planning, the charter is the document that satisfies both conditions.

Why this answer

The project charter is the document that formally authorizes the project and empowers the project manager to apply organizational resources. It is created during initiation, before the project management plan and its subsidiary plans are developed. The benefits management plan informs the charter but does not authorize the project, and planning documents such as the stakeholder engagement plan come later.

Exam trap

The trap here is confusing the document that authorizes the project with the plan that describes how the project will be managed.

Full explanation →

223

Multi-Selectmedium

Which THREE of the following are components typically included in a business case?

Select 3 answers

A.Stakeholder Register

B.Cost-Benefit Analysis

C.Work Breakdown Structure

D.Risk Assessment

E.Executive Summary

AnswersB, D, E

Cost-benefit analysis quantifies expected financial returns against projected outlays, directly satisfying the business case's need to justify investment viability. It compares total costs with anticipated benefits, enabling stakeholders to assess whether the initiative delivers sufficient value. This financial comparison is a standard business case component, alongside expected outcomes and risks.

Why this answer

A business case typically includes an Executive Summary (E), which concisely presents the problem, proposed solution, and recommendation to decision-makers at the top of the document. It also includes a Cost-Benefit Analysis (B), which quantifies expected costs against projected benefits (e.g., ROI, NPV, payback period) to justify the investment. A Risk Assessment (D) is also standard, identifying potential risks, their likelihood and impact, and mitigation strategies that could affect the initiative's viability.

By contrast, a Stakeholder Register (A) is a project stakeholder management artifact produced during project initiation, not a core business case component, and a Work Breakdown Structure (C) is a scope decomposition tool created during project planning, so neither belongs in the business case itself.

Exam trap

CAPM often tests the boundary between pre-project artifacts (business case, benefits management plan) and project artifacts (stakeholder register, WBS) — candidates pick WBS or stakeholder register because they sound 'project-y' without checking which phase produces them.

Full explanation →

224

MCQeasy

A startup is adopting Scrum for the first time. During the Sprint Review, stakeholders request many changes to the product increment. What is the best way for the Scrum Master to handle this?

A.Let the Development Team decide which changes to implement immediately.

B.Add the changes to the current Sprint Backlog immediately.

C.Ask the Product Owner to add the changes to the Product Backlog for prioritization in future Sprints.

D.Ignore the feedback since the Sprint is complete.

AnswerC

New requests during Sprint Review are product backlog items, not scope for the current Sprint. The Product Owner alone orders and prioritises the backlog, so routing changes there preserves the Sprint's fixed goal while allowing stakeholders' input to be evaluated for future Sprints.

Why this answer

In Scrum, the Sprint Review is a time for stakeholders to inspect the increment and provide feedback, but changes cannot be made to the current Sprint as the Sprint Goal and scope are fixed. The Product Owner is responsible for managing the Product Backlog, so the best action is to capture these change requests and have the Product Owner add them to the Product Backlog for future prioritization. This ensures the Development Team remains focused on the current Sprint Goal and that changes are evaluated against business value and priority in upcoming Sprints.

Exam trap

The trap here is that candidates confuse the Sprint Review with a mid-Sprint change opportunity, thinking stakeholder feedback must be acted on immediately, rather than understanding that the Product Backlog is the proper channel for all new requirements.

How to eliminate wrong answers

Option A is wrong because the Development Team should not decide on implementing changes immediately; they are focused on delivering the current Sprint Goal, and unplanned changes disrupt the Sprint Backlog and violate the Sprint's timebox. Option B is wrong because adding changes to the current Sprint Backlog mid-Sprint violates the Scrum principle of a fixed Sprint Backlog and can destabilize the Sprint Goal; changes should only be introduced if the Sprint Goal is not threatened, and even then, only the Product Owner can cancel the Sprint. Option D is wrong because ignoring stakeholder feedback contradicts the inspect-and-adapt principle of Scrum; feedback is valuable for future Sprints and should be captured, not discarded.

Full explanation →

225

MCQmedium

A business analyst is managing requirements for a software upgrade project. The project sponsor wants to ensure that every requirement can be traced back to a business need. What is the primary purpose of requirements traceability?

A.To ensure each requirement meets a business need

B.To document system architecture

C.To assign requirements to team members

D.To estimate project costs

AnswerA

Traceability links each requirement backwards to its originating business need and stakeholder, confirming that no requirement exists without justification. This directly satisfies the sponsor's constraint that every requirement be traceable to a business need, exposing gaps or gold-plating during scope validation.

Why this answer

Requirements traceability ensures that each requirement is linked to a business need, helping to validate scope, manage changes, and confirm value. It also helps in identifying the impact of changes.

Full explanation →

Certified Associate in Project Management CAPM (CAPM) — Questions 151–225