I am a software tester, I want to share my test experience about "How Six sigma is beneficial for a QA/tester?"
We should admit ,with limit of our recognition, we can't do things perfectly in first place, we have to improve it again and again.
So we have to define our goal, quality goal, that will guide us how to improve.
even if Linux kernel development was not perfect too, the developers have to refactor again and again. but what their goal is ? there must be a goal, sometime is throughout, timing and so on.
When I was in charge of android updating feature, without knowledge of 6σ， I just focused on the test cases execution passing rate.
With the knowledge, I focused on the android updating quality.
I use DMAIC process in 6σ to define android updating quality.
first, what should be the android updating quality?
I thought it should be :
- stable, everyone should update their phone successfully.
- reliable, even if the failure occurs, they can recovery.
- support many updating ways, the developer, user, producer can get their device updated.
- cheap, the updating file should be small, the fee to updating devices should be cheap in storage and transfering
- smart, the updating should be smart, it can do updating at spare time.
- in time, the emergency updating should update in time.
- maintainable, it should be very easy to get failure logs without having phone in hand
[Develop KPIs to measure Quality[
then I start to develop KPIs to measure quality goals
for example, use big data to monitor stability, automatically calculate reliability and so on
[Start Analysis what I did not enough]
by analyzing those data, I can find what I missed
invent some test patterns to improve the test quality and so on
let the new test patterns / tools in production
I think that's the power of 6σ:
let me think in quality
let me run Plan-Do-Check-Act cycle in right way more faster
let me use fancy charts of quality that will make your leader think you are