SOFTWARE DESIGN FOR SIX SIGMA (DFSS): A PRACTICAL GUIDE FOR SUCCESSFUL DEPLOYMENT - Software Design for Six-Sigma: A Roadmap for Excellence - page 227

Gen 0
“As Is”

Gen 1
120 days

Gen 2
6-12 months

Use DFSS to create
Standard process with
scalable features that
provide a framework
to migrate to future
state

Evolve process into SAP
environment and drive
20% productivity
improvement

VISION

METRICS

L - 40 hrs

M - 20 hrs

Touch Time
Cycle Time
Win Rate

Same

unknown
Manual 1-20 weeks

S -
Manual 3-10 days

10 hrs

Automated

Unknown
Unknown
Unknown
Unknown

Measured

Automated
Accuracy

Accuracy

Accuracy
Completeness Completeness

Win Rate
Compliance
Auditable/
Traceable

Completeness
Win Rate
Mistake proofed
Mistake proofed

Win Rate
planned
planned

hope

hope

SCOPE

Service 1 Service 2

FIGURE 9.7 SAP software design multigeneration plan.

for successful DFSS deployment. The algorithm works as a compass leading Black
Belts to closure by laying out the full picture of the DFSS project. We would like to
think of this algorithm as a recipe that can be tailored to the customized application
within the company's program management system that spans the software design
life cycle. 6 Usually, the DFSS deployment team encounters two venues at this point:
1) Develop a new program management system (PMS) to include the proposed DFSS
algorithm. The algorithm is best fit after the research and development and prior to the
customer-use era. It is the experience of the authors that many companies lack such
universal discipline from a practical sense. This venue is suitable for such companies
and those practicing a variety of PMS hoping that alignment will evolve. 2) Integrate
with the current PMS by laying this algorithm over and synchronizing when and
where needed.
In either case, the DFSS project will be paced at the speed of the leading program
from which the project was derived in the PMS. Initially, high-leverage projects
should target subsystems to which the business and the customer are sensitive. A sort
of requirement flow-down, a cascading method should be adopted to identify these

6 The design life cycle spans the research and development, development, production and release, customer,
and post-customer (e.g., software and after market).