Spitfire Development Team
Meet the Team
| Khalilah Gambrell | kgambrell@ebsco.com | Product Owner | United States (US) | ||||
| Christine Schultz-Richert | cschultz-richert@ebsco.com | Product Owner | United States (US) | ||||
| Radhakrishnan Gopalakrishnan (Vijay) | RGopalakrishnan@ebsco.com | FSE | United States (US) | ||||
| Kalibek Turgumbayev | kalibek_turgumbayev@epam.com | Solution Architect | Kazakhstan (KZ) | ||||
| Pavlo Smahin | Team Lead (Java) | Ukraine (UA) | |||||
| Viacheslav Kolesnyk | viacheslav_kolesnyk@epam.com | Java Developer | Poland (PL) | ||||
| Mukhiddin Yusupov | mukhiddin_yusupov@epam.com | Java Developer | Uzbekistan (UZ) | ||||
| Svitlana Kovalova | svitlana_kovalova1@epam.com | Java Developer | Ukraine (UA) | ||||
| Denys Bohdan | denys_bohdan@epam.com | JS Lead Developer | Ukraine (UA) | ||||
| Dmytro Melnyshyn | dmytro_melnyshyn@epam.com | JS Developer | Ukraine (UA) | ||||
| Sherzod Kenjaev | sherzod_kenjaev@epam.com | AQA | Uzbekistan (UZ) | ||||
| Valery Pilko | valery_pilko@epam.com | QA | Georgia (GE) | ||||
| Natalia Zaitseva | Scrum Master | Ukraine (UA) |
Team Calendar
Below you can find vacation email template that you can use.
You should cc: PO - Khalilah, SM - Natalia, Front-end Lead - Denys or Back-end Lead - Pavlo, DM - Oleksii Petrenko and your Resource Manager
| Note |
|---|
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. for vacations 3-4 weeks the request should be sent, two month before. |
| Info | ||
|---|---|---|
| ||
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. |
| Iframe | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Scrum Board
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 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 = Spitfire (to be filtered out from manual testing queue).
Spitfire - 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