quality myths
DESCRIPTION
Presentation used for discussion at Meetup on June 17 2013TRANSCRIPT
Debunking Quality MythsSREERAM KISHORE CHAVALI
About MeQA Strategy Consultant
QA Director - Satmetrix
Senior QA Manager - Informatica
Technical Manager - Ramco Systems India
- QA Winning Forumla: on SlideShare
- Product Management and QA Collboration - Meetup April 2013
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
- Don't waste your career
Most Critical MythsDefinition of Quality
Automated Testing eliminates Manual Testing
Aim for 100% test automation
Testers need to know coding
More...
Anatomy of an effective debunkingBringing all the different threads together, an effective debunking requires:
• Core facts—a refutation 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—any gaps 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.
Sample AnalogyNo two projects are same: Technology, complexity, people, cost, effort
Treat each variation of software project as a variation of a medical condition
Diagnose each project carefully.
Find out similarities
Find out differences
Apply what works based on known facts
Explore solutions for new challenges
Don't force fit a process, team to follow a rigid process. Establish guidelines, goals and leave flexibility.
Establish Facts/GuidelinesDon'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
Matrix Example
Quadrant Example
MindMap Example
Referenceshttp://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
Our roleActively add your perspective to discussions that are myths
Promote material that debunks myths
establish forums specific to your domain/situation.
DiscussionPick a topic
Know the group: Role, Type of Software
Develop a visual that bring clarity to 'Myth'
- Grid
- Quandrants
- Mindmaps
- etc.
Recap/Wrap up