Eureka Team

Eureka Team

Eureka Development Team

 

 

 

Recent space activity


 

Meet the Team 

Craig McNally

Technical Product Owner

United States (US)

Matt Reno

Technical Product Owner

United States (US)

Vincent Bareau

Product Owner

United States (US)

Viktor Gema

Solution Architect

Czech Republic (CZ)

Peter Lojko

Project Manager

United States (US)

Oleksii Kuzminov

Team Lead (Java)

Czech Republic (CZ)

Dmytro Tkachenko

Java Developer

Ukraine (UA)

Yauhen Vavilkin

Java Developer

Georgia (GE)

Pk Jacob Pullolickal

Java Developer, EBSCO

United States (US)

Ryan Berger

JS Developer

United States (US)

Yauhen Viazau

AQA

Uzbekistan (UZ)

Yury Barsukou

QA

Ukraine (UA)

Natalia Zaitseva

Scrum Master

Ukraine (UA)

Kimie Kester

UX Designer

United States (US)

Team Calendar

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

You should cc: PO - Craig, SM - Natalia, Team Lead - Oleksii K., 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. 

Vacation template

Hi team, 

 

I would like to take a vacation

on  12  - 17  of November 2026

and

on the 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-eureka' label in case it in posted in some other project;

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

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

 


Eureka - Jira Flow

 

Definition of Ready

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

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

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

  • Estimation in Story Points is added;

  • There are no blockers, dependencies, 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

Retrospective / Action Plan

 


Eureka - Definition of Done v1.0

 


Spikes / Investigations