Smart QA Practice
Customer issues slowing your rapid development cycle? Technical debts swamping your effort? Want to sharpen your QA practice?
To enable engineering to deliver more features, not just fix issues?
Testing slowing you down?
Think automation will fix it?
Well it takes more than that.
It is not about being faster, to do more testing, it is the opposite.
It is not about uncovering more technical debt, it is the opposite.
It takes human intelligence with machine assistance to be effective, efficient and preventive.
Uncover key issues, quickly and early. It is about doing SmartQA .
“Do less. Accomplish more”.
Ok, how is my practice?
What are typical solutions and their challenges?
#1 Regress frequently. Automate.
Certainly helps to ensure health is not compromised by frequent changes.
But, is that good enough? After all, automated tests execute the same path and cannot find newer issues.
#2 Do more unscripted testing.
Certainly helps to dig into context and do better testing.
Is it good enough? Well, when it veers into ad-hoc testing, efficacy may not be as good it should be.
#3 Strengthen process with tools.
Certainly helps to relook at process, tighten and streamline it.
Is it good enough? Well process is great, but it is the practice that is key to brilliant outcomes.
How can we help?
Strengthen your test design practice to lower escapes
Augment practice with Immersive Session Testing to test rapidly
Enable in-sprint automation to check rapidly
Sharpen practice with measures to steer continuously
Help you do less by organising & leveraging assets
Case studies
“Transform QA practice
to better, faster & lesser“
leading to lower defect escapes in seasonal releases, enhanced visibility of quality/risks to management and improved pride & ownership by QA.
“Enhance coverage,
reduce escapes“
to find dormant issues that would have otherwise derailed certification, improving code coverage by 10+% on a well tested embedded system code.
“Find issues early
via brilliant dev tests“
to enable smooth integration of components developed by various teams and rollout large applications with low cutover risk.
“Reduce testing
to deliver rapidly”
by untangling test assets to optimise regression. Setup clear scope of dev and QA test, simplify documentation to ‘write less, think better & do smarter’.
So, how does this work? – Engagement model
ASSESS & PLAN
Discussions with senior management to understand problems/expectations
Deep dive into process & practice via interviews, survey & walk-thru of assets
Publish assessment report, the current baseline
Outline actions, timelines, support needed
DO & TRANSFORM
SmartQA orientation- Masterclass for all Product owners, Leads/Mgmt, Dev & QA
Discuss and agree on transformation action plan
Weekly coaching/mentoring/doing sessions for all teams
Publish tips/guidelines/sample documents to aid transformation
Sprint wise data collection & analysis, weekly review
CONCLUDE & SUSTAIN
Publish improvements referenced against the baseline
Identify champions for sustaining this the next SIX months
Publish cheat sheets for Dev, QA, and management of agreed upon practice
Publish metrics to steer and to measure outcomes
Do you face these challenges?
Grappling with too much testing?
Challenged by test adequacy?
Troubled by development test?
Weighed down by automation?
Testing slowing you down?
Yes, I would like to discuss
