110 likes | 388 Views
Outline. What is Six Sigma? Six Sigma methodologies Process Improvement — DMAIC Define – Measure – Analyze – Design – Verify (DMADV). Outline (Cont). Six Sigma Key Roles Typical Six Sigma Project in Software How Six Sigma Helps Process Improvement References. What is Six Sigma ?.
E N D
Outline • What is Six Sigma? • Six Sigma methodologies • Process Improvement — DMAIC • Define – Measure – Analyze – Design – Verify (DMADV) CSE 577b - Six Sigma
Outline (Cont) • Six Sigma Key Roles • Typical Six Sigma Project in Software • How Six Sigma Helps Process Improvement • References CSE 577b - Six Sigma
What is Six Sigma ? What is Sigma? • Sigma (s) is the Greek symbol used to represent standard deviation, a measure of the variation from the mean in a normal distribution • Six Sigma (6 ) is a business-driven, management philosophy based on multi-faceted approach to process improvement, reduced costs, and increased profits. It was pioneered by Motorola in 1986. CSE 577b - Six Sigma
Six Sigma methodologies • DMAIC • DMADV CSE 577b - Six Sigma
Process Improvement — DMAIC • Define: Define the project goals and customer (internal and external) deliverables • Measure: Measure the process to determine current performance • Analyze: Analyze and determine the root cause(s) of the defects • Improve: Improve the process by eliminating defects • Control: Control future process performance CSE 577b - Six Sigma
Define – Measure – Analyze – Design – Verify (DMADV) • Define: Define the project goals and customer (internal and external) deliverables • Measure: Measure and determine customer needs and specifications • Analyze: Analyze the process options to meet the customer needs • Design: Design (detailed) the process to meet the customer needs • Verify: Verify the design performance and ability to meet customer needs CSE 577b - Six Sigma
Six Sigma Key Roles • Executive Leadership • Champions • Master Black Belts • Black Belts • Green Belts CSE 577b - Six Sigma
A Typical Six Sigma Project in Software • Customers express concern that software defects are causing frequent failures in the field • A Six Sigma team is formed to scope the problem, collect data, and determine the root causes • The team’s analysis of the data determines that poorly understood interface requirements accounts for 90% of the problem in the field • The project collects data to verify the problem has been corrected, and continues collecting data to ensure the problem does not return • The organization’s requirements process is modified to ensure future projects do not encounter similar problems CSE 577b - Six Sigma
How Six Sigma Helps Process Improvement • PI efforts often generate have little direct impact on the business goals • Six Sigma delivers results that matter to managers (fewer defects, higher efficiency, cost savings, etc …) • Six Sigma concentrates on problem solving in small groups, focused on a narrow issue • Six Sigma focuses on the customer’s perception of quality CSE 577b - Six Sigma
References • Journal: • International Journal of Six Sigma and Competitive Advantage (IJSSCA) • Books: • Rath & Strong, “Six Sigma Pocket Guide,” Rath & Strong Management Consultants, Lexington, MA, 2001. • Six Sigma Fundamentals: A Complete Guide to the System, Methods and Toolsby Dean H Stamatis CSE 577b - Six Sigma
References (Cont) • Website: • http://en.wikipedia.org/wiki/Six_Sigma • http://www.isixsigma.com/sixsigma/six_sigma.asp • http://www.sei.cmu.edu/publications/documents/05.reports/05tn005.html • http://www.sei.cmu.edu/str/descriptions/sigma6_body.html • Magazine: • Smith, Larry R., “Six Sigma and the Evolution of Quality in Product Development,” Six Sigma Forum Magazine, Vol. 1, Issue 1, Nov 2001 • Six Sigma: Quality Performance; July 2003 - Maryann G. Billington and Peter J. Billington, Ph.D. CSE 577b - Six Sigma