Presentation used for discussion at Meetup on June 17 2013

1. Debunking Quality
Myths
SREERAM KISHORE CHAVALI

2. About Me
QA Strategy Consultant
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 unproved or 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
Definition of Quality
Automated Testing eliminates Manual Testing
Aim for 100% test automation
Testersneed to know coding
More...

5. Anatomy of an effective 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 two projects 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 come to 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. Matrix Example

9. Quadrant Example

10. MindMap Example

11. References
http://softwaretestingfundamentals.com/software-testing-myths/
http://en.wikipedia.org/wiki/List_of_software_categories
http://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.pdf
http://en.wikipedia.org/wiki/Software_quality

12. Our role
Actively add yourperspectiveto discussions that are myths
Promote material that debunksmyths
establish forums specific to yourdomain/situation.

13. Discussion
Pick a topic
Know the group: Role, Type of Software
Develop a visual that bring clarity to 'Myth'
- Grid
- Quandrants
- Mindmaps
- etc.

14. Recap/Wrap up