Promin Team

Promin Team

Promin Development Team

 





Recent space activity

Recent updates

Loading recently updated content…



Meet the Team 

Khalilah Gambrell

kgambrell@ebsco.com

Product Owner

United States (US)

Christine Schultz-Richert

cschultz-richert@ebsco.com

Product Owner

United States (US)

Ryan Szu Hwa Lee

rlee1@corp.epnet.com

EIS Lead

United States (US)

Radhakrishnan Gopalakrishnan (Vijay)

RGopalakrishnan@ebsco.com

FSE

United States (US)

Viktor Gema

viktor_gema@epam.com

Solution Architect

Czech Republic (CZ)

Pavlo Smahin

pavlo_smahin@epam.com

Team Lead (Java)

Ukraine (UA)

Viacheslav Kolesnyk

viacheslav_kolesnyk@epam.com

Java Developer

Croatia (HR)

Aliaksandr Fedasiuk

Aliaksandr_Fedasiuk@epam.com

Java Developer

Uzbekistan (UZ)

Denys Bohdan

denys_bohdan@epam.com

JS Lead Developer

Ukraine (UA)

Oleksandr Hladchenko

oleksandr_hladchenko1@epam.com

JS developer

Ukraine (UA)

Valery Pilko

valery_pilko@epam.com

QA

Georgia (GE)

Natalia Zaitseva

natalia_zaitseva1@epam.com

Scrum Master

Ukraine (UA)

Team Calendar





Below you can find a vacation email template that you can use.

You should cc: PO - Khalilah, Christine, Alvaro, SM - Natalia, Front-end Lead - Denys or Back-end Lead - Pavlo, DM - Oleksii Petrenko, and your Resource Manager

All requests should be sent in advance; the only exception is emergency requests for 1-2 days.  

For a 1-week vacation, the request should be sent, preferably, 2 weeks before.   

For long-term vacations (2 weeks), the request should be sent, preferably, one month before. 

For vacations of 3-4 weeks, the request should be sent two months before.

Vacation template

Hi team, 



I would like to take a vacation

on  12  - 17  of November 2026

and

on  17th  of December 2026



Please approve if there are no objections.  




For the items to be fetched and shown on the board, the following requirements should be met:

  • Item must have 'epam-promin' label in case it is posted in some other project;

  • Item must have a 'back-end' or 'front-end' label to be caught by quick filters;

  • Item should have Development Team = Promin (to be filtered out from the manual testing queue).




Definition of Ready

User Story or Bug can be added to a Sprint  only if it conforms to the following criteria of the Definition of Ready:

  • Requirements are clearly expressed by PO, reviewed/groomed, and well understood by the dev team;

  • Acceptance criteria are clearly defined and confirmed by the PO and the dev team;

  • Estimation in Story Points is added;

  • There are no blockers, dependencies, or prerequisites preventing the team from completing the story/bug (if there are any - they must be clearly indicated and the story/bug must be moved to Blocked status);

  • Story conforms to INVEST requirements (if possible):

    • Independent

    • Negotiable

    • Valuable

    • Estimatable

    • Small 

    • Testable