User Story Lifecycle

1. Create a User Story: In Azure DevOps, go to the backlog of your project and select the iteration (sprint) that you want to add the user story to. Then click on the “New Work Item” button and select “User Story” from the dropdown menu. Fill in the required fields such as title, description, acceptance criteria, and priority. You can also add tags, attachments, and set the estimate for the user story.
2. Add User Story to Sprint: Once the user story is created, you can add it to the sprint by dragging and dropping it from the backlog to the sprint board. Alternatively, you can go to the sprint board and click on the “Add work items” button to select the user story from the backlog.
3. Assign User Story to Team Member: To assign the user story to a team member, go to the sprint board and click on the user story to open it. Then click on the “Assignee” field and select the team member from the dropdown menu. You can also assign the user story by dragging and dropping it to the team member’s name on the sprint board.
4. Track Progress of User Story: As team members work on the user story, they can update the progress by changing the state of the work item. In Azure DevOps, the default workflow for user stories includes states such as “New”, “Approved”, “Committed”, “Done”, and “Closed”. You can also customize the workflow to fit your team’s needs.
5. Review and Approve User Story: Once the user story is completed, it can be reviewed by the product owner or stakeholders to ensure that it meets the acceptance criteria. If there are any issues or changes required, they can be added as comments or tasks in the work item. Once the user story is approved, it can be closed by changing its state to “Closed”.

By following these steps, you can effectively manage the lifecycle of user stories in Azure DevOps and ensure that they are completed on time and meet the requirements of the project.

In simple terms, these can be represented in the table below