In Scrum, a user story typically goes through several key states as it progresses from idea to implementation. Here are the states we will for User storires or Tasks:
Backlog: The user story is initially captured in the team backlog, where it awaits prioritization and refinement.
Ready: The story is refined and has clear acceptance criteria. It is now ready for implementation. This state ensures that the team understands the story and what is required to complete it.
In Progress: The team is actively working on the user story. This state indicates that development is underway.
- Blocked: The story work cannot proceed due to some external or internal impediment that must be resolved before continuing.
In Testing: Once development is complete, the story enters the validation state. Here, the team tests the implementation against the acceptance criteria to ensure it meets the requirements.
In Review: After successful validation by the team, this means it has been tested, but has not been reviewed and accepted by the PO.
Done: This means it has been completed, tested, accepted by PO and is ready for release.
- Cancelled – Work item is not to implement either because the PO decided or the team came to an agreement that it should not done.
These states help teams manage the flow of work and ensure that user stories are completed efficiently and effectively. Each state provides visibility into the progress of the story and helps identify any bottlenecks in the process.
Once the item is done it moves to the release board. (this is not the final version! - SHAIKH, Sahil tagged)
To be released / Backlog: The is meant to be released
In UAT: Once development is complete, the story is ready for User Acceptance Testing in a dedicated environment
Released: Finally when user story satisfies Definition Of Done, the user story is deployed to production, making it available to end users.
