BUSINESS-ANALYST practice question 32 of 35

Over the past month, a business analyst (BA) has worked with various stakeholders at Cloud Kicks to document requirements for an upcoming Tableau implementation. A stakeholder suggested a revision to the requirements. The BA sent the updated requirements to the stakeholders and they signed off. Where should the BA track this milestone?

Full set: 310 questions
Answer options
A: Statement of work
B: Change log Correct answer
C: Sprint plan
Correct Answer:
B. Change log
Explanation

A change log is a formal document used in project management to track all changes made to project requirements after the baseline has been established. Since a stakeholder suggested a revision to already documented requirements and this change was formally approved (signed off), the change log is the appropriate artifact to record this event. It provides an audit trail of what was changed, why, by whom, and when it was approved, which is a critical milestone in the change control process.

Why Incorrect

A. Statement of work: This document defines the initial project scope and deliverables; it is not used for tracking ongoing changes to requirements during the project lifecycle.
C. Sprint plan: This outlines the work to be performed in a specific sprint. While the change might be included in a sprint, the plan itself doesn't track the history of the change request and its sign-off.

References

1. Salesforce Trailhead, Business Analyst Best Practices, "Manage Stakeholder Collaboration" module. This module discusses the importance of managing changes and gaining alignment, for which a change log is a standard tool.

2. International Institute of Business Analysis (IIBA), A Guide to the Business Analysis Body of Knowledge (BABOK Guide) v3, Section 5.5: "Define Change Strategy". This section details the processes for managing and tracking changes to requirements, which aligns with the use of a change log.

Scroll to Top