/
Eureka Team

Eureka Team

Eureka Development Team

 

 

Contents

 

Recent space activity

Recent updates

Loading recently updated content…

 

Meet the Team 

, (opens new window)

Craig McNally

Solution Architect, EBSCO

United States (US)

, (opens new window)

Matt Reno

Technical Product Owner, EBSCO

United States (US)

, (opens new window)

Vincent Bareau

Solution Architect, EBSCO

United States (US)

, (opens new window)

Peter Lojko

Project Manager, EBSCO

United States (US)

, (opens new window)

Oleksii Kuzminov

Team Lead (Java), EPAM

Czech Republic (CZ)

, (opens new window)

Dmytro Tkachenko

Java Developer, EPAM

Ukraine (UA)

, (opens new window)

Yauhen Vavilkin

Java Developer, EPAM

Georgia (GE)

, (opens new window)

Pk Jacob Pullolickal

Java Developer, EBSCO

United States (US)

, (opens new window)

Aliaksei Harbuz

Java Developer, EPAM

Belarus (BY)

, (opens new window)

John Coburn

JS Developer, EBSCO

United States (US)

, (opens new window)

Yauhen Viazau

AQA, EPAM

Uzbekistan (UZ)

, (opens new window)

Polina Ustimenko

QA, EPAM

Kazakhstan (KZ)

, (opens new window)

Natalia Zaitseva

Scrum Master, EPAM

Ukraine (UA)

, (opens new window)

Kimie Kester

UX Designer, EBSCO

United States (US)

Team Calendar

Below is a vacation email template you can use.

You should cc: PO - Matt, 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, send the request preferably 2 weeks in advance.   

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

from 12  - 17  of November 2026

and

on the 17th of December 2026

 

Please approve if there are no objections.  

Eureka Scrum Board

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

  • Item must have the 'epam-eureka' 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 = Eureka (to be filtered out from manual testing queue).

 

 

Eureka Support Board

Before creating a new item for the Eureka team, read the Guideline.

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

  • Item must be created in Eureka Support project;

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

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 the 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 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

Eureka FY27 Q1 Progress Dashboard

Eureka Features Board

Defects Backlog Dashboard

Retrospective / Action Plan

Eureka - Definition of Done v1.0

Spikes / Investigations

Eureka - Jira Flow