...
To consider the Story ready for a developer we should have this criterion already defined:
- Title: a clear user The story title is defined and give a well visibility of the problem to be solved
- Description/Problem statement: a clear and concise statement that describes a specific problem to be solved or a gap to be filled.
- registered at Jira, reviewed and approved by the RBI Product Manager and RBI Technical Manager, with proper technical details and acceptance criteria aligned between RBI and CI&T teams
- 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.
- Dependencies: mapped Registered all blockers/dependencies/risks from other teams/applications
- Estimates: use the specific measure to estimate the story on the macro visionAccess 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 team validates the technical solution (How?)
- The test plan is defined and documented including the types of tests. Align with the Acceptance Criteria during the refinement.
- Wireframes: mockups provided by the UI/UX designer
- Testability: comprehensive test plan created to guide the developers in executing the required testsThe 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.
c) Desirable, but hard to obtain: Non-functional requirements like the avg response time for API, page load time for web, responsiveness for App screens and so on - The story Status is “Ready for Development” on JIRA
- Desirable: use the specific measure to estimate the story on the macro vision