TMMi: should you care? Step-Auto Conference 2013, Bangalore
•Télécharger en tant que PPT, PDF•
0 j'aime•844 vues
Keynote TPI on the Auto-Step Software Testing Conference, Bangalore India May 2013
Recommandé
Recommandé
Contenu connexe
En vedette
Similaire à TMMi: should you care? Step-Auto Conference 2013, Bangalore
Similaire à TMMi: should you care? Step-Auto Conference 2013, Bangalore (20)
Plus de SYSQA BV
Plus de SYSQA BV (20)
Dernier
Dernier (20)
TMMi: should you care? Step-Auto Conference 2013, Bangalore
- 1. TMMi: should you care? Step-Auto conference on test process improvement 3th May 2013, Bangalore
- 4. ©SYSQAAlmere Recent trends in system development 4
- 5. ©SYSQAAlmere Sometimes bad testing costs a lot
- 6. ©SYSQAAlmere declare vertical_veloc_sensor: float; horizontal_veloc_sensor: float; vertical_veloc_bias: integer; horizontal_veloc_bias: integer; ... begin declare pragma suppress(numeric_error, horizontal_veloc_bias); begin sensor_get(vertical_veloc_sensor); sensor_get(horizontal_veloc_sensor); vertical_veloc_bias := integer(vertical_veloc_sensor); horizontal_veloc_bias := integer(horizontal_veloc_sensor); ... exception when numeric_error => calculate_vertical_veloc(); when others => use_irs1(); end; end irs2; Ariane raket $ 15,5 billion = 840 billion
- 8. ©SYSQAAlmere Test Maturity Model integration 8
- 9. ©SYSQAAlmere TMMi – Maturity levels 9 1. Initial Managing a test project 2. Managed 5. Optimization 3. Defined Managing a test organization 4. Measured Measuring product and process performance Continuously improve product and process Q Test Policy and Strategy Test Planning Test Monitoring and Control Test Design and Execution Test Environment Test Organization Test Training Program Test Lifecycle and Integration Non-functional Testing Peer Reviews Test Measurement Product Quality Evaluation Advanced Peer Reviews Defect Prevention Test Process Optimization Quality Control
- 10. ©SYSQAAlmere TMMi has a positive impact on • Product quality • Test engineering productivity • Spend time • Lead time 10
- 15. ©SYSQAAlmere 15
- 16. ©SYSQAAlmere Allen curve 16 ‘The distance between engineers’ offices affected the frequency of their communication’ – Prof. Thomas Allen MIT
- 21. ©SYSQAAlmere 21
- 22. ©SYSQAAlmere TMMi: should you care 22
- 24. ©SYSQAAlmere Count the number of times the people wearing white pass the basketball 24 Please focus and be silent
- 25. ©SYSQAAlmere 25
- 26. ©SYSQAAlmere 26
- 27. ©SYSQAAlmere
- 28. ©SYSQAAlmere
Notes de l'éditeur
- Remember: attendance list needs to be filled in and handed over to HRM This version of the TMMi training is intended for both internal professionals of SYSQA and the external interested parties. It therefor should adhere to the TMMi Professional TMMi model training Release 1.0 guidelines The exam is multiple choice, 40 questions, pass rate is 65 % or higher (26 or more correct answers) Version control: V0.4: 14/12/2012 Changes after review (Roger Wouterse) V0.3: 10/12/2012 Color of all sheets set to SY”SQA standards, overall review on usage of language (Sietske Faling) V0.2: 05/12/2012 Added the Level 1 to Level 5 magerial to original setup of training (Bart Fessl) V0.1: 17/08/2012 Initial version, based on the Dutch internal SYSQA training “TMMi opleiding V2.8 “Roger Wouterse)
- Besparing: 30.000 testwerk
- 16 process areas On the initial level: chaotic, undefined test process. Foces mostly on debugging. “Heroes” organization, leaning on very good individuals by a lack of repeatable processes. Testing takes place in an ad-hoc fashion, after development is finished. No focus on risks or awareness of the higher risks. ‘overcommitted’. During times of crisis, all processes are abandoned. A lack in the abaility to repeat processes. Managed: testing becomes a separately managed specialism. Next to debugging, testing is viewed as a separate additional process. When there is a crisis, the testing processes are still folowed. Testing is still a phase after programming. The effort is focused using the knowledge of risks, leading to test plans and test approaches and strategies. Structured testing on a separate testing environment is introduced. Reviews and early involvemend are still lacking. Defined: fully integrated in the SD process. Test organisation is responsible for templated and guidelines. Repeatable and standardized way of testing for the whole company is introduced (where it used to be determined per project). Testing becomes a profession, test cases become re-usable, etc. Measured: well defined, trained, managed and measured process. Goals are set in a SMART way. Decsions are fact-based. Reviews and inspections are an integrated part of SD. Measurement is part of an organization-wide measurement program. Optimization: ongoing focus on test process improvemt, understanding of disturbances in the process in order to become able to predict and prevent these disturbances. Fine-tuning of the testing process. Focus on defect prevention, not detection.
- Summary of Business reasons why to implement TMMi By setting up the test organization in an effective and efficient way, it becomes clear that the goal for testing will change from defect detection to defect prevention. By using TMMi to (re)structure the testprocesses a better product and a higher ROI for the company can be realised.