Definition Of Ready - DoR

Owned by Bandoch dos Santos, Diego
Last updated: Sept 25, 2023 by Hellen Rodrigues Magalhaes
1 min read

The Definition of Ready ensures that the product backlog items are well-prepared, understood, and have enough information for the development team to start working on them. The criteria in the DoR may vary from team to team.

To consider the Story ready for a developer we should have this criterion already defined:

Mandatory

Problem statement and Solution are aligned with the market
Acceptance Criteria: specific conditions or requirements that a product or feature must meet to be considered acceptable or "done" from the perspective of the stakeholders or users.
Wireframes: mockups provided by the UI/UX designer
Review Figma to ensure consistency with requirements and mockups.
Registered all blockers/dependencies/risks from other teams/applications
Access granted to the team to specifics tool inside of the story(Ex: Salesforce)
Create a POC for the User Story
When the story has at least one integration with another system/repo:
Complemented with any existing architectural diagrams (sequence diagrams, infrastructure diagrams).
The story has defined and documented:
a) API schema (input contract, output contract, error codes).
b) Data sources involved as well the format of each entity.
The story Status is “Ready for Development” on JIRA
The story is approved by the RBI Product Manager and RBI Technical Manager, with proper technical details and acceptance criteria aligned between RBI and CI&T teams
In case of external partners, the team validates the technical solution with all the stakeholders

Desirable

The test plan is defined and documented including the types of tests and data mass that will be used. Align with the Acceptance Criteria during the refinement.
Non-functional requirements like the avg response time for API, page load time for web, responsiveness for App screens and so on