VIRBank Kristina Naudžiūnaitė Rita Birgelytė Daina Dirmaitė Andriy Voitenko Tadej Rola Vilnius 2018

VIRBANK PAY BILLS ONLINE SECURE LOANS WITHDRAW/DEPOSIT MONEY INVEST VIRBANK IS A VIRTUAL BANK WITH HEADQUARTERS IN LITHUANIA, VILNIUS, WITH OFFICES ALSO IN LATVIA AND ESTONIA VIRBANK OFFERS TRADITIONAL BANKING SERVICES ONLINE WITH NO DIRECT CUSTOMER ACCESS POINTS VIRBANK ENABLES CUSTOMERS TO: PAY BILLS ONLINE SECURE LOANS WITHDRAW/DEPOSIT MONEY INVEST

CUSTOMERS 790.452 13 76% 24% MAIN MARKETS: TOTAL CUSTOMERS FROM COUNTRIES 76% 24% PRIVATE CORPORATE MAIN MARKETS:

ORGANIZATIONAL STRUCTURE CEO PRIVATE CUSTOMERS BANKING BALTICS BANKING GLOBAL CORPORATES & INSTITUTIONS FINANCE & ACCOUNTING OPERATIONS SERVICES & IT AUTOMATIZATION ANALYTICS IT DEVELOPMENT IT INFRASTRUCTURE RISK MANAGEMENT AML RISK ASSESSMENT PROFITABILITY MANAGEMENT HR

HISTORY 2013 2014 - 2017 2018 - 2020 START UP FOUNDED FACING PROBLEMS NEW PAYMENT HUB VIRBANK STARTUP FOUNDED BY 5 DEVELOPERS WITH THE IDEA TO DISRUPT TRADITIONAL UNDERSTANDING OF WHAT IS BANKING THE SYSTEM WAS BUILT USING START-UP MIND-SET, FOCUSING ON OBTAINING FAST RESULTS AND WITHOUT LONG-TERM PLANNING AT THE TIME SYSTEM WAS BUILT THERE WAS A LACK OF BUSINESS, TECHNICAL KNOWLEDGE AND NO DOCUMENTATION WAS PREPARED. THEREFORE, ADDING NEW FEATURES NOW BECOMES AN ARDUOUS TASK TIME FOR CHANGES AND MOVE FROM AN OLD PAYMENT HUB TO A NEW ONE

6 80 PROJECT SET UP EMPLOYEES DIVIDED INTO DIFFERENT TEAMS APPLYING AGILE METHODOLOGY, SCRUM FRAMEWORK EACH DEPARTMENT HAS ITS OWN COMMITTEE THAT REPRESENTS BUSINESS NEEDS, WHILE SERVICES & IT DEPARTMENT IS RESPONSIBLE FOR IMPLEMENTING THE PROJECT 2018 2 YEARS LONG PROJECT 2020

PROJECT SCOPE DELIVERABLES: Project documentation, Progress reports, Issues reports, Weekly meeting notes EXCLUSIONS: Development of COTS, Testing: Unit testing, Functional testing SUCCESSFULL: If less than 6 minor, 3 major AND 0 FATAL FAULTS, during 1st month of production + TIME AND BUDGET FRAME, CONSTRAINTS: Impossible to customize the system Remote work of support team

IT EMPLOYEES AND QUALIFICATIONS SOFTWARE ARCHITECTS 3 DEVELOPERS 15 5 SENIOR 6 REGULAR 4 JUNIOR TEST MANAGER TEST ENGINEERS 10 4 MANUAL TESTERS 6 AUTOMATION SPECIALISTS SECURITY SPECIALISTS 4 SYSTEM ANALYSTS PROJECT MANAGER 2

SPECIFIC REQUIREMENTS OF ANALYSED PROJECT THE NEW SYSTEM SHOULD PROCESS PAYMENTS IN LESS THAN 5 SEC. USERS SHOULD NOT EXPERIENCE MORE THAN 1 HOUR OF DOWNTIME WHILE UPDATING SYSTEM ON PRODUCTION ENVIRONMENT PAYMENT HUB HAS TO BE INTEGRATED GRADUALLY WITH EACH LEGACY SYSTEM COMPONENT AND FOLLOWED BY SUFFICIENT INTEGRATION TESTING

TECHNOLOGIES CURRENT SYSTEM: DATABASE: MICROSOFT SQL SERVER, MySql, MongoDB BACK-END: .NET C#, Java, NodeJS FRONT-END: HTML + BOOTSTRAP, CSS + LESS, REACTJS PROJECT MANAGEMENT TOOLS: JIRA + CONFLUENCE VERSION CONTROL: GIT, SVN AUTOMATION SERVER: JENKINS TESTING: SELENIUM WEBDRIVER INTEGRATION: .NET C# AND JAVA WILL COVER MOST OF THE INTEGRATION CASES JIRA + CONFLUENCE FOR PROJECT MANAGEMENT GIT – VERSION CONTROL

REQUIREMENTS FOR TESTING PROCESS CODE CONTRIBUTION: CONTRIBUTED CODE SHOULD BE REVIEWED AND ACCEPTED BY AT LEAST 2 SENIOR DEVELOPERS (CRUCIBLE CODE REVIEW TOOL). BEFORE CONTRIBUTING, UNIT TESTS SHOULD BE RUN TEST COVERAGE: UNIT TEST COVERAGE SHOULD BE AT LEAST 80% INTEGRATION TEST COVERAGE SHOULD BE AT LEAST 90% TEST CASES SHOULD COVER 100% OF THE REQUIREMENTS GENERAL RULES: REGRESSION TESTING SHOULD BE AUTOMATISED AND MADE BEFORE EVERY RELEASE. SECURITY TESTING SHOULD BE DONE AFTER MAJOR CHANGES TO THE SYSTEM. PERFORMANCE TESTING SHOULD BE DONE REGULARLY.

REQUIREMENTS FOR CONFIGURATION MANAGEMENT PROCESS DATABASE BACKUP IS DONE EVERY NIGHT. 4 ENVIRONMENTS ARE USED: DEVELOPMENT, TESTING, STAGING, PRODUCTION. BUILD AND DEPLOYMENT IS DONE WITH JENKINS. CHANGES TO REQUIREMENTS AND DEFECT TRACKING IS DONE USING CONFLUENCE AND JIRA SOURCE CODE VERSION CONTROL IS DONE WITH GIT. FOR EACH CHANGE A NEW BRANCH IS CREATED, WHICH IS REVIEWED BEFORE MERGING WITH MASTER. 3 MAIN BRANCHES ARE USED: DEVELOPMENT, RELEASE, MASTER.

THANK YOU FOR YOUR ATTENTION!