🪃
Engineering Playbook
  • Engineering Playbook
  • Agile Development
    • Kanban from the start
    • Daily Stand-up
    • Collaboration
      • Mobile Designer X Mobile Developer
    • Backlog Management
      • Backlog Refinement
    • Card Management
      • Epics
      • User story
        • Collaboration experience with acceptance criteria
        • Proper acceptance criteria
      • Task
      • Bug
      • Hotfix
      • Sub-task
      • Defect
      • Columns
      • Card organization
      • Column Limit
      • Board Templates
    • Pull System Task Assignment
    • Retrospectives
    • Team Agreement
      • Working Agreement
      • Definition of Ready
      • Definition of Done
    • Agile Metrics
  • Github
    • Source Control
    • Merge Strategies
    • Versioning
    • Code Reviews
      • Author's Checklist
      • Reviewer's Checklist
  • Documentation
    • GraphQL as an API Doc
  • DevOps
    • Continuous Integration
Powered by GitBook
On this page
  • When should a Definition of Ready be updated
  • What should be avoided
  • How to get stories ready

Was this helpful?

  1. Agile Development
  2. Team Agreement

Definition of Ready

When the development team picks a user story from the top of the backlog, the user story needs to have enough detail to estimate the work needed to complete the story within the sprint. If it has enough detail to estimate, it is ready to be developed.

💡 Advisory Note:

If a user story is not Ready in the beginning of the iteration, then it increases the chance that the story will not be done at the end of this sprint.

To help team members to ensure that the user story they wrote contains all the necessary details for the scrum team to understand the work to be done.

When should a Definition of Ready be updated

Update the Definition of Ready anytime when the team observes that there is a missing piece of information in the user stories that repeatedly impacts the planning.

What should be avoided

The Definition of Ready the checklist covers items that apply in a general. Don't add items or details that only apply to one or two user stories.

How to get stories ready

In the case that the highest priority work is not yet ready, it still may be possible to make forward progress. Here are some strategies that may help:

  • Backlog refinement sessions are a good time to validate that the prioritized user stories are verified to have a clear description, have required links on UX/UI designs, have well-defined acceptance criteria, and have a business value that can be demonstrated. This will also be a good time to break down large user stories.

  • Prioritization sessions are a good time to prioritize user stories that unblock other blocked high-priority work.

  • Blocked user stories can often be broken down in a way that unblocks a portion of the original stories' scope. This is a good way to make forward progress even when some work is blocked.

PreviousWorking AgreementNextDefinition of Done

Last updated 3 years ago

Was this helpful?