Common Rules
Overview
| # | Rule | Description |
|---|
| 1 | Public holiday and Annual Leave ( same as VN regulation) | VN public holiday and 12 AL |
| 2 | Pull request | Peer review (optional), team lead review is mandatory |
| 3 | Performance review | Every 1 year, the US point will be collected every sprint (see the figure below) |
| 4 | Week per sprint | 2 |
SLA
| Priority | Response Time | Solution |
|---|
| Highest (P1) | 5 minutes | 2 hours |
| High (P2) | 30 minutes | 4 hours |
| Medium (P3) | 1 hours | 12 hours |
| Low (P4) | 2 hours | 24 hours |
| Very low (P5) | 4 hours | As planned (Not SLA) |
Bug/Incident state flow highgest P1
| State | Description |
|---|
| TODO | Bug/Incident P1, Client Phone call to hotline datapal support |
| ACTIVE | As soon as the Bug is assigned, Tester will change the status from TODO to ACTIVE and proceed to clarify the circumstances of the problem. |
| IN PROGRESS | Developer/DevOps changes the Bug status from ACTIVE to IN PROGRESS and conducts the bug fixing process |
| RESOLVED | After completing coding, the developer creates a PR and waits to be merged into the develop branch. During this time they will change the status from IN PROGRESS to RESOLVED. Make sure that Defect Type, Defect origin, Cause Category, Cause and Solution are filled out. DevOps when handling Infrastructure Bugs will ignore this status |
| IN TESTING | Dev/DevOps changes the status from RESOLVED to IN TESTING and reassigns Tester. Make sure that evidence about the bug fix results is saved in the Bug comments |
| REOPEN | If the Tester evaluates that the bug is still not fixed, change the status from IN TESTING to REOPEN. Note that reopened bugs need a REOPEN label |
| DONE | The Tester switches to DONE status when the bug has been resolved |
Bug/Incident state flow highgest P2, P3, P4, P5
| State | Description |
|---|
| TODO | The client creates a Bug ticket when it detects an application bug or an infrastructure incident. Bug tickets will be created by the Client with priority from P2 - P5 |
| ACTIVE | As soon as the Bug is assigned, Tester will change the status from TODO to ACTIVE and proceed to clarify the circumstances of the problem. |
| IN PROGRESS | Developer/DevOps changes the Bug status from ACTIVE to IN PROGRESS and conducts the bug fixing process |
| RESOLVED | After completing coding, the developer creates a PR and waits to be merged into the develop branch. During this time they will change the status from IN PROGRESS to RESOLVED. Make sure that Defect Type, Defect origin, Cause Category, Cause and Solution are filled out. DevOps when handling Infrastructure Bugs will ignore this status |
| IN TESTING | Dev/DevOps changes the status from RESOLVED to IN TESTING and reassigns Tester. Make sure that evidence about the bug fix results is saved in the Bug comments |
| REOPEN | If the Tester evaluates that the bug is still not fixed, change the status from IN TESTING to REOPEN. Note that reopened bugs need a REOPEN label |
| DONE | The Tester switches to DONE status when the bug has been resolved |
| STT | Role | Supporter | Phone | Email | Language |
|---|
| 1 | DevOps | Tung Pham | 0973957746 | tungpv.it@gmail.com | VN |
| 2 | Dev Backend Authen, Authoz | Ha Pham | | | VN/EN |
| 3 | Dev Backend Grouping tool, Vi motus | Tu Ta | | | VN/EN |
| 4 | Dev Backend Mapping tool | Quy Do | | | VN/EN |
| 5 | Dev Backend Data stride | Duc Do | | | VN |
| 6 | Dev Frontend | Man Nguyen | | | VN/EN |