Definition of Ready - mhmunem/Grocery-Comparison-App GitHub Wiki

Task DoR

  • The tasks is estimated.
  • The task has a description with a clear outcome, i.e. the "M" in SMART.

Story DoR

  • It complied to the INVEST evaluation framework.

  • The stories are Independent:

  • Story can be developed Independent from other stories.

  • One team member can complete the work with minimal or no dependencies on others.

  • Clear and appropriate name labels for tasks.

  • The task description is well written and anyone can pick up tasks without others help.

  • The stories are Valuable:

    • The priority in the backlog is clear
    • The team understand why we do this and the impact on the user

  • The stories Estimable:

    • The story points based on the complexity
    • All task times are estimated by the team. (using in fibonacci number, T-shirt sizing, MD, etc.)

  • The stories are Small:

    • It is not an epic.
    • It can be completed in less than one sprint.

  • The stories are Testable:

    • The team understands how the story can be tested.
    • The story has clear acceptance criteria to test.
    • Acceptance tests and examples are defined.
    • Mock data are defined.

  • The story has an estimate, i.e. complexity.

  • The story has clear acceptance criteria.

  • The story has been broken down into (ready) tasks.

Sprint DoR

  • It has a goal that matches the product vision, as discussed with the PO.

  • It contains stories that are all ready.

  • Stories are sorted in priority order.

  • It has a start and closing date

  • The template of the User Story format is provided as following:

       As a <user>, I want to <goal> so that I can <benefit>.

    • Acceptance Criteria template:

      Scenario 5: <summary label>
 - Given the user <done this>
 - When the user <goes to>
 - And <additional>
 - Then the user <can do this>

  • Acceptance criteria conditions of satisfaction is known to all team members.

⚠️ **GitHub.com Fallback** ⚠️