Printable View
ISO 9000 : dirty Water purified only when audit comes.. again will become dirty, it will be purified few days before audit.
CMM : dirty water purified only once... wait untill client gets a feel that we are using dirty water.. again purify starts..
Six Sigma :dirty water purified once and kept in control..
Nice definitions. :thumb:Quote:
Originally Posted by santoct2002
Please explain by short how keeps Six Sigma under control the purified water.
It has DMAIC and DFSS to keep track every SigSigma PROCESS , You can get more details in following page..Quote:
Originally Posted by ovidiucucu
http://www.isixsigma.com/dictionary/DMAIC-57.htm
But also ISO 9001:2000 states the PDCA (Plan Do Check Act) cycle, that can keep the water clean between two audits.Quote:
Originally Posted by santoct2002
Well, as I know, ISO9001:2000 introduces also the notion of "zero defects".Quote:
Originally Posted by Mick
But we cannot say that every bug in a software product is a defect.
Maybe at one moment the caption of your medical application can irritate few old nurses when upgrading the hospital computers OSs from Windows 2000 to XP. This is not a defect, it's just a nonconformity that can be easely fixed.
You and another individual seem to be missing my point. I think maybe people need to pause and try and differentiate between opinion and fact. There is a big difference between reading about it and being responsible for implementing it. Getting a group of 'sensitive' developers to take responsibility for defects in their code has always been met with resistance in my 15+ years of experience.Quote:
Originally Posted by Hokutata
It is a pet peeve of mine so I hope that clears it up for you guys. If not, it still doesn't change the facts that I have observed whether in management at the time or one of the developers being asked to buy into following the guidelines.
Maybe they just cut east coast developers out of a different mold and your mileage will vary. :p
I came to work and tore off the page of my 2004 Dilbert desk calander. It's Dogbert talking to the pointy haired boss:
Dogbert: You've got to implement a six sigma program or else you're doomed.
Boss: Aren't you the same consultant who sold us the worthless TQM program a few years ago?
Dogbert: I assure you that this program has a totally, totally different name.
Boss: When can we start?
Just thought it was an amusing coincidence.
Jeff
Defect "management" is always an interesting topic. There is so much hype that real issues often get overlooked. Just a few notes:
1) An error in something (such as a peice of code) is NOT a bug or defect, DURING THE TIME IT IS IN DEVELOPMENT. It becomes one when either of the following occurs:
a) The test plan for this phase is not sufficient to catch the error
b) The test plan is not properly executed.
If a test is executed within a phase catchs an error, and the error is corrected without the project leaving that phase, then this is merely another cycle of the local iterative process.
The first can be dealt with by having an iterative test process and a good grasp of CDRIL principals [internal analysys to determine the set of stimuli that is needed to exercise all possible operations]. The second can be dealt with only by a strong incentive policy known as "Keep your job".
2) One guarenteed way to avoid ALL errors and defects is to have no specification. If there are no requirements specifying what the program must/should/can do as well as those items which it can't/shouldn't do, then any operational behavour can not be deemed incorrect. :eek:
Just as an interesting note, my wife is the Senior administrative assistant to the global chief engineer of Underwriters Laboratories, which is one of the largest certification agencies in the world.
I've worked in a German company that dables in this. No, there are no more bugs. However, the number of bugs that are reported by the customer are greatly reduced.Quote:
Originally Posted by marsh_pottaye
But this generally happens: in every company/project the number of reported bugs decreases in time.Quote:
Originally Posted by YourSurrogateGod
At least in Europe, ISO9001 is pretty enough. It's a nonsense to try others, even googling "CMM" + "certified" + "India" (just for an example) you'll find tens of thousands of results.
Quote:
Originally Posted by micknustiunimik
What do you trying to convey here? I could not understand ? Why India? Why you are searching in Google?? ... I am not able to understand.. plz explain. :confused:
1. He/she said: "just for an example".Quote:
Originally Posted by santoct2002
2. What are you not able to understand why somebody is searching in Google?
Besides, if you do search using that query you'll find 13.800 results. This could mean that CMM is a fairly popular standard in India ( and also Pakistan from the results).Quote:
Originally Posted by ovidiucucu
That's pretty good, isn't it? :)Quote:
Originally Posted by PadexArt