Promin Team
Promin Development Team
Contents
- 1 Promin Development Team
- 1.1 Meet the Team
- 1.2 Team Calendar
- 1.2.1 Vacation template
- 1.3 [TO UPDATE] Scrum Board
- 1.4 [TO UPDATE] Promin - Jira Flow
- 1.5 Umbrellaleaf FY27 Q1 Progress
- 1.6 [TO UPDATE] Defects Backlog
- 1.7 Definition of Ready
- 1.8 Retrospective / Action Plan
- 1.9 Promin - Definition of Done
- 1.10 Promin - Roadmap
- 1.11 [TO UPDATE] Spikes / Investigations
Recent space activity
Recent updates
Meet the Team
Khalilah Gambrell | Product Owner | United States (US) | ||
Christine Schultz-Richert | Product Owner | United States (US) | ||
Ryan Szu Hwa Lee | EIS Lead | United States (US) | ||
Radhakrishnan Gopalakrishnan (Vijay) | FSE | United States (US) | ||
Viktor Gema | Solution Architect | Czech Republic (CZ) | ||
Pavlo Smahin | Team Lead (Java) | Ukraine (UA) | ||
Viacheslav Kolesnyk | Java Developer | Croatia (HR) | ||
Aliaksandr Fedasiuk | Java Developer | Uzbekistan (UZ) | ||
Denys Bohdan | JS Lead Developer | Ukraine (UA) | ||
Oleksandr Hladchenko | JS developer | Ukraine (UA) | ||
Valery Pilko | QA | Georgia (GE) | ||
Natalia Zaitseva | 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