-
Notifications
You must be signed in to change notification settings - Fork 4
Definition of Ready
Alexandre Quessy edited this page Feb 19, 2022
·
6 revisions
The stories at the top of the Product Backlog that the Team will be pulling into the Sprint Backlog, must be Ready. The Product Owner is responsible for putting the features and stories in the backlog. However, the Team must work with the Product Owner during Backlog Refinement to help them get the stories into actionable shape. Only then will the Team be able to estimate how much work any one story will take and how many Points they can take into a Sprint.
Here are the attributes of a user story for us to consider it Ready to be implemented by a developer:
- Have a title (starting with an action verb)
- Provide a user story (describing which user it's for, and why there is value to this story)
- Provide a list of acceptance criteria (each criteria must be measurable)
- Ideally provide a wireframe or mockup.
- It should be story-pointed.
- spikes and bugs are 0 points
- spike should be time-boxed to given duration (in hours or days) Once the spike is done, we should create some other ticket(s).
- spikes are investigations for which there is some unknown.
- items that are not ready have the "to groom" label.
- The team must agree on the technical details of the implementation.