SIX SIGMA FUNDAMENTALS - Software Design for Six-Sigma: A Roadmap for Excellence - page 165

Differences between SIx Sigma and Design For Six Sigma

Six Sigma Design for Six Sigma

DMAIC: Define, Measure, Analyze,
Improve, and Control.

DMADV: Define, Measure, Analyze, Design,
and Verify.

DMADOV: Define, Measure, Analyze,
Design, Optimize, and Verify.

Looks at existing processes and fixes
problems.

Focuses on the upfront design of the product and
process.

More reactive.
Dollar benefits obtained from Six Sigma
can be quantified rather quickly.

More proactive.
Benefits are more difficult to quantify and tend to
be more long term. It can take 6 to 12 months
after the launch of the new product before you will
obtain proper accounting on the impact.

FIGURE 7.15 DMAIC versus DFSS comparison. 4

today. The differences between the two approaches are captured in Figure 7.15. In
addition to ICOV, DMADV and DMADOV are used as depicted in Figure 7.15.
Unlike different models where the team members on a project need to figure out
the way and technique to obtain the data they need, Six Sigma provides a set of tools
making the process clear and structured and therefore easier to proceed through in
order to save both time and effort and get to the final goal sooner. Table 7.3 shows a
list of some of these tools and their use.

7.10 SOFTWARE SIX SIGMA

Jeannine Siviy and Eileen Forrester (Siviy & Forrester, 2004) suggest “Line of sight”
or alignment to business needs should be consistently clear and quantitative in the
Six Sigma process. “The ability of Six Sigma's focus on” should also be critical to
quality factors and to bottom-line performance to provide resolution among peers
with a similar rating and to provide visibility into (or characterization of) the specific
performance strengths of each. As an example, with Six Sigma, an organization might
be enabled to reliably make a statement such as, “We can deliver this project in

2%
cost, and we have the capacity for five more projects in this technology domain. If
we switch technologies, our risk factor is “xyz” and we may not be able to meet cost
or may not be able to accommodate the same number of additional projects.”

±

7.10.1 Six Sigma Usage in Software Industry

The earliest attempts to use Six Sigma methodology in development were considered
part of electronic design where mapping the Six Sigma process steps to the

4 http://www.plm.automation.siemens.com/en us/Images/wp nx six sigma tcm1023-23275.pdf.