Skip to content

Definition-Of-Ready (User Stories)

The definition of ready for user stories should satisfy the following criteria:

  1. Independent: The user story should be self-contained, in a way that there is no inherent dependency on another user story.
  2. Negotiable: User stories, up until they are part of a sprint, can always be changed and rewritten.
  3. Valuable: A user story must deliver value to the end-user.
  4. Estimable: You must always be able to estimate the size of a user story.

User Story Template

The following template can be used to create user stories:

As a <type of user>, I want <some goal> so that <some reason>.

Example User Stories

  1. As a user, I want to be able to log in to the system so that I can access my account.
  2. As a user, I want to be able to view my order history so that I can see what I have ordered in the past.
  3. As a user, I want to be able to add items to my shopping cart so that I can purchase them later.

Definition -Of-Ready (Tasks)

The definition of ready for tasks should satisfy the following criteria:

  1. Specific: The task should be specific enough that it can be completed in a single sprint.
  2. Measurable: The task should be measurable so that it can be tracked and completed.
  3. Achievable: The task should be achievable within the sprint.
  4. Relevant: The task should be relevant to the user story it is associated with.
  5. Time-bound: The task should have a clear deadline for completion.
  6. Estimable: You must always be able to estimate the size of a task.
  7. Small: The task should be small enough to be completed in a single sprint.
  8. Testable: The task should be testable so that it can be verified as complete.
  9. Understandable: The task should be understandable by all team members.
  10. Valuable: The task should deliver value to the end-user.