What status should be set for a user story that is ready for testing in UAT?

When a user story is prepared for User Acceptance Testing (UAT), it should be set to the status "Ready for Testing." This status indicates that the user story has fulfilled the necessary criteria and has been completed to a point where it can be tested by users or stakeholders to ensure that it meets their requirements and is functioning as intended in a UAT environment.

Setting the status to "Ready for Testing" signifies that all development work is done, and any preliminary checks or quality assurance measures have been satisfied. This clarity helps both the testing team and stakeholders understand that the user story is now in the testing phase, awaiting evaluation and feedback before it can be finalized or moved into production.

In contrast, other statuses like "In Progress" imply that work is still ongoing, "Completed" might suggest that the story is done but does not specify readiness for testing, and "Not Started" indicates that no work has yet been done on the story. Thus, "Ready for Testing" is the optimal status to communicate that the user story is now poised for UAT.