1. 1 WKSC-NJD. PDS in Action. Customer focus By Andrei Telegin and Aliaksandr Dranitsa AUGUST 4, 2015

2. 2 Scene of action The Start What EPAM Team did The Outcome Agenda

3. 3 ‘1C’ like system For US people: Accounting Auditing Tax and Legal Project introduction

4. 4 1. Get PwC contract 2. Dominate on Scandinavia market 3. Aggregate all standalone applications in one “Studio” Business goals

5. 5 1. Customer is not very happy with the product they have 2. Customer is not satisfied with their development process. 3. No experience working with vendors Customer. Environment

6. 6 No QA Outdated technologies: Delphi etc. Code quality: spaghetti code, legacy code, not used code. Old DB’s, file based storages, and low performance. Old ‘unfriendly’ UI Performance Scalability Customer is not very happy with the product they have

7. 7 No solid vision what exactly they need and how should it work. Declared DSDM methodology. In reality waterfall. Performance of their development team. Constant deadline miss Customer is not happy dev process

8. 8 JanFebMarAprMayJuneJulyAugSeptOctNovDec ➜ Project start PM Architect ➜ Architecture creation Stream leads ➜ Start implementation ➜ Implement Viper/Delf functionality ➜ Client side functionality Studio Stream How it started: 2014 Viper/Delf Stream ➜ Server side functionality Cloud Stream

9. 9 Greenfield New architecture New set of tools Cloud Full UX redesign Technical challenges

10. 10 Customer doesn’t have in depth technologies understanding. Fixed schedule Customer tries to be proxy for all communications Communicational challenges

11. 11 Minsk team performs customer support beyond their dev. activities SDL trainings for Minsk team EPAM SDL Expert participates in all meetings MS CC help Quality Assurance CC consultation Agile CC consultation VALUE ADD CONSULTING CUSTOMER SDL TRAINING EPAM COMPETENCY CENTERS HELP

12. 12 “Minimize security-related vulnerabilities in the design, code, and documentation and to detect and eliminate vulnerabilities as early as possible in the development life cycle.” SDL – Goal

13. 13 1234 Major Steps to implement SDL Perform Assessment of Security Practices against SDL Initial Technical assessment, gap analysis Establish Security Practices for Requirements and Architecture Filling gaps on the level of analysis and management Establish Security Practices for Implementation and Testing Filling gaps on the level of implementation / testing Make security fixes for existing codebase Review, test and fix existing implementation

14. 14 Threat modeling tool

15. 15 CHECKMARX Report

16. 16 Beta 1 and Beta 2 Releases were delivered on time. Customer loved it. Implemented SCRUM, which formally complies to DSDM Now 100% of developers are EPAM employees. We got Customer TRUST. Results

17. 17 Ahead of the plan

18. 18 JanFebMarAprMayJuneJulyAugSeptOctNovDec RC1 ➜ ALL MUST’s are implemented RC2 ➜ MUST’s and selected SHOULD’s are implemented 1.0 Launch ➜ Deployed System Beta 1 ➜ Implement base functionality Beta 2 ➜ Implement PwC MUST’s ➜ Implement next MUST’s 2.0 RC1 Next Release schedule 2015 ➜ Run customer support Support

19. 19 1. Get PwC contract Got it! 2. Dominate on Scandinavia market Work in progress… 3. Aggregate all standalone applications in one “Studio” Done! Business goals