BUSINESS-ANALYST Question 31

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose B2

  The important part is creating a 'User Story' for the new changes/updates, none of the other answers specify that happening. This is important before you get to the testing stage as what are you testing if you haven't created a story for the change/update

• Chose B7

  Updating the change request log is essential for documenting the requested changes, tracking them, and ensuring they are properly managed throughout the project. Additionally, drafting a new user story is a way to capture the updated requirements in a clear and concise format that can be easily understood by the development team. User stories are a common Agile technique for capturing functional requirements and are used as a basis for development and testing. "A" might be relevant for managing the changes, but it doesn't specifically address how to capture the updated requirements in a user-focused format like a user story. "C" is not directly related to managing changes to requirements after the technical demo.

• 3

  I think correct option is A. When requirements change, it is important to update the change management document and user acceptance testing plans. This will ensure that all stakeholders are aware of the changes and that the new requirements are tested thoroughly.