Spitfire Development Team




Recent space activity



Meet the Team 

Khalilah Gambrell

kgambrell@ebsco.comProduct Owner

Sobha Duvvurisduvvuri@ebsco.comFull Stack Tech Lead

Carole Godfrey

cgodfrey@ebsco.comFull Stack Developer

Dmytro Tkachenko

dmytro_tkachenko@epam.comTeam Lead (Java)

Natalia Zaitseva

natalia_zaitseva1@epam.comJava Developer

Andrii Paias

andrii_paias@epam.comJava Developer

Igor Godlevskyi

igor_godlevskyi@epam.comJS Developer

Yurii Danilenko

yurii_danylenko@epam.comJS Developer

Maksym Dryha

maksym_dryha@epam.comJS Developer

Victoria Rabykina

victoria_rabykina@epam.com

Scrum Master


Team Calendar




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 Hints


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