SaFi Bank Space : SaFi MVP: 2.3. Execution Strategy

4.1.1. Entry and Exit Criteria

• The entry criteria refer to the desired conditions in order to start test execution; only the migration of the code and fixes need to be assessed at the end of each cycle. 

• The exit criteria are the desirable conditions that need to be met to proceed with the implementation. 

• Entry and exit criteria are flexible benchmarks. If they are not met, the QA team will assess the risk, identify mitigation actions and provide a recommendation. All this is input to the project manager for a final “go-no go” decision. 

4.1.2. Test Cycles

• There will be two cycles for functional testing. Each cycle will execute all the scripts.

• The objective of the first cycle is to identify any blocking, critical defects, and most of the high defects. It is expected to use some workaround in order to proceed with the tests.

• The objective of the second cycle is to identify remaining high and medium defects, remove the workaround from the first cycle, and correct gaps in the scripts.

4.1.3. Validation and Defect Management

• It is expected that the testers execute all the scripts in each of the cycles. However, it is recognized that the testers could also do additional testing if they identify a possible gap in the scripts. This is especially relevant in the second cycle when the Product Team joins the QA team in the execution of the test since the Product Team has a deeper knowledge of the business processes. If a gap is identified, the scripts and traceability matrix will be updated and then a defect logged against the scripts.

• The defects will be tracked through JIRA only. The Squad teams will gather information on a daily basis from JIRA, and request additional details regarding the defects. The Squad teams will work on fixes. 

• It is the responsibility of the tester to open the defects, link them to the corresponding test case, assign an initial severity and status, retest, and close the defect.

• It is the responsibility of the Tech Lead to review the severity of the defects and facilitate with the Squad team the fix and its implementation, communicate with testers when the test can continue or should be halted, request the tester to retest, and modify the status as the defect progresses through the cycle.

• It is the responsibility of the Squad teams to review the defects in JIRA on a daily basis, ask for details if necessary, fix the defect, communicate to Tech lead that the fix is done, and implement the solution.

• It is the responsibility of the Project Manager to communicate with the Product Owner and Business Owner about all the NON-critical defects especially HIGH severity defects whether those bugs need to be fixed immediately or can wait for the next sprint.

Defects found during the Testing will be categorized according to the bug-reporting tool “JIRA” and the categories are:

4.1.4. Defect Life Cycle

1. QA will create a bug ticket, select a component, and assign it to the Product Owner with their respective teams listed below:

   • Miroslav Pavelek (Accounts)

   • Maria D'Amato (Transactions)

   • Kristof Szep (Loans & Risk)

   • Viktor Humaj (Back Office)

   • Ilija Sovilj (Common)

   • Branislav Haukwitz (Customer & Onboarding)

   • Revazi Dzidziguri (Finance)

   • Miroslav Pavelek (Accounts & Subscription)

2. PO will decide whether the bug is valid, change request, or needs to be fixed immediately.

3. For change requests, PO will communicate with the Business Owners to validate and agree before the implementation.

4. For P1 ticket, it needs to be fixed immediately.

5. For P2 to P4 tickets, PO will decide whether the bug needs to be fixed immediately or not that important for EPFS license so it can wait for the next sprint.

6. PO will then assign the tickets to the development team that will fix the bugs.

7. Once fixed, the Dev team will assign the tickets to QA. Otherwise, re-assign to Dev team for rework.

8. QA will close the ticket.

4.1.5. Bug Report Template