Which step should the business analyst take next?

Universal Containers is currently doing user acceptance testing for a global customer service project that leverages Service Cloud. A stakeholder is executing a test case for a specific user story.

The stakeholder has provided this feedback:

• The functionality described in the test case is working as expected.

• The stakeholder wants to change the label of several fields described in the test case.

• The stakeholder wants to add two new fields that were excluded from the test case.

Which step should the business analyst take next?
A . Acknowledge the feedback, update the existing user story to include the field changes, and assign the user story back to the technical team for immediate development.
B . Acknowledge the feedback, create a new test case that includes the field changes, and assign the test case hack to the stakeholder far immediate testing.
C . Acknowledge the feedback, create a new user Story that includes the field changes, and ask the stakeholder to update the existing tat case to show it was successfully tested.

Answer: C

Explanation:

This answer suggests acknowledging the feedback, creating a new user story that includes the field changes, and asking the stakeholder to update the existing test case to show it was successfully tested as the next step for the BA after receiving this feedback from a stakeholder during user acceptance testing for a global customer service project that leverages Service Cloud. Acknowledging the feedback shows respect and appreciation for the stakeholder’s input and involvement. Creating a new user story that includes the field changes helps to capture and prioritize the new requirements, and avoid scope creep or impact on other user stories. Asking the stakeholder to update the existing test case to show it was successfully tested helps to validate and document that the functionality described in the test case is working as expected.

Reference: https://trailhead.salesforce.com/en/content/learn/modules/salesforce-business-analyst-quick-look/use-user-stories-to-capture-requirements