After stakeholders formally signed off on requirements, the business analyst (BA) received numerous emails requesting changes to Salesforce during uses acceptance testing (UAT). The BA quickly became

The correct answer is A. Change request log. A change request log is a formal tracking document used to capture, organize, assess, and prioritize requests for changes that arise after requirements have been baselined (signed off). It records each request's description, requester, priority, impact, and status - giving the BA

Document

Question

After stakeholders formally signed off on requirements, the business analyst (BA) received numerous emails requesting changes to Salesforce during uses acceptance testing (UAT). The BA quickly became overwhelmed by the requests and needs a way to organize and peritonitis them. What should the BA use to help them organize these requests?

Options

AChange request log
BScope statement specification
CGap analysis document

How the community answered

(62 responses)

A
76% (47)
B
8% (5)
C
16% (10)

Explanation

A change request log is a formal tracking document used to capture, organize, assess, and prioritize requests for changes that arise after requirements have been baselined (signed off). It records each request's description, requester, priority, impact, and status - giving the BA a structured way to manage scope changes without losing track of anything. A scope statement (B) defines the project boundaries but is not a tracking tool for incoming requests. A gap analysis (C) compares current vs. desired state during discovery; it is not designed to manage post-sign-off change requests. The change request log is the correct artifact for post-baseline change management.

Topics

#Change request log#UAT#Change management#Scope management

Community Discussion

No community discussion yet for this question.

Full BA-201 Practice