O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Улучшение процесса разработки ПО для IT компании

369 visualizações

Publicada em

Доклад Юрия Мединского на Analyst Days-7. 13-14 октября 2017. Минск
www.analystdays.com

Publicada em: Educação
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Улучшение процесса разработки ПО для IT компании

  1. 1. OCT 13, 2017 WITH ROLES AND RESPONSIBILITIES EXPLAINED PROCESSES IMPROVEMENT FOR IT COMPANY
  2. 2. WHY I’M HERE? • Product Development, B2B, Market Penetration, Initial Phase • Are industrial standards (ProdBOK and BABOK v3) helpful • Which options do we have against PDLC • What we can and can’t achieve by implementing PDLC from scratch • Some numbers as an outcome aligned to approx. 80 FTE of worldwide product team (USA, UK, New-Zealand, Belorussia, Russia, Philippines) • Real mistakes and oversights • Alternative ways to avoid mistakes 1© EPAM 2017
  3. 3. REFERENCES 2© EPAM 2017
  4. 4. THE INITIAL IDEA • Product development life cycle • Release and scope management • Marketing and product strategy • Roles and responsibilities • Transparency and control • Risk Management 3© EPAM 2017
  5. 5. PRODUCT DEVELOPM ENT LIFE CYCLE 4© EPAM 2017
  6. 6. PRODUCT DEVELOPM ENT LIFE CYCLE 5© EPAM 2017
  7. 7. RELEASE MGT (HALF A YEAR PERSPECTIVE) M1 M2 M3 M4 M5 M6 M7 M8 M9 M10 M11 M12 Elaboration ➜Approved Business Requirement Documentation Functional Analysis ➜Project Implementation Architecture Documentation ➜Software Requirements Documentation Core Development and Testing ➜Deployed System, Sources ➜Issues in Defect Tracking System ➜Test Specification, Artifacts & Results Dev., Approval and Distribution of CAT Interface Public Specification ➜Draft CAT Interface Public Specification Update of CAT Interface Public Specification Based on Feedback ➜Approved CAT Interface Public Specification Integration of the System with SROs ➜SRO Rollout Schedule Rollout of the System for SROs ➜ System Deployed to Production ➜Test ResultsIntegration Testing Industry Testing, Forensic Analysis, and improvement ➜Test Results: Feedback to Participants Dev Infrastructure Build-out QA Infrastructure Build-out Prod Infrastructure Build-out for Exchanges and Market Data Int Infrastructure Build-out DR Infrastructure Build-out EXAMPL E 6© EPAM 2017
  8. 8. RELEASE MGT M1 M2 M3 M4 M5 M6 M7 M8 M9 M10 M11 M12 Release 001 Planning BA/UX Feature Development Regression Testing Go live Market Requirements Roadmap Release 002 Planning BA/UX … Strategic Planning Competitive Benchmarking Market Requirements Roadmap Release 003 Planning 7© EPAM 2017
  9. 9. RELEASE PLANNING PROCESS 8© EPAM 2017
  10. 10. FEATURE DEVELOPMENT PROCESS 9© EPAM 2017
  11. 11. CHANGE MANAGEMENT 10© EPAM 2017 Identify Negotiate Elaborate Estimate Plan Implement • Bug is something with customer would call a bug • We also need XYZ to be delivered • Urgent request from customer • Urgent demo with XYZ functionality included • I thought this feature already exists. Now this is our promise to the customer
  12. 12. MARKETING AND PRODUCT STRATEGY • Communication plan between Marketing, Product and R&D teams • Market events input and outcomes (IBM, Gartner etc.) • Market requirements •Market segmentation •Customer segmentation •Problem statements and mapping • Competitive benchmarking 11© EPAM 2017
  13. 13. MARKETING AND PRODUCT STRATEGY • Communication plan between Marketing, Product and R&D teams • Market events input and outcomes (IBM, Gartner etc.) • Market requirements •Market segmentation •Customer segmentation •Problem statements and mapping • Competitive benchmarking 12© EPAM 2017
  14. 14. PEOPLE TO CONTACT WITH Internal Users External Users END USER Those who use/will use the system UX CREATOR The main group of people who provide requirements UX • System Administrators • Methodologies • Auditors • Legal SIG Special Interest Group who provide constrains or constraining requirements against a solution BA SPONSOR A person who accept the solution against Market requirements and company strategy DM Product Team BA BA 13© EPAM 2017
  15. 15. BA UX COMPETENCIE S 14© EPAM 2017
  16. 16. THE FIRST CONTACT POINT BA TEAM BA TEAM 15 Stream 1 Stream 2 … Stream N BA TEAM © EPAM 2017
  17. 17. TRANSPARENCY AND CONTROL EXAMPLE 16© EPAM 2017
  18. 18. TRANSPARENCY AND CONTROL 17© EPAM 2017 Roadmap MGT Poor Planning Miss Estimation Lack of BA and MGT resources Miss Tracking 65 % of initial scope deliverable in HMW
  19. 19. GENERIC CONCLUSIONS • Scrum + Waterfall = "Watergile" • Industrial standards provide no clarity against specific cases (i.e. B2B + new product + existing market) • 65% accuracy is the only achievable thing for the first attempt • Feature completeness is negotiable (scope is not so strict) • Transparency and control requires at least 1 FTE per 20 people (it’s better to give a chance to PM) 18© EPAM 2017
  20. 20. LESSONS LEARNED • Marketing and product strategy is not something which you can 100% rely on dealing with new products • Release and scope management is not possible with poor tracking • Tracking requires a tool, skills and ‘religious’ usage • PDLC is not applicable if both (a) customer and (b) service provider have lack of experience 19© EPAM 2017
  21. 21. BA CAN DO THIS © EPAM 2017
  22. 22. THANK YOU © EPAM 2017
  23. 23. BA AND UX 10© EPAM 2017. PRIVATE & CONFIDENTIAL
  24. 24. BUSINESS ANALYSIS ACTIVITIES COMPUTE BACKLOG IN ITERATIONS • Requirements GAP exercise • Create, decompose and confirm Epics, Features, User Stories and Scenarios decomposition • Estimations: HLE, Sprint, Release • Prioritization: Features and user stories GAIN PRODUCT VISION AND SCOPE UNDERSTANDING • Problems/Benefits analysis • Solution dos and don’ts • Business Rules captured IDENTIFY BUSINESS NEEDS • Business processes and Data Strategy • Stakeholder goals and success criteria • Business User past and present tasks ESTABLISH REQUIREMENTS MANAGEMENT RULES RESEARCH AND DEVELOPMENT SUPPORT • Change management • Backlog playground rules • Sign off process • Requirements traceability • Real options • Sign off process 15© EPAM 2017
  25. 25. BUSINESS ANALYST UX & VISUAL DESIGN DEVELOPME NT ROLES AND RESPONSIBILITIES • Create and refine Backlog in line with Datawatch goals • Review Business User’s tasks and Opportunities • Implement continuous PDLC improvement approach • Support Features and User Stories prioritization • Increase transparency and control on the project • Analyze requirements and architecture constraints • Identify internal and external dependencies • Agree on solution components for the Datawatch product based on technical requirement • Define and document Datawatch technical architecture • Design solutions for planned Swarm Features. UI design • Design evaluation based on outlined goals and priorities • Information architecture • Build design consistency and product alignment with main product experience principles • Support shaping product vision 11© EPAM 2017. PRIVATE & CONFIDENTIAL
  26. 26. DESIGN INVOLVEMENT PHASES © EPAM 2017. PRIVATE & CONFIDENTIAL OPERATIVE TACTICAL STRATEGIC ISSUES TO COVER Design Quality Product Quality Teams Miscommunication Time to Market ISSUES TO COVER Risks Reduction Increase User Base Brand Support Decision Making Support • Cover design requests • Problem Based Tasks Approach • Design Evaluation • Analytics • Design Guidelines • Design Review • User Validation • User Validation • Product Principles • Co-design • Business-based KPI’s • UX Research (User-based) • Competitive Analysis • Design System • Deep Cross-team communication 12

×