Copado Certified Practice Exam

When a last-minute change is made to a component you have just committed on a user story, what should you do?

1. Create a new user story for the changes.

2. Commit it again on the same user story.

3. Abandon the last-minute change.

4. Notify the QA team before proceeding.

The correct answer is: Commit it again on the same user story.

Committing the change again on the same user story is a practical approach. By doing this, you ensure that all related changes are tracked within the same user story, maintaining a clear history of modifications. This is significant for version control, as it keeps all relevant updates centralized, making it easier to manage and understand the evolution of the user story. Creating a new user story for the changes may complicate the development process, as it could lead to fragmented tracking and potential confusion regarding what has been implemented versus what remains to be done. Abandoning the last-minute change would mean you are throwing away possibly important work that could enhance the functionality. Notifying the QA team could be necessary but does not directly address how to handle the code itself within the user story context. Thus, the most coherent action is to commit the change again on the same user story to keep the work organized and integrated.