1 / 16

QMS at FinAnalytica

QMS at FinAnalytica. Presented by Marian Dichev, MQA. SQA ?!?!. Software Quality Assurance What is this? Do we really need it? Whom it will help? Management? Developers? Clients?. History. Our experience so far… Why one year ago we failed? Why we think this time we will succeed?

talon-delaney
Download Presentation

QMS at FinAnalytica

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. QMS at FinAnalytica Presented by Marian Dichev, MQA

  2. SQA ?!?! Software Quality Assurance • What is this? • Do we really need it? • Whom it will help? Management? Developers? Clients?

  3. History • Our experience so far… • Why one year ago we failed? • Why we think this time we will succeed? • Why you are so important? • The reality in other companies….

  4. QMS ?!?! Quality Management System • What is this? • Do we really need it? • Whom it will help? Management? Developers? Clients?

  5. Our Dev Process as part of QMS • What is software development process? • What is the purpose of the process? • Types of processes? • What does our process regulate?

  6. Product Manager Project Manager Product Leaders – Constant role FoF Equity managers Risk Project Leader – On project by project basis Ronin trial setup Morley integration Etc. Technical Leader – Constant role Market Risk Scenario Generation Factor Models Bayesian Models Robust Models Credit Risk Sensitivities Stable models estimation and simulation Portfolio Optimizer Front-end, Charts and visualization Framework Data interfaces Big Calculators Instruments DB Performance Your role…

  7. Definition of roles • Product leaders are responsible for functionalities from the user view point • Product leaders are advised on the technical implication of a new feature by the Technical leaders • Technical leaders are responsible for technical aspects of the modules. • A technical leader should undertake a technical decision after consultation with all product leaders the product of whom is affected by the module of interest. • Project Leader is the person responsible for execution of the project: • Business Logic Document • Risk assessment • planning on each stage of development process • Monitoring and managing the project execution

  8. Evaluation Parties • Product manager • RD management • Senior Management • Client Benefits • We know better what we aim • We know if the project will pay out • We know better if the project corresponds to our Business strategy

  9. Preparation Parties • Tech Team (Project Leader, Product and Tech Leads, developers/mathematician) • QA • Product manager • RD management • Client Benefits • We build project team • Put more time and efforts in understanding the project • Many people are involved • Make as many iterations as needed • Limit the probability of future surprises

  10. Implementation And Testing Parties • Tech Team • QA • RD management • Client Benefits • We know the status of the ongoing project • We fix problems earlier • Update client earlier

  11. Delivery Parties • Tech team • QA • Product manager • RD management • Senior Management • Client Benefits • More time for special tests • Put client into Acceptance

  12. Postmortem Parties • ALL!!! Benefits • Share experience • Point out problems and achievements • Update QMS

  13. The Wind of Change… • More dynamic, structured and formal communication • More dynamic working style • New roles and responsibilities • New team oriented working style • New role of Client in Project lifecycle • Learn to write and follow procedures based on our own experience • Learn to respect others people work • Learn to have VISION about your work and the way you work

  14. Product Manager - Doug Project Manager - Todor Product Leaders – Constant role FoF - Dobri Equity managers - Niki Risk – Boryana Project Leader – On project by project basis Ronin trial setup - Dobri Morley integration - Yuri Etc. Technical Leader – Constant role Market Risk - Ivan Scenario Generation - Ivan Factor Models - Metodi Bayesian Models - Metodi Robust Models - Metodi Credit Risk - Georgi Sensitivities - Georgi Stable models estimation and simulation - Stoyan Portfolio Optimizer – Milen Front-end, Charts and visualization -Alex Data interfaces - Alex Big Calculators – Ivo Instruments – Nasko Framework, DB and Performance – Stan Web-Service – Dinko BeanDesigner - Stefan Your role…

  15. What does this mean for you for the next month or two? • Product Leader • Obtain knowledge of competitors systems • Obtain knowledge about work-flow of customers • Obtain knowledge about the needs of customer • Learn to communicate – client, senior management, RD team; learn to be the link… • Review and Update the user documentation on your product • Technical Leader • Obtain in-depth knowledge of your Cognity module • Obtain in-depth knowledge of what competitors do • Learn to communicate • Review and update the technical documentation on your module • Project Leader • Learn to understand the clients need • Learn to put them into our framework • Learn to communicate – oral, written, etc… • Learn to lead a project, but also to lead people • Learn to coordinate, Learn to monitor, Learn to make fast decisions, Learn to prioritize • Learn to see the entire plan, but also the important details

  16. Q&A • Will this increase the time for delivering new modules/features? • Is specification writing and reading useless and just time wasting procedure? • Is accurate planning at all possible? • Other…

More Related