Spitfire Development Team
Contents
Recent space activity
-
-
Data Import Traffics Diversion commented May 20, 2022
-
-
-
Data Import Traffics Diversion commented May 20, 2022
-
Data Import Traffics Diversion commented May 20, 2022
-
-
-
Data Import Traffics Diversion commented May 20, 2022
-
-
Meet the Team
| Khalilah Gambrell | kgambrell@ebsco.com | Product Owner |
Pavlo Smahin | Team Lead (Java) | ||
| Igor Gorchakov | Java Developer | ||
Viacheslav Kolesnyk | viacheslav_kolesnyk@epam.com | Java Developer | |
| Shans Kaluhin | shans_kaluhin@epam.com | Java Developer | |
| Yahor Sviarchkou | yahor_sviarchkou@epam.com | Java Developer | |
Denys Bohdan | denys_bohdan@epam.com | JS Lead Developer | |
| Mariia Sychova | mariia_sychova@epam.com | JS Developer | |
| Svitlana Korol | svitlana_korol@epam.com | JS Developer |
| Doniyor Otamurodov | doniyor_otamurodov@epam.com | JS Developer | |
| Priyanka Terala | priyanka_terala@epam.com | JS Developer |
| Dmitrii Vagin | dmitrii_vagin@epam.com | AQA | |
| Valery Pilko | valery_pilko@epam.com | QA | |
Natalia Zaitseva | Scrum Master |
Team Calendar
- EDIT THE CALENDAR
Customize the different types of events you'd like to manage in this calendar.
#legIndex/#totalLegs - RESTRICT THE CALENDAR
Optionally, restrict who can view or add events to the team calendar.
#legIndex/#totalLegs - SHARE WITH YOUR TEAM
Grab the calendar's URL and email it to your team, or paste it on a page to embed the calendar.
#legIndex/#totalLegs - ADD AN EVENT
The calendar is ready to go! Click any day on the calendar to add an event or use the Add event button.
#legIndex/#totalLegs - SUBSCRIBE
Subscribe to calendars using your favorite calendar client.
#legIndex/#totalLegs
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