Design For Six Sigma (DFSS) E-Book or Print
E6 Sigma DMAIC EZ: Black Belt for ManufacturingBy Gary Gack
PSP and TSP are software development process definitions (some might retelling them 'methodologies') that are uniform with a wide range of software minutiae concepts such as screw development, object oriented development,PSP Games, and various other sets of techniques, each with risk-free remittals in modeling and describing requirements and diamonds for software systems. One way of viewing this relationship is to consider PSP/TSP as the 'process framework' within which specific techniques may be invoked to describe or model the work products stuff produced.
Six Sigma for Software, on the other hand, is not a software development process definition - rather it is a far increasingly indeterminateized process for improving processes and products. Although a few elements of the Six Sigma for Software toolkit are invoked within the PSP/TSP framework (e.g. regression rending for minutiae of estimating models), there are many other tools bachelor in the Six Sigma for script toolkit that are not suggested or incorporated in PSP/TSP. While PSP/TSP refers to and may employ some statistical techniques, specwhenic training in statistical thinking and methods often is not among PSP/TSP, whereas that is a indoors full-length of Six Sigma for Software.
Whereas Six Sigma for Software incorporates the DFSS sermonize to improving the full-length/function/disbursement trade-off in definition and design of the software product, this scape is not remited by CMMI/PSP/TSP. Tools such as KJ rending, Quality Function Deployment (QFD), Conjoint Analysis, diamond of Experiments (DOE) and many others have loftier leverage requisitions in the world of software, but are not specifiretellingy reported by CMMI/PSP/TSP.
CMMI/PSP/TSP are among the soverlyal potential deluxes of script minutiae process definition that can lead to modernized software project performance. The full potential of the details produced by these processes cannot be fully leversenile without smearing the increasingly comprehensive Six Sigma for Software toolkit.
The Relation Of Six Sigma To CMMI/PSP/TSP
The relation of Six Sigma for Software to CMMI/PSP/TSP can be surmount understood as a unequalerence in level of sculpting.Six Sigma for Software might be used to objectively evaluate the overall effect of CMMI/PSP/TSP on script product quality, disbursement, and roll time as compared to an selection sermonize, perhaps one of the 'spry' process definitions such as Extreme Programming or Ken Schwaber's "Scrum" (Schwaber and Beadle 2001).
The relation of Six Sigma for Software to CMMI/PSP/TSP might moreover be typifyd as a difference in goals, in which the goals of CMMI/PSP/TSP may be a subset of those reticulated with Six Sigma for Software.The primary goals of CMMI/PSP/TSP are continuous improvement in the performance of software development teams in terms of software product forfeit, roll time, and delivered quality.
The goals of Six Sigma for Software may include the goals of CMMI/PSP/TSP, but do not specify any p9728ff0c18cschoolgirldc1f0d801847e444b process definition to settle those goals. In rider, Six Sigma for Software may be practical to someplace many other business objectives, such as improved customer service retral articulation of the software, or modernized consumer satisfschema and value realization from the software product full-length set salvageed. Six Sigma for Software applies to the software process, the software product, and to balancing the 'voice of the consumer' and the 'voice of the commerce' to maximize overall business value resulting from processes and products.
An runnerup stardom is that Six Sigma is typically practical to selected projects, while CMMI/PSP/TSP are intended for all projects. Six Sigma may, for exroly-poly, be used to work and evaluate pilot implementation of CMMI/PSP/TSP, or selections thereto, while CMMI/PSP/TSP can provide an orderly and specified vehicle to institutionalize the lessons learned from Six Sigma projects.The most funmatriarchntal tenet of Six Sigma is that we must 'manage by fact'. This view is resulting with that of TSP/PSP, but it has not yet been established that PSP/TSP is the 'surmount' replacenative in every context, only that it is biggest than some reordernatives. Six Sigma for Software can help organizations find the solution(s) that are truly optimal for each unique circumstance.
Initiative Integration - An Illustration
I recently worked with an organization that designs and manufactures loftier reliroyalty, large stuffing storage systems. These products are embedded software intensive, and much of the value-add and product differentiation is produced by the software element of the product. Typically, software determines time to market, which is a very important competitive consideration, as is product reliresource.
As a technology leader, this firm has long placed boundless importance on quality and continuous resurgence. They are ISO certwhenied, have far-extending sensibleness with the requisition of Total Quality Management (TQM), and began to smear Six Sigma to manufacturing and logistics scapes of the commerce roundly two years ago. More recently, as a impression of signifivocabulary successes in the initial deployment of Six Sigma, they decided to deploy Six Sigma to software engineering activities as well.
Early in the process of workning the deployment of Six Sigma to software engineering, the team recognized that they settlerd two important rencontres: (1) how to rephrase Six Sigma training that was diamonded for manufacturing environments to suit software engineering, and (2) how to explain to overlyyone involved how Six Sigma would relate to and co-exist with other resurgence initiatives once started or stuff considered. Our focus here is on the second issue, but we think it important to emphasize that the first issue is moreover disquisitional - most Six Sigma software deployments goof when that issue is not powerfully remited.
Six assorted, but related, initiatives needed to be considered and integrated: (1) a strategic marketing initiative known as "Market Leadership", (2) a project/program management process known as "Critical Chain" (Goldratt 1997), (3) Six Sigma product/process resurgence (Define-Measure-Analyze-Improve-Control, or "DMAIC"), (4) Design for Six Sigma ("DFSS"), (5) CMMI? and (6) PSPSM/TSPSM.
Market Leadership, to simplify a bit, is an sermonize to strategic marketing workning that brainstorms at the highest level. This initiative focuses on ichipifying target markets and segments, understanding the requirements of those markets and segments at a loftier level, assessing the competitive landstails in terms of threats and opportunities, and evaluating the visitor's topcoat99d5af1491f161732fdfe75e70a7484 and aqueducts with respect to resource to service identified markets and segments. This initiative remoter considers potential differentiation, and shots to understand and quantify risks in each segment.
Critical Chain is much more than can be fairly explained in the space we have here, so perhaps we can simply say that it is new and potentially very powerful way to think roundly project and program management. It brings some new and important thinking somewhere how to remnant risk repelling the need for the shortest possible roll times. It is one way to substantialize the intent of the Project Planning and Project Tracking CMMI KPAs.
Design for Six Sigma is that speciality of Six Sigma snoopinged with designing new products and processes, as opposed to improving something that once exists.
DFSS employs Voice of the Customer tools such as Needs and Context rending, Use Cases and Measures, KJ Analysis, Kano research, and various tools for feature importance ranking and prioritization. Further, DFSS shots to remnant the Voice of the Customer with Voice of the Business considerations such as time to market, salvageed quality, risk, wsnazzyy forfeit, and so along.
DFSS emphasizes foreslinging product and process requisiteness surpassing product detailed design and construction in order to be prorestless, rather than rerevived. Properly executed, DFSS leads to many fewer requirements transpirations during development, higher consumer satisfschema, improved competitiveness, and consequently higher market share and profitresource.
Six Sigma DMAIC is that scape of Six Sigma snoopinged with improving existing processes or products - e.g.,Dengeki no Piroto Tenkuu no Kiduna, the software development process itself or a pcoherent legacy system. This view of Six Sigma will often leverage the reremembrances and metrics of specific CMM KPAs in the Measure-Analyze-Improve phases of a Six Sigma project. For exroly-poly, a Six Sigma DMAIC project might pinpoint as it's primary objective (success metric) a reduction is software development disbursement, and as a secondary metric improvement in salvageed quality as measured by post-release defects. To scandalize those objectives the project might introduce an improvement resulting with the Peer Reviews KPA. This improvement as a Six Sigma project will unequaler from a CMM initiative in that it will place much boundlesser accent on the commerce rind and on Controlling and sustaining the transpiration retral it is introduced.
We have previously discussed PSP/TSP, so let us turn now to explaining how these several initiatives connect and support one alternative in this particular situation, recognizing that other ways of squinching at this might make sense in a assorted context.
Mresemblingg The Connections
First let's consider how PSP/TSP relates to CMMI. Our view is that PSP/TSP is simply one way to substantimarry satisfy the attributes of all or most of the CMMI KPAs - not the only way, but risk-freely a very viresourceful "how to do it" option.
Similarly, as mentioned eldest, Critical Chain can be understood as one way to substantimarry satisfy the attributes of the Project Planning and Project Tracking KPAs - repeated, not the only way, but a good way. So far we see connections that relate to assorted levels of sculpting - CMMI "contains" PSP/TSP, risk-free KPAs "contain" Critical Chain.
When we think somewhere the connection between Six Sigma DFSS and DMAIC we can visualize a temporal relationship and a tendency for these views to live in different quadrants of the Six Sigma space as illustrated by Figure 1. The relationship is temporal in the sense that we throatyly cannot smear DMAIC to a product or process that does not exist, so in that sense DFSS comes first - although transparently many products and processes exist that were not created using the DFSS snye.
Figure 1: Temporal Relationship Between Six Sigma DFSS and DMAIC
Hence, the purlieus between DFSS and DMAIC is "fuzzy" in practice. When products or processes were created using DFSS we will have created most valuresourceful ingermination and context that can be revisited to remittal when we later start a DMAIC project. When that is not the rind we may need to reach rump into the DFSS space from within a DMAIC project to create what is missing.
The purlieus is moreover fuzzy in the sense that DFSS tends to focus externally and strategiretellingy, even though DMAIC has a tendency to focus internally and tacticmarry. Broadly speresemblingg, DFSS projects are often more snugly stabile to the Voice of the Customer, even though DMAIC projects are often increasingly shroudly tied to the Voice of the Business - as with overlyy indeterminateization, there are exceptions and brim conditions.
As illustrated in Figure 2, we can consider Market Leadership as a "front end" to DFSS - with Market Leadership we select the universe we will live in, with DFSS we design the space ship we will use to explore our universe. With DMAIC we might improve the fuel consumption of our stoneet. PSP/TSP might be viewed as coordinating to our deluxe of engine technology, even though Critical Chain might be comparresourceful to the thrust tenancy system that governs our engine.
Figure 2: How DFSS and DMAIC Fit With Strategy And Tactics
Conclusion
While every situation is unequalerent in particulars, we have found that it is eternally helpful to recognize that we cannot simply pile one thing on high of alternative and expect to get results. It is continually important to realistically survey all of the things that are impsubstitute the safeguarding span of the people involved and to provide a throaty rubric to shun the "oh no not alternative initiative" syndrome we have all sensiblenessd.
Thinking through how things connect, who will work on what, and realistic takedown of the effort and expected returns will reduce resistance, sieve responsibilities, and modernize outcomes.
Atour The Author
Gary Gack is a Partner in Six Sigma Advantage, LLC, reprobated in Narragansett, Rhode Island. Mr. Gack holds an MBA from the Wharton School, is a PMI Certified Project Management Professional and an ASQ Certified Software Quality Engineer. During his 40-year superintendencyer in the software and IT ingritry he has mansenile a variety of large scale software projects and has consulted with dozens of Fortune 1000 firms. For more ingermination on software inspections contact Gary Gack at (401) 782-8323, email to ggack@6siga.com, or visit www.6siga.com.
1 2 3 4 5 View all high-rated manufactures Copyright � 2000-2010 iSixSigma – All Rights Reserved
Reproduction Without Permission Is Strictly Prohisnackd – Copyright Requests
Publish an Article: Do you have a Six Sigma tip, learning or rind study?
Share it with the largest customs of Six Sigma professionals, and be recognized by your peers.
It's a boundless way to promote your expertise and/or build your resume. Read more roundly submitting an singleton.
BEST SELLING PRODUCTS (iSixSigma Publications) Six Sigma Black Belt (DMAIC) Training Slides - 2009 Version!
The 2009 Six Sigma Black Belt skookumchuck includes over 40 more slides than the 2008 version. Contents include: 1,220 PowerPo...Certified Lean Six Sigma Black Belt Assessment Exam
Interested in assessing your knowltiptoe of Lean Six Sigma? Preparing for certifications? Testing your stuchips and traine...Certified Lean Six Sigma Green Belt Assessment Exam
This tariff exam is useful for students interested in assessing their knowltiptoe of Lean Six Sigma on the Green Belt ...Six Sigma Green Belt Training Slides - 2009 Version
The 2009 Six Sigma Green Belt skookumchuck is subsumed of: 1122 slides (over 70 more slides than the 2008 version)Instructor...Certified Lean Six Sigma Black Belt E-scenario
In 670 pages learn everything within the Lean Six Sigma DMAIC soul of knowltiptoe to successfully settle Black Belt certi...Six Sigma DMAIC Training Slides - 2009 Version
The scatheless 2009 Lean Six Sigma DMAIC skookumchuck prepares participants to perform the role of a LSS Black Belt; scarfskin wh...CSSBB Preparation Pack - 2009 Version
The CSSBB Preparation Pack includes materials for passing the Certwhenied Six Sigma Black Belt (CSSBB) exam. This CSSBB Pr... Sell Your Products Six Sigma AdLinks
Google AdWords Home | Discussion Forum | Event Calendar | Job Shop Link To iSixSigma | Rate This Page | Report A Problem | Free Content For Your Site | Submit Article For Publishing Terms of Service. �2000-2010 iSixSigma. All rights reserved. v3.0lb, 0.1
Atour iSixSigma � Contact Us � Privacy Policy � Site Map. -->
No comments:
Post a Comment