Definition of Ready and Done

We apply the technique of definition of ready and done because it creates transparency. Everyone can have a shared understanding of the required standars of work that was required. This is the SCRUM method where you will find the checklist of what you can consider it done. All the teams member must follow these standards as a minimum.

As you can see below, those are a checkbox which it can be considered to be offically done.

Ready (we can start designing)

• Business rules are precise and the PO answered our questions
• Dependencies on other tickets are known
• The ticket is estimated and has an owner
• The scope is only what is needed

Design approved (we can start coding)

• Wireframe, data dictionary, MCD and MLD are done
• The trainer approved them in writing on the ticket

Done (we can deploy to staging)

• All acceptance criteria of the issue are met
• Invalid data is refused
• Users see a clear message on failure and on success
• The code is clean and easy to read
• The UI is in English and follows the graphic chart
• Database changes are in SQL scripts
• No secret in the repo
• The Postman collection covers normal and error cases and passes
• Commits follow our conventions
• A teammate reviewed the pull request and it is merged
• Deployed to staging with the script and the PO is told
• The wiki and the board are up to date

Ready for develop

The PO accepted the feature on staging and no bug is still open.