How to implement quality
Download as PPTX, PDF0 likes387 views
This document discusses how to implement quality testing for software products. It outlines that quality testing involves analyzing requirements, planning the testing scope and approach, defining what needs to be tested, when to start testing, how to perform testing, where testing should be done, who will test, and the importance of documentation and metrics. It also emphasizes the importance of teamwork, collaboration with customers, and continual self-development.
How to implement quality
- 1. How To Implement Quality Iryna Pylypchuk
- 3. Where to start? • Analysis ▫ Learn the product ▫ Review the documents ▫ Ask the questions ▫ Identify the risks
- 4. What is next? • Planning ▫ Scope ▫ Approach ▫ Resources
- 5. What should be defined?
- 6. Why do we need testing? • Detect errors in a software product • Conformance to requirements • Establishes confidence • Evaluates quality attributes
- 7. When to start testing?
- 8. What is necessary to be tested?
- 9. How to perform testing? • Define testing approach • Follow test policies • Periodically review the process • Document workflows • Follow standards
- 10. Where testing should be performed
- 11. Who will perform testing?
- 12. QC Team • Smart • Free to express their feelings • Enthusiastic • Ambitious • With a shifted leadership • Creative • Result oriented • Interested in achieving common goal
- 13. Team Work
- 14. Team Work • How to cooperate? ▫ Create a collaborative climate ▫ Be open to others' ideas and suggestions ▫ Assume good faith ▫ Seek consensus ▫ Establish a communications system
- 15. Teamwork is also an individual skill • You must be: ▫ Willing to find problems ▫ Own the problem ▫ Solve the problem
- 16. Collaboration with the customer
- 17. Collaboration with the customer • Main principles: ▫ Review Test Approach with your customer ▫ Update with the progress ▫ Communicate the issues ▫ Confirm the changes to Test Strategy ▫ Be polite, honest and open
- 18. What documentation does matter?
- 19. What documentation does matter? • Requirements • Test Plan • Test Design Specification • Test Case Specification • Defect Reports • Test Summary Reports • Sign Off Checklist
- 22. …or Data based
- 23. Why metrics? • Metrics reduce arguments based on opinion • Metrics give you answers what really works • Metrics show where your strengths are • Bosses love metrics
- 24. Example: Simple Statistics • QA issues vs. customer tickets QA Customer • Issues found during UAT Enhancements UAT defects Data issues Existing issues Defects caused by enhancements
- 25. What about self development? • Learn from others • Look for greater results • Share your knowledge • Participate in webinars/seminars/trainings/IT Weekends …