/
UI Peer Review duties plan
UI Peer Review duties plan
Purpose
Idea of this process is to keep existing quality gate with 2 approves under each PR for teams where less then 3 UI developers.
Coordinator of UI Peer Review activities - Mariia Aloshyna
In case of Mariia's absence Dmitriy Litvinenko will be coordinator.
Process
- Each PR in FOLIO should have 2 approves
- Ask for review and tag FE TL-Reviewers in yours Pull requests
- PR requests have to be reviewed in 48 hours
- PR requests should have detailed description related to business flow and technical background of provided changes
- Reviewer should have appropriate task in sprint backlog to make sure that capacity reflect to this activity.
- Before each sprint 3 reviewers are selected.
- Reviewers are rotated each sprint.
- In case of absence(vacation/sick leave) SM have to notify Mariia Aloshyna
- After planning UI PR coordination should write e-mail to PO and SM of duty persons
Meet the Team
UI review team 1 | Zak Burke | Stripes Force | ||
Denys Bohdan | Denys_Bohdan@epam.com | Spitfire | ||
![]() | Uladzislau Kutarkin | Uladzislau_Kutarkin@epam.com | Firebird | |
Oleksandr Hladchenko | oleksandr_hladchenko1@epam.com | Folijet | ||
| Dmitriy Litvinenko | Dmitriy_Litvinenko@epam.com | Vega | |
![]() | John Coburn | JCoburn@EBSCO.COM | Stripes Force | |
Artem Blazhko | Artem_Blazhko@epam.com | Vega | ||
UI review team 3 | Mariia Aloshyna | Mariia_Aloshyna@epam.com | Folijet | |
Dmytro Melnyshyn | Dmytro_Melnyshyn@epam.com | Spitfire | ||
Vadym Shchekotilin | Vadym_Shchekotilin@epam.com | Firebird |
Duties list
Sprint | On Duty |
---|---|
210 | UI review team 3:
|
211 | UI review team 2:
|
212 | UI review team 1:
|
Related content
FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix
FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix
Read with this
UI Testing Team Request/Backlog Page
UI Testing Team Request/Backlog Page
More like this
Vega UAT Readiness Guide
Vega UAT Readiness Guide
Read with this
Volaris - Jira Flow
Volaris - Jira Flow
More like this
Back-end module development using the scratch environment and Rancher
Back-end module development using the scratch environment and Rancher
Read with this
Firebird - Jira Flow
Firebird - Jira Flow
More like this