Baseline information is the current state or performance of a system or process before any changes are made.
Baseline information is essential for documenting the acceptance criteria, which are the conditions that must be met for a solution or deliverable to be accepted by the stakeholders. The analyst should have gathered baseline information to support the minor modification in the user portal, such as the current customer satisfaction rate, response time, error rate, etc. The analyst should have compared the baseline information with the expected outcomes of the modification, and defined the acceptance criteria accordingly. If the analyst failed to gather any baseline information, the acceptance criteria would be incomplete and returned. The other options are not likely to cause this problem. The scope document is a document that defines the boundaries and deliverables of the project or solution, but it is not required to be included in the acceptance criteria paperwork. Forward and backward traceability are techniques to link the requirements to their sources and deliverables, which can help to ensure completeness and consistency of the requirements. User stories are a tool to document the requirements from the perspective of a user or customer, using a simple format of "As a
<role>, I want <goal>, so that <benefit>". User stories can be used as a requirements document tool, but they are not sufficient for defining the acceptance criteria. References: PMI-PBA Examination Content Outline, page 13; PMI-PBA Reference List, page 1, BABOK Guide v3, page 39.