Spitfire Team
Spitfire Development Team
Recent space activity
-
-
Karate tests and TestRail integration contributed 19 minutes ago
-
-
-
Folijet Team contributed about 4 hours ago
-
-
-
Write Karate tests with Github Copilot and TestRail MCP server contributed about 7 hours ago
-
-
-
RTR Configuration on Eureka contributed yesterday at 3:06 PM
-
-
-
UAT - Prevent Inactive patrons from Requesting - DRAFT contributed yesterday at 7:52 AM
-
Meet the Team
Khalilah Gambrell | Product Owner | United States (US) | ||
Christine Schultz-Richert | Product Owner | 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 | Poland (PL) | ||
Svitlana Kovalova | Java Developer | Ukraine (UA) | ||
Denys Bohdan | JS Lead 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 and Christine, 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 2025
and
on 17th of December 2025
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-spitfire' 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 = Spitfire (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 PO and the dev team;
Estimation in Story Points is added;
There are no blockers, dependencies, or prerequisites preventing the team from completion of the story/bug (if there are any - they must be clearly indicated and story/bug must be moved to Blocked status);
Story conforms to INVEST requirements (if possible):
Independent
Negotiable
Valuable
Estimatable
Small
Testable