Sprint 3 - Action items

 

https://rbictg.atlassian.net/browse/IBFEC-136

  • Consider responsiveness during development

  • Do not consider figma only as the truth. We should questionate when figma not make sense.

https://rbictg.atlassian.net/browse/IBFEC-139

  • PO bring to the development team what will be the structure used in Sanity

  • Create a checklist of topics for business refinement

https://rbictg.atlassian.net/browse/IBFEC-158

  • Even during development use masses that resemble real scenery.

https://rbictg.atlassian.net/browse/IBFEC-232

  • When a code/structure restructuring happens:
    signal to QA that needs more attention on the specific point.

  • The dev should perform the tests in native

PS: All bugs/sub-bugs should have the 5 why analyses when the ticket is closed.