Monday 11th August

Process changes

1. Timeline should include testing with frontend integration
   1. Timeline should be given with complete understand of what needs to be done
2. Acceptance criteria is nothing but checklist for release from development
   1. We should not miss any acceptance criteria while releasing -> this is the basic of release
   2. Requirements gets added newly while development
      1. Are QAs giving the explicit requirements while doing the story telling? -> should we miss it or not, if yes then we need to take it in next relase.
3. Only owner of the release and owner of the environment can merge/deploy code to the respective environment.
   1. Owner can check it with local demo or qa demo or dev env demo for everything to make sure whatever we're merging/pushing is stable.
   2. Release owner needs to set up a demo meeting with two days in advance so that we can get the bandwidth if there are some issues.
4. If its blocker/failing, and you know it, then fix it just get everyone onboarded by a slack channel message over technology or preprod channel
5. PMs will be conducting every week demos with ongoing releases, and tracking their observations, and keeping the notes of it.
   1. if there are some tickets/user stories which are interdependent what should we do in the PM demos.
   2. make sure whatever we're demoing is fulfilling the acceptance criteria.
6. A QA while writing the defect/bug, should check thorough and share the complete defect/bug details this is only for staging environment
7. For Preprod/Mercury, QA Should do a complete RCA Document for each issue/defect, set up a meeting with all stakeholders to get them onboraded, and then make a plan of fix. -> This will take place once we've released the current v2.0 to the production environment.
8. Technical feasibility sometimes miss the requirements, how can we tackle this issue? -> GS