Business Analysis Planning and Monitoring

Planning the BA approach, stakeholder engagement, governance, information management, and performance improvements.

5 minutes 5 Questions

Business Analysis Planning and Monitoring is a core knowledge area in the Certified Business Analysis Professional (CBAP) framework that encompasses the activities required to coordinate and oversee business analysis efforts throughout a project or initiative. This discipline ensures that business …

Concepts covered
Plan Business Analysis ApproachBA Activity Planning and TimingPlan Stakeholder EngagementStakeholder Collaboration and Communication NeedsDecision-Making and Change Control ProcessesApproval and Sign-Off ProcessesRequirements Traceability and LineageIdentify BA Performance ImprovementsRoot Cause Analysis of BA Performance IssuesPredictive vs Adaptive Planning ApproachesComplexity and Risk Assessment for BAStakeholder Analysis and ClassificationPlan Business Analysis GovernanceRequirements Prioritization ApproachPlan BA Information ManagementRequirements Reuse and Repository ManagementBA Performance Metrics and Measures
Test mode:
Start practice test

CBAP - Business Analysis Planning and Monitoring Example Questions

Test your knowledge of Business Analysis Planning and Monitoring

Question 1

A business analyst has categorized stakeholders for an ERP implementation using a salience model. One stakeholder group possesses legitimacy and urgency but lacks power. Another group has power and legitimacy but no urgency. The project sponsor asks the analyst to justify which group should receive more frequent communication and engagement. Which evaluation best supports prioritizing the group with power and legitimacy?

Correct Answer: Dominant stakeholders with power and legitimacy hold sustained influence and can escalate to definitive status if urgency emerges, warranting proactive engagement

In Mitchell's Salience Model, stakeholders possessing both power and legitimacy are classified as Dominant stakeholders, and they warrant proactive engagement because they hold sustained organizational influence and can quickly become Definitive stakeholders (highest priority) if urgency arises, making it strategically wise to maintain strong communication with them.

One option correctly identifies the dependent stakeholder classification but incorrectly argues they should be higher priority; dependent stakeholders lack power and rely on others to act on their behalf. Another option incorrectly attributes urgency to dominant stakeholders, which contradicts the scenario stating they lack urgency. Another option misclassifies them as dormant; dormant stakeholders possess only power, not both power and legitimacy.

Key concept tested: Mitchell's Stakeholder Salience Model classifications and engagement prioritization.

Question 2

A team is building a new HR system and has completed documenting business requirements, stakeholder requirements, and solution requirements. The project sponsor asks the business analyst to ensure every business requirement can be traced to at least one solution requirement. Which technique should the business analyst apply to fulfill this request?

Correct Answer: Create a traceability matrix mapping each business requirement to its corresponding solution requirements

A traceability matrix is the standard technique used to map relationships between different levels of requirements, ensuring that every business requirement is addressed by at least one solution requirement and enabling forward and backward tracing.

A lineage diagram showing chronological evolution is not a recognized BA technique for verifying requirement coverage. Grouping requirements by functional area into a package organizes them but does not establish or verify linkages between requirement levels. A coverage analysis linking solution requirements to test cases addresses testing coverage, not the upstream tracing from business requirements to solution requirements that the sponsor requested.

Key concept tested: requirements traceability and the use of a traceability matrix within the Trace Requirements task.

Question 3

Which type of traceability links a requirement back to its origin or source?

Correct Answer: Backward traceability connects requirements to their originating sources such as stakeholder needs or business objectives

Backward traceability (also called derive-from traceability) links a requirement back to its origin or source, such as stakeholder needs, business objectives, or higher-level requirements from which it was derived, allowing analysts to understand why a requirement exists.

Forward traceability links requirements to downstream artifacts like design, test cases, or deliverables, not back to originating sources. Vertical traceability incorrectly describes connections at the same level of abstraction, when it actually refers to tracing across different levels of the requirements hierarchy. Lateral traceability is not a standard traceability classification in the BABOK framework.

Key concept tested: understanding the direction and purpose of requirements traceability types in the BABOK.

More Business Analysis Planning and Monitoring questions
456 questions (total)
Practice 100 questions
One session at a time, always new questions