Team
Taras Spashchenko | Technical Product Owner Solution Architect | |
Yogesh Kumar | Product Owner | |
Oleksandr Haimanov | DevOps Engineer | |
Sergii Masiuk | sergii_masiuk@epam.com | DevOps Engineer |
Oleksii Petrenko | Scrum Master | |
Eldiiar Duishenaliev | DevOps Engineer | |
Arsen Atoyan | DevOps Engineer | |
Dmytro Moroz | DevOps Engineer | |
Yaroslav Ishchenko | yaroslav_ishchenko@epam.com | DevOps Engineer |
Team Calendar
Vacation policy
Folio - Vacation Policy - EBSCO/EBS-CRDI - EPAM Knowledge Base: (broken link, fixing)
- Plan your vacation for three months ahead. Only exceptional vacation is acceptable without PO approve.
- Your vacation should not exceed two weeks.
- If you don't know exact dates – just highlight number of days to evaluate Team capacity.
- If during the desired vacation period we have two previously approved vacations of other members of the same team, the vacation may be not approved. It is valid for the team of up to 8 developers, if you have more than 8, it is OK to have tree and more parallel vacations in proportion. The precedence for intersections is defined on FIFO (first in, first out) basis.
- Small deviations are possible (health or family issues) but they should be clarified personally with your SM.
- Send Vacation Request to your SM. SMs should check if there are any concerns about the requested dates (overlapping with other vacations in the team, length of vacation, planned releases), clarify vacation dates with POs and if no objections (it does not affect delivery and limitations of the current policy), confirm vacation as approved. For any edge cased - consult with DM.
- After Approval - fill the desirable dates period in corresponding team's calendar in Ebsco Confluence.
- Create Vacation Request on vacation.epam.com and attach email with approval.
- Click Leave For Vacation when it will be the first vacation day.
- Click Mark Arrived when the vacation is ended.
Vacations are stored in Kitfox Calendar.
Some other useful info
Resources
- Kitfox SB (DevOps SB) Kitfox Board
- How to get started with Rancher environment
- Manage Performance Testing environments
- Manage Scratch Environment ver 1.2
- Rancher Environments
- For issues regarding reference environments see: FOLIO DevOps
- Sprint Review/Demo/Planning (Vega)
- Sprint review (Demo)
- Sprint retrospective
- FOLIO-3372 vs OKAPI-1061
- Kitfox workload
- Lotus (R1 2022)
- Lotus (R1 2022) Bugfest environment preparation plan
- Roles and responsibilities
- Data migration process
- Bug Fest R1 2022 Lotus
- Morning Glory (R2 2022)
- Lotus bugfest - Reindex resolution
- Unified pipeline NG Roadmap
- Bugfest modules' requirements
- Points of contact