Technical practices to share
Download as PPTX, PDF0 likes59 views
This document discusses practices that can help increase project success, including requirements analysis, reviews, and exploratory testing. It outlines an agenda covering technical practices, testing as a decision, requirements analysis, requirements reviews, and exploratory testing. Requirements analysis and reviews are recommended to identify defects without executing code. Exploratory testing should be dynamic, focused on changes, and time-managed to test concepts without a script. Proper practices and management are key to project success.
Technical practices to share
- 1. A way to succeed Bassam Al-Khatib
- 2. Will talk about the following Choose your testing cycle Requirements analysis and reviews Custom projects test should be explored 2 Project Success
- 3. Agenda 1.Introduction. 2. Technical practices necessity. 3. Testing is a decision. 4. Requirement Analysis. 5. Requirement Reviews. 6. Exploratory Test. 3
- 4. 1.Introduction Practices and activities are dynamic. Good practices are needed to increase the success of project. Good management for the applied practices is a key point. 4
- 5. 1. Introduction Good practices are selected according factors like: 1. Project conditions . 2. Type of requirements. 3. Due date. 4. Amount of code changed. 5
- 6. 1. Introduction Factors – Continue. 5. Expected risks. 6. Testing scope. 7. Tester`s experience. 8. Testing types. 6
- 7. 1. Introduction I will identify the following practices: 1. Requirements analysis. 2. Requirements Reviews. 3. Exploratory Test. 7
- 8. 2. Technical skills necessity New practices help to improve testing life cycle activities. 8
- 9. 3. Testing is a decision 9
- 10. 5. Requirements reviews According to the analysis you perform select the review type. Review should be according well designed checklist. 10
- 11. 5. Requirements reviews No need to execute code. Aims to identify defects and improvements 11
- 12. 5. Requirements reviews General objectives for requirement reviews: 12
- 13. 5. Requirements reviews For example the scope of a requirements review will for "Eurofins 8.0e Training Requirements Management" : - Detect the exact behavior of the new changes of the training application and their side effects. - Address both functional and nonfunctional requirements. 13
- 14. 6. Exploratory Test Test should have the concept. 14
- 15. 6. Exploratory Test Should be dynamic. Should be feasible and time managed. Should be close to changes areas. 15
- 16. Thank You! 16