How to implement quality

453 views

Published on

How To Implement Quality
by Iryna Pylypchuk


Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
453
On SlideShare
0
From Embeds
0
Number of Embeds
43
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

How to implement quality

  1. 1. How To Implement QualityIryna Pylypchuk
  2. 2. Where to start?
  3. 3. Where to start? • Analysis ▫ Learn the product ▫ Review the documents ▫ Ask the questions ▫ Identify the risks
  4. 4. What is next?• Planning ▫ Scope ▫ Approach ▫ Resources
  5. 5. What should be defined?
  6. 6. Why do we need testing?• Detect errors in a software product• Conformance to requirements• Establishes confidence• Evaluates quality attributes
  7. 7. When to start testing?
  8. 8. What is necessary to be tested?
  9. 9. How to perform testing?• Define testing approach• Follow test policies• Periodically review the process• Document workflows• Follow standards
  10. 10. Where testing should be performed
  11. 11. Who will perform testing?
  12. 12. QC Team• Smart• Free to express their feelings• Enthusiastic• Ambitious• With a shifted leadership• Creative• Result oriented• Interested in achieving common goal
  13. 13. Team Work
  14. 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. 15. Teamwork is also an individual skill• You must be: ▫ Willing to find problems ▫ Own the problem ▫ Solve the problem
  16. 16. Collaboration with the customer
  17. 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. 18. What documentation does matter?
  19. 19. What documentation does matter?• Requirements• Test Plan• Test Design Specification• Test Case Specification• Defect Reports• Test Summary Reports• Sign Off Checklist
  20. 20. What provides direction?
  21. 21. Intuition based or…
  22. 22. …or Data based
  23. 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. 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. 25. What about self development?• Learn from others• Look for greater results• Share your knowledge• Participate in webinars/seminars/trainings/IT Weekends …

×