Download as PDF, PPTX
Uploaded bySreeram Kishore Chavali
Quality myths
The document discusses common myths in quality assurance and provides guidance on effectively debunking myths. It defines a myth and explains why discussing myths is important for the profession. The most critical myths include definitions of quality and beliefs that automated testing eliminates manual testing or that testing requires coding skills. To debunk myths, one should present key facts without overkill, warn about false information, provide alternative explanations, and use graphics when possible. Quality assurance practices must be tailored to each specific project based on its technology, complexity, people, costs rather than following rigid processes. Factors like the type of software, industry, cost of bad quality, and a project's maturity level will impact quality approaches. Visual tools like matrices, quadrants and mind
More Related Content
![5G Explained! A High Level Overview [Introduction]](https://cdn.slidesharecdn.com/ss_thumbnails/5gexplainedahighleveloverview-260119165306-cc137a3e-thumbnail.jpg?width=640&height=640&fit=bounds)
Quality myths
- 1.
- 2. About Me QA StrategyConsultant QA Director - Satmetrix Senior QA Manager - Informatica Technical Manager - Ramco SystemsIndia - QA Winning Forumla: on SlideShare - Product Management and QA Collboration - Meetup April 2013
- 3. Myth Definition: An unprovedor false collective belief that is used to justify a social institution. Why Talk about these? - Pride in Profession - Bring Clarity - Establish realistic goals/objectives - Don't waste your career
- 4. Most Critical Myths Definitionof Quality Automated Testing eliminates Manual Testing Aim for 100% test automation Testersneed to know coding More...
- 5. Anatomy of aneffective debunking Bringing all the different threads together, an effective debunking requires: • Core facts—arefutation should emphasise the facts, not the myth. Present only key facts to avoid an Overkill Backfire Effect; • Explicit warnings—beforeany mention of a myth, text or visual cues should warn 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 why the myth is wrong and, optionally, why the misinformers promoted the myth in the first place; • Graphics – core facts should be displayed graphically if possible.
- 6. Sample Analogy No twoprojects are same: Technology,complexity,people, cost, effort Treat each variation of software projectas a variation of a medical condition Diagnose each projectcarefully. Find out similarities Find out differences Apply what worksbased on knownfacts Explore solutions for new challenges Don't force fit a process,team to follow a rigid process.Establish guidelines, goals and leave flexibility.
- 7. Establish Facts/Guidelines Don't cometo conclusion based on limited data and establish a broader rule Factors 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 of Operation e.g. Don't try to force a Start Up Practice on Mission Critical Software
- 8.
- 9.
- 10.
- 11.
- 12. Our role Actively addyourperspectiveto discussions that are myths Promote material that debunksmyths establish forums specific to yourdomain/situation.
- 13. Discussion Pick a topic Knowthe group: Role, Type of Software Develop a visual that bring clarity to 'Myth' - Grid - Quandrants - Mindmaps - etc.
- 14.