Spitfire Development Team
Meet the Team
| Khalilah Gambrell | kgambrell@ebsco.com | Product Owner | ||||||||||||
| Christine Schultz-Richert | cschultz-richert@ebsco.com | Product Owner | ||||||||||||
| Radhakrishnan Gopalakrishnan (Vijay) | RGopalakrishnan@ebsco.com | FSE | ||||||||||||
| Pavlo Smahin | Team Lead (Java) | |||||||||||||
| Viacheslav Kolesnyk | viacheslav_kolesnyk@epam.com | Java Developer | ||||||||||||
| Shans Kaluhin | shans_kaluhin@epam.com | Java Developer | ||||||||||||
| Sherzod Nurjonov | sherzod_nurjonov@epam.com | Java Developer | ||||||||||||
| Khasan Sidikov | khasan_sidikov@epam.com | Java Developer | ||||||||||||
| Artur Hovhannisyan | artur_hovhannisyan1@epam.com | Java Developer | ||||||||||||
| Denys Bohdan | denys_bohdan@epam.com | JS Lead Developer | ||||||||||||
| Dmytro Melnyshyn | dmytro_melnyshyn@epam.com | JS Developer | ||||||||||||
| Zaza Managadze | zaza_managadze@epam.com | JS Developer |
| Oll Isanbaev | oll_isanbaev@epam.com | AQA | ||||||||
| Sherzod Kenjaev | sherzod_kenjaev@epam.com | AQA | ||||||||||||
| Valery Pilko | valery_pilko@epam.com | QA | ||||||||||||
| Yauhen Viazau | yauhen_viazau@epam.com | QA | ||||||||||||
| Natalia Zaitseva | Scrum Master |
Team Calendar
| Team Calendars | ||
|---|---|---|
|
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
| 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 is 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-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