Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Quality Requirement Management with Q-Rapids

1 view

Published on

Softeam use case presentation.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Quality Requirement Management with Q-Rapids

  1. 1. This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 732253. Quality Requirement Management With Q-Rapids Poznan – 18/02/2019 – 19/02/2019 Antonin Abherve
  2. 2. Softeam Use Case status overview Work performed during the last period Empirical Study Action Plan Remaining Issues Future Actions Plan Table of Context
  3. 3. Softeam use case status overview Specific metric to address QR Coverage
  4. 4. Monitoring the ModelioNG project Complete the Q-Rapids Dashboard deployment ( Forecasting service, qr-alert) Defined personalized row data Kibana dashboards Calibrate Quality Factors and Strategic indicators (weight) Development of the QG Generation Plugin to Open Project Initiate the direct feedback process using the on-line questionnaire Planification of the Empirical Study Process Work performed during the last period
  5. 5. QG Generation Plugin to Open Project Constraints – An automated tool can’t include new tasks in project plan. – Quality Requirement Issues can’t be ignored by the project manager without explanation. Softeam QG Generation Approach – Q-Rapids Platform generate a QR Item in Project workflow – The Project Manager can derive this QR in concrete task to solve the issue – Or justify why he decide to ignored this QR
  6. 6. Empirical Studies Planning 2019 Jan. February March April May June July Week 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 T2.3 Q-Rapids Process EasterWeek Workshop (Telco) Observation PE1/PE2 Interviews T3.5 Mitigation Activities Infernal Data Gathering Interviews (Telco) Validation Workshop (F2F) Other - Strategic Indicators BN SI (Telco) SI refining workshop (F2F) T2.3 Process Metrics Survey Gathering Data Iteration 1 Iteration 2 Iteration 3 Construction Validation Q-Rapids Evaluation SI Creation SI Refinement Softeam Empirical Study Action Plan
  7. 7. Softeam Constraint Direct Observation will not be possible du to our internal organization. Softeam propose to provide written feedback about the usage of Q-Rapids during internals management meetings (3 reports for the 3 iteration) Action Plan Week 6-7(February),10-11(March) and 17-18(May): 3 Workshop telco to verify in which way the partner companies are using and collecting the status of the progress in using Q-Rapids. Working Documents (3 Iteration) :Provide written feedback about the usage of Q-Rapids during internals management meetings. (End of February, end of March, mid May) Weeks 14-15 (April) : First F2F interview to examine how people applying Q-Rapids and perceive the transformation of your organization processes towards Q-Rapids. Weeks 21-22 (May) : Second F2F interview to examine how people applying Q-Rapids and perceive the transformation of your organization processes towards Q-Rapids. Q-Rapids Process 7
  8. 8. Softeam Constraint Standardised internal documentation related to Risk managements and mitigation action didn’t exist in Softeam. Softeam organize internal / unformal meeting to gather common practice applied in Softeam data related to risk management and mitigation action. Action Plan 28 February : provide documents which summaries common practice in Softeam related to risk management and mitigation action. Weeks 11 – 12 (March) : Organize a Telco to interview Softeam “Risk Managers”. If this first telco is not enough, a second could be considered. Weeks 21-22 (May) : Organize F2F validation workshops in Paris with the same actors. Mitigation Activities 8
  9. 9. Softeam Constraint Development of new metrics are limited by the availability of raw data We will have to work on the improvement of the quality of the existing metrics Action Plan Weeks 6-7 (February) : Telco dedicate to reviewing / study the extension of current set of metrics Weeks 14-15 (April) : First F2F meeting to review current metrics and get practitioners' feedback on the usability and the need to improve and/or add more metrics. Weeks 21-22 (May) : Second F2F meeting to validate improvements undertaken as a result first meeting and enquire if further improvements/additions are needed in process metrics. End of each months from January to May : Provide monthly a snapshot of collected metrics and an analysis report related to our evaluation of the quality of collected data Strategic Indicators BN 9
  10. 10. The quality of the metrics which are collected at this time has bean estimated not significant enough by end users Remaining Issues
  11. 11. Monitoring the Modelio 3.9 / 4.0 development process Execute the Empirical Study Action Plan Develop a couple of new OpenProject metrics dedicated to monitoring of Quality Requirement response to “Close the Loop” Work on the improvement of the quality the metrics which are currently collected Future Actions Plan

×