Six Sigma software industry import errors during interpretation, Six Sigma process with great success in the pipeline as well as hardware manufacturing process, the results so that the software industry himself, began to implant Six Sigma software, but a few years later, looking back Six Sigma does not seem to bring any gains to show for our software in this site.
So Six Sigma implant it really was a mistake? Definitely not! At present due to misinterpretation of their Six Sigma in the software industry in the embarrassing situation to a large extent, I've listed some common mistakes, and we resolve together.
Myth 1: Six Sigma can only measure the defect density of
software organizations in the implementation of Six Sigma projects are plagued by three basic questions:? "? How to calculate Sigma" "What is the defect (defect)" What are the chances? "Because there are data, many software organizations only with Sigma defect density as a measure they ignore a simple fact: only defect density metrics development process, is not equivalent to the user to use the software product satisfaction if the defect density process. the measure can not be the end user is linked, then the measure of significance is not great.
Myth 2: Only with software organizations CMMI High Maturity of Six Sigma in order to use
this misunderstanding comes mainly from the limitations of Six Sigma understanding, in fact, when you understand the essence of Six Sigma, you will find it and CMMI1.3 of GPs and the CMMI2.0 GOV II and is also closely related, as speaking in front of Enabling Project Six Sigma. In fact, many of the concepts of Six Sigma principles, methods that can help any level of software organizations.
Myth 3: Six Sigma is only using statistical techniques of
Six Sigma (Sigma - which was the standard deviation) name is one of the causes of misunderstanding, eliminate variability is an important concept of Six Sigma, but not the only focus. Six Sigma approach also includes a number of non-statistical methods, but these statistics and other analytical tools, Six Sigma make a more complete, more meaningful.
Myth 4: Six Sigma can be effectively used for the entire software development process
Although the production of software products have their own process, but production lines and different. No two software product development process is exactly the same, and the same brand glass production process thousand million times are not any different. Innovation is the normal software development process, so the amount of data that a number of software sub-processes will not be great, which gives Six Sigma Improvement tremendous obstacles. When implanted Six Sigma software process, which should have been more concerned about the normalization of recurring events, such as assessment, various testing activities.
Myth 5: All Six Sigma projects must yield economic benefits
concerned about ROI, economic indicators are at a Six Sigma attraction, which also resulted in some people think that all Six Sigma projects must produce immediate economic benefits, the consequences are ignored for Six Sigma success of the project to establish the necessary support infrastructure. The Six Sigma software implanted in the process, organizations often need to put into the implementation of a so-called Enabling Project, organized as a strategic investment, continue to support follow-effective improvements. The idea of two practice fields and CMMI2.0 II and GOV are very similar.
Myth 6: sigma = CMMI four embodiments
only for evaluation requirements, Sigma floor and do not cover the establishment of high maturity CMMI architecture, Sigma CMMI is not equal to four.
Myth 7: Six Sigma is to improve the performance of the only goal of
many software organizations implement Six Sigma, the 6σ level of performance improvement targets as the ultimate goal, but ignored other important indicators associations and organizations, such as: profitability, response time, customer satisfaction, employee satisfaction, market share and so on. Measure is not an end, what kind of measure is not important, the key is to improve the investment ultimately reflected in the upgrade of core indicators. Elimination of variation (variation) should not be a software organization improvement goals, maximize the value will bring variation, loss minimization is the goal. Six Sigma will be implanted into the software process, be sure to keep that in mind!
Much of Six Sigma I'm very recognized. As the concept of quality costs, customers come from customers to the idea of a closed-loop method of improvement. The use of reasonable can be used in the improvement of the software process.