A given user story has a description and an acceptance criterion. Which two other things are needed to mark the story as ready?

Priority (A): Before a user story can be marked as ready, it needs to be prioritized. This helps the

development team understand the importance of the story relative to other items in the backlog and

ensures

that

the

most

critical

features

are

addressed

first.

Reference: Appian Documentation - Managing Backlogs and Prioritization

Estimation (D): Estimation is essential to determine the effort required to implement the user story.

It allows the team to plan the sprint effectively, allocate resources, and ensure that the story can be

completed

within

the

sprint

timeline.

Reference: Appian Documentation - Estimation Techniques

Note: Sprint number (B) and developer assignment (C) are important for sprint planning and task

allocation but are not required to mark the story as ready.