Eureka Team
Eureka Development Team
Recent space activity
-
-
Projects(Namespaces) contributed about an hour ago
-
-
-
How to handle CapabilitySets which include Capabilities which may not be deflined yet. commented yesterday at 1:59 PM
-
How to handle CapabilitySets which include Capabilities which may not be deflined yet. contributed yesterday at 12:39 PM
-
-
-
[Quesnelia] [non-ECS] [Data import] Create MARC authority Records contributed yesterday at 8:16 AM
-
-
-
Authority file settings redesign commented yesterday at 7:58 AM
-
Meet the Team
| Technical Product Owner | United States (US) | |
| Vincent Bareau | Product Owner | United States (US) |
| Taras Spashchenko | Solution Architect | Germany (DE) |
Peter Lojko | Project Manager | United States (US) | |
| Team Lead (Java) | Czech Republic (CZ) | |
| Pavel Filippov | Java Developer | Lithuania (LT) |
| Dmytro Tkachenko | Java Developer | Ukraine (UA) |
| Java Developer | Georgia (GE) | |
| Roman Leshchenko | Java Developer | Ukraine (UA) |
| Yaroslav Kiriak | Java Developer | Ukraine (UA) |
| Ryan Berger | JS Developer | United States (US) |
| Zak Burke | JS Developer | United States (US) |
| Aidyn Zhakizhanov | JS Developer | Kazakhstan (KZ) |
| Yauhen Viazau | QA/AQA | Uzbekistan (UZ) |
| Scrum Master | Ukraine (UA) | |
| Kimie Kester | UX Designer | United States (US) |
Team Calendar
Below you can find 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 request 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 2022
and
on 17nd of December 2022
Please approve if there are no objections.
Scrum Board
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