Quality myths

327 views

Published on

Presentation used for discussion at Meetup on June 17 2013

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
327
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Quality myths

  1. 1. Debunking QualityMythsSREERAM KISHORE CHAVALI
  2. 2. About MeQA Strategy ConsultantQA Director - SatmetrixSenior QA Manager - InformaticaTechnical Manager - Ramco SystemsIndia- QA Winning Forumla: on SlideShare- Product Management and QA Collboration - Meetup April 2013
  3. 3. MythDefinition: An unproved or false collective belief that is used to justify a socialinstitution.Why Talk about these?- Pride in Profession- Bring Clarity- Establish realistic goals/objectives- Dont waste your career
  4. 4. Most Critical MythsDefinition of QualityAutomated Testing eliminates Manual TestingAim for 100% test automationTestersneed to know codingMore...
  5. 5. Anatomy of an effective debunkingBringing all the different threads together, an effective debunking requires:• Core facts—arefutation should emphasise the facts, not the myth. Presentonly key facts to avoid an Overkill Backfire Effect;• Explicit warnings—beforeany mention of a myth, text or visual cues shouldwarn that the upcoming information is false;• Alternative explanation—anygaps left by the debunking need to be filled.This may be achieved by providing an alternative causal explanation for whythe myth is wrong and, optionally, why the misinformers promoted the mythin the first place;• Graphics – core facts should be displayed graphically if possible.
  6. 6. Sample AnalogyNo two projects are same: Technology,complexity,people, cost, effortTreat each variation of software projectas a variation of a medical conditionDiagnose each projectcarefully.Find out similaritiesFind out differencesApply what worksbased on knownfactsExplore solutions for new challengesDont force fit a process,team to follow a rigid process.Establish guidelines, goals and leaveflexibility.
  7. 7. Establish Facts/GuidelinesDont come to conclusion based on limited data and establish a broader ruleFactors that determine variations in Software Quality discipline- Type of Software: Business Application, Embedded Software, Operating System, Mobile App, Games- Types of Industry: Internet, Healthcare, Insurance, Finance- Cost of Bad Quality: Mostly High but $$$ varies based on Maturity of business.- Evolving Vs Established: New Business, First year of Operation, 10 years of Operation, 30 years ofOperatione.g. Dont try to force a Start Up Practice on Mission Critical Software
  8. 8. Matrix Example
  9. 9. Quadrant Example
  10. 10. MindMap Example
  11. 11. Referenceshttp://softwaretestingfundamentals.com/software-testing-myths/http://en.wikipedia.org/wiki/List_of_software_categorieshttp://www.flickr.com/photos/softwaretestingclub/7579063452/sizes/o/in/photostream/http://www.flickr.com/photos/softwaretestingclub/8396776442/sizes/o/in/photostream/http://blog.smartbear.com/process/how-to-improve-communication-between-qa-and-development/http://www.skepticalscience.com/docs/Debunking_Handbook.pdfhttp://en.wikipedia.org/wiki/Software_quality
  12. 12. Our roleActively add yourperspectiveto discussions that are mythsPromote material that debunksmythsestablish forums specific to yourdomain/situation.
  13. 13. DiscussionPick a topicKnow the group: Role, Type of SoftwareDevelop a visual that bring clarity to Myth- Grid- Quandrants- Mindmaps- etc.
  14. 14. Recap/Wrap up

×