Sarah: Hello Mr. Agile, How are you doing? I have a question for you. In agile, when do you consider something ready to implement?
Mr. Agile: I am doing very well Sarah. In agile, we have 3 stages of readiness:
- User Story is READY if a team can implement it, and a Product Owner can prioritize it.
- The Backlog is READY when about 1.5-2 times Sprint's worth of User Stories at the top of the backlog is READY, and those user stories are sufficiently small to fit in a sprint.
- Team is READY when every team member is self-organized.
Sarah: That's very interesting and helpful Mr. Agile. Can you please explain more about user story readiness?
Mr. Agile: A User Story can be considered READY if:
- It is defined as need, conversations, and confirmations and has unique priority in relation to every other story in the product backlog.
- It follows INVEST principals, which means a story is independent, negotiable, valuable, estimable, and testable.
- It has been estimated (in story points) by the team.
- It is small enough to fit inside a sprint. Larger stories should be reformulated and splitted before the sprint planning to be considered "Ready".
- It does not have any known dependency that can block the completion of story.