The usual agile requirements life cycle consists of three simple states: “not started”, “in progress” and “done”. This is not enough! These steps only cover the software development part of the requirements life cycle. Do not forget about the stages before and after. First requirements are new, then they are analyzed and estimated, then they are commited for delivery in a sprint. After that comes the states mentioned above. After that comes release, deployment, maintenance and eventually retirement. Have a look at the Requirements Abstraction Model.
User Story Life Cycle is Not Enough
