CAPM Business Analysis Frameworks — 15 Questions

Question 1

A project manager is leading a software development project. The business analyst has identified that the current requirements gathering process does not align with the enterprise's business analysis framework. The team is experiencing frequent scope changes and rework. What should the project manager do first to address this issue?

Accepted Answer

Review the enterprise's business analysis framework and adjust the requirements process to comply with it.. Option C is correct because the project manager must first ensure the requirements gathering process aligns with the enterprise's business analysis framework. This alignment is a foundational step to reduce scope changes and rework, as the framework defines standard practices, templates, and governance for requirements management. Without compliance, any change control or documentation updates will be ineffective because the underlying process itself is non-conforming.

Answer

Immediately implement a change control process to manage scope changes.

Answer

Train the business analyst on the project's requirements gathering techniques.

Answer

Update the requirements documentation to include a traceability matrix.

Question 2

During the planning phase of a project, the business analyst needs to define the solution scope. Which business analysis framework artifact is most appropriate to document the high-level boundaries and capabilities of the solution?

Accepted Answer

Context diagram. The context diagram is the most appropriate artifact for documenting the high-level boundaries and capabilities of a solution during the planning phase. It visually represents the system as a single process, its external entities (actors), and the data flows between them, clearly defining what is inside and outside the solution scope. This aligns with the business analyst's need to capture the solution's scope boundaries without detailing internal processes.

Answer

User stories

Answer

Business case

Answer

Work breakdown structure (WBS)

Question 3

A business analyst is facilitating a requirements workshop for a new regulatory compliance system. Stakeholders disagree on the priority of two requirements: Requirement X (must meet legal deadline) and Requirement Y (improves user efficiency). The project sponsor insists on including both, but the timeline is tight. What is the best approach to resolve this conflict?

Accepted Answer

Conduct a feasibility study to evaluate trade-offs and present options.. Option D is correct because conducting a feasibility study allows the business analyst to objectively evaluate trade-offs between Requirement X (regulatory compliance) and Requirement Y (user efficiency) within the tight timeline. This approach provides data-driven options (e.g., scope adjustments, resource reallocation) to the project sponsor, enabling an informed decision without prematurely sacrificing either requirement or escalating unnecessarily. It aligns with the BABOK® Guide's principle of collaborative decision-making through analysis rather than assumption.

Answer

Prioritize Requirement X because it is regulatory, and defer Requirement Y.

Answer

Escalate to the steering committee for a decision.

Answer

Include both requirements and extend the project deadline.

Question 4

A business analyst is using a business analysis framework to identify stakeholders. Which technique is most effective for ensuring all affected parties are considered?

Accepted Answer

Creating a stakeholder map and validating with experts. Option C is correct because stakeholder mapping, when validated with experts, systematically identifies all affected parties by visually representing relationships, influence, and impact. This technique leverages expert judgment to cross-check the map against organizational knowledge, ensuring no stakeholder group is overlooked. It is more comprehensive than ad-hoc methods because it follows a structured framework (e.g., PMI's stakeholder identification process) and incorporates validation to fill gaps.

Answer

Brainstorming with the project team

Answer

Conducting one-on-one interviews with known stakeholders

Answer

Distributing a questionnaire to the organization

Question 5

During requirements validation, the business analyst discovers that a key requirement conflicts with an existing system constraint. The project manager wants to proceed with the requirement as-is to meet customer expectations. What should the business analyst do?

Accepted Answer

Document the conflict, analyze trade-offs, and facilitate a decision with stakeholders.. Option B is correct because the business analyst's role in requirements validation includes documenting conflicts, analyzing trade-offs (e.g., cost, schedule, technical feasibility), and facilitating a decision among stakeholders. This aligns with the BABOK® Guide's requirement for collaborative decision-making, ensuring that the project manager's desire to meet customer expectations is balanced against the system constraint through an informed, consensus-driven process.

Answer

Escalate directly to the project sponsor.

Answer

Modify the requirement to avoid the constraint without informing stakeholders.

Answer

Accept the project manager's decision and proceed.

Question 6

A business analyst is evaluating the performance of a business analysis framework after project completion. Which metric best indicates the effectiveness of the requirements management process?

Accepted Answer

Number of requirements defects found post-implementation. The number of requirements defects found post-implementation directly reflects the quality and completeness of the requirements management process. A high number of defects indicates that requirements were poorly defined, ambiguous, or missed during elicitation and validation, making it the most relevant metric for evaluating the effectiveness of that process.

Answer

Schedule variance

Answer

Number of requirements traced to test cases

Answer

Stakeholder satisfaction survey results

Question 7

A business analyst is selecting a business analysis framework for a small project with limited budget. Which framework characteristic is most important to consider?

Accepted Answer

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

Answer

Alignment with industry standards

Answer

Comprehensiveness to cover all possible scenarios

Answer

Integration with existing project management tools

Question 8

Which TWO of the following are core components of a business analysis framework according to PMI standards?

Accepted Answer

Business analysis planning and monitoring. According to PMI's Business Analysis for Practitioners: A Practice Guide, the core components of a business analysis framework are the five domains: Business Analysis Planning and Monitoring, Elicitation and Collaboration, Requirements Life Cycle Management, Strategy Analysis, and Requirements Analysis and Design Definition. Option A is correct because Business Analysis Planning and Monitoring is the domain that defines how business analysis activities will be executed, including stakeholder analysis, planning deliverables, and establishing governance. Option C is correct because Requirements Life Cycle Management covers the management of requirements from creation through retirement, including traceability, prioritization, and change control.

Answer

Stakeholder engagement

Answer

Procurement management

Answer

Risk management

Question 9

Which THREE of the following are techniques commonly used in business analysis frameworks to elicit requirements?

Accepted Answer

Prototyping. Prototyping is a technique used in business analysis to elicit requirements by creating a working model of the product or system. This allows stakeholders to interact with a tangible representation, clarify their needs, and provide feedback early in the process, reducing misunderstandings and rework.

Answer

SWOT analysis

Answer

Critical path method

Question 10

You are a business analyst for a large retail company implementing a new inventory management system. The project uses a waterfall business analysis framework. During the requirements phase, you have completed stakeholder analysis, conducted interviews, and documented functional requirements. Now, during requirements validation, the warehouse manager (a key stakeholder) states that the system must support real-time inventory updates from handheld scanners, a requirement not previously mentioned. The project manager is concerned because this requirement could impact the budget and schedule, and the design phase is scheduled to begin next week. You have a requirements prioritization meeting tomorrow. The warehouse manager insists this is critical for operations. The project sponsor expects all requirements to be finalized before design. What is the best course of action?

Accepted Answer

Analyze the impact of the requirement on cost, schedule, and scope, and present options at the prioritization meeting.. Option C is correct because, as a business analyst following a waterfall framework, you must analyze the impact of a new requirement on cost, schedule, and scope before making decisions. Presenting this analysis at the prioritization meeting allows stakeholders to make an informed trade-off decision, aligning with the project sponsor's expectation that requirements are finalized before design begins. This approach maintains the integrity of the requirements validation process without prematurely escalating or rejecting the requirement.

Answer

Immediately escalate to the project sponsor to decide whether to include the requirement.

Answer

Add the requirement to the requirements document and adjust the project plan accordingly.

Answer

Reject the requirement because it was not identified during elicitation and will delay the project.

Question 11

During the requirements elicitation for a new software system, the business analyst (BA) conducts a series of interviews with stakeholders. After the first interview, the BA realizes that the questions are too technical and the stakeholders are struggling to provide clear requirements. What should the BA do to improve the elicitation process?

Accepted Answer

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

Answer

Continue with the same questions but provide a glossary of technical terms.

Answer

Replace interviews with a review of existing documentation.

Answer

Reduce the number of stakeholders to only those with technical backgrounds.

Question 12

A business analyst is facilitating a workshop to define the scope of a new customer relationship management (CRM) system. The project manager insists on including a feature that automates email campaigns, but the BA has identified that this feature is outside the agreed budget and timeline. The product owner supports the feature because it was requested by a key customer. What should the BA do first?

Accepted Answer

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

Answer

Reject the feature because it exceeds the budget.

Answer

Add the feature to the backlog but flag it as out of scope.

Answer

Request a budget increase from the project sponsor.

Question 13

A business analyst is creating a requirements traceability matrix (RTM) for a project. Which of the following is the primary purpose of an RTM?

Accepted Answer

To track requirements from identification through delivery and testing.. The primary purpose of a Requirements Traceability Matrix (RTM) is to link each requirement from its origin through the entire project lifecycle, including design, development, testing, and delivery. Option C correctly identifies this end-to-end traceability function, which ensures that every requirement is accounted for and validated against test cases and deliverables.

Answer

To document the final version of requirements after project closure.

Answer

To assign requirements to specific team members.

Answer

To estimate the cost of each requirement.

Question 14

During a requirements validation session, the project sponsor questions whether a particular requirement aligns with the business case. The business analyst recalls that the requirement originated from a regulatory compliance need. What should the BA do to resolve the concern?

Accepted Answer

Show the sponsor the traceability link to the regulatory requirement.. Option B is correct because the business analyst (BA) should use the traceability link to demonstrate how the requirement directly maps to a regulatory compliance need, which is a valid justification within the business case. Traceability ensures that every requirement is linked back to a business objective or external driver, such as a regulation, and provides objective evidence to resolve the sponsor's concern without subjective debate.

Answer

Ignore the sponsor's comment and proceed with the requirement as documented.

Answer

Remove the requirement to address the sponsor's concern.

Answer

Postpone the discussion until the next stakeholder meeting.

Question 15

A business analyst is using a requirements management tool to store and track requirements. During a review, the BA notices that two stakeholders have conflicting requirements for the same system feature. What is the best approach to resolve this conflict?

Accepted Answer

Facilitate a meeting with both stakeholders to discuss and reach a consensus.. Option C is correct because the business analyst's role includes facilitating stakeholder collaboration to resolve conflicts, ensuring that requirements are aligned with business needs. Using a requirements management tool to track conflicting requirements is insufficient; the BA must actively mediate a discussion to reach consensus, as this is a core competency in business analysis frameworks like the BABOK.

Answer

Choose the requirement from the stakeholder with higher authority.

Answer

Document both requirements and let the development team decide.

Answer

Escalate the conflict to the project sponsor immediately.