32
By: Nick Blank March 1, 2012

By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

Embed Size (px)

Citation preview

Page 1: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

By: Nick BlankMarch 1, 2012

Page 2: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Six Sigma • Definitions• Goals• History• Methods• Roles• Benefits• Criticism• Software Development

Page 3: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Business management strategy.• Seeks to improve quality of process outputs.o Identifying and removing the causes of defects.o Minimizing variability.

• Set of quality management methods. (statistical methods)

• Creates a special infrastructure of people.• Follows a defined sequence of steps.

Page 4: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Critical to Quality: internal critical quality parameters that relate to the wants and needs of the customer.

• Critical to Customer: the input to the Quality Function Deployment activity.

• Defect: Any type of undesired result.• Opportunity: area within a product, process, service,

or other system where a defect could be produced or where you fail to achieve the ideal product in the eyes of the customer

Page 5: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• To achieve no more than 3.4 defects per million opportunities. (99.99966%)

• 6 standard deviations between the mean and the nearest specification limit.

Graph from http://en.wikipedia.org/wiki/Six_Sigma

Page 6: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• "Born" at Motorola from Art Sundry's criticism of the company's quality.

• As a result Motorola found out that better quality is cheaper.

• Bill Smith developed the particulars in 1986.

Page 7: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• DMAICo Improvement system for existing processes

• DMADVo Improvement system for developing new processes or products

Page 8: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Define - the problem, the voice of the customer, and the project goals.o Identify the Critical To Quality characteristicso Create a map of the process to be improved with defined and

measurable, deliverables, and goalso Tools: Benchmark, Baseline, Voice of the Customer, Process

Flow Map

Page 9: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Measure - key aspects of the current process and collect relevant data.o Establish valid and reliable metrics to monitor the progress of

the project Input, process, and output indicators are identified

o Determine the impact of defects from each input on the CTQso Once reasons for input failure are determined, preventative

actions are put into placeo Tools: Defect Metrics, Data Collection, Sampling Techniques

Page 10: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Defects Per Million Opportunities (DPMO) = (Total Defects / Total Opportunities) * 1,000,000

• Defects (%) = (Total Defects / Total Opportunities)* 100%

• Yield (%) = 100 - %Defects

• http://www.isixsigma.com/process-sigma-calculator/

Page 11: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Analyze - the data to investigate and verify cause and effect relationships.o Identify the gap between existing performance and desired

performanceo Root Cause Analysis – finding the causes of defectso Process Improvement Scenarioso Tools: Cause and Effect diagrams, Decision and Risk Analysis,

Control Charts

Page 12: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Improve -  the current process based upon data analysis techniques.o Create new improvement solutions for each root causeo Cost/Benefit Analysis

What happens if improvements are not made or improvements take too long to implement

o Process experimentation and simulationo Implement and adapt to these solutions and the results from

these changes

Page 13: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Control -  the future state process to ensure that any deviations are corrected.o A monitoring plan with proper change management methodso Implement the lesson learnedo Put tools in place to maintain process improvement gainso Trainingo Document the project

New procedures and lessons learned are maintained and give a solid example

o Identify future Six Sigma improvement opportunities

Page 14: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Define –  the problem, the voice of the customer, and the project goals.

• Measure –  key aspects of the current process and collect relevant data.

• Analyze –  the data to investigate and verify cause and effect relationships.

Page 15: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Design - optimize the design and plan for design verification.o Specification Limitso Simulation modelo Measurement and Control Plan

Page 16: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Verify - the design, set up pilot runs, implement the production process.o Pilot runso Training of personnel that will maintain processo Implementing the processeso Document the processes

Page 17: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

o Professional who works on project.o Awareness of Six Sigma, but no training.o Anyone

Page 18: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

o Operate in support or direction of Black Belts.o Trained to analyze and solve quality

problems.o Two weeks of training in methods and basic

statistical tools.

Page 19: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

o Team Leader on Six Sigma projects.o Capable in the explanation of six sigma

philosophies and the principles.o Training in team leadership.o Knowledge of Lean.o Four to Five weeks of training.

Page 20: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

o Expert in Six Sigma methods and tools.o Responsible for training others to the Green

and Black belt levels.o Responsible for maintaining the integrity.o Highest certification.o Assists the Champion with deployment.

Page 21: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

o Translate the company's vision, mission, goals and metrics.

o Make resources available and remove road blocks.

o Resolves cross-functional issues.

Page 22: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

o Establish strategic focus.o Ensure Six Sigma within the context of the

organization's culture and vision.

Page 23: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

o Motorolao General Electrico Allied Signalo Citibanko Microsofto Lockheed

Page 24: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• General Electric produces annual benefits of over 2.5 billion.

• Less customer service costs.• Raise customer satisfaction.

Page 25: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Need aggressive performance tracking and accountability for results.

• Employees need to be willing to use statistical tools.• Pay more attention to steps than the actual result.• Six Sigma is over sold.  Too many consulting firms

claiming mastery. • Cost of infrastructure.• Cost of training for "belts." (MBB at least $17,000

alone)• A pacemaker needs higher standards than six sigma.

Page 26: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Process variation can never be eliminated or even reduced below a moderate level.  No two modules are alike.

• There are very large differences in skills and experience from one developer to another.

• Specifications are not based around tolerances.  • Systems don't fail because the are assembled from

many loosely toleranced components.• A single well-placed defect in a low level component can

be catastrophic.

Page 27: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Time - The amount of time required to perform a task.• Size - The size of the work product.• Defects - the number and type of defect, removal time,

point of injection, and point of removal.

Page 28: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Works best with incremental and evolutionary product development.

• Instrumented to produce high quality metric data.• Normally requires changes to the software development

process and project management process.• As quality is improved, more defects are found earlier in

life cycle and more predictable.• Has significant impact in scheduling tasks and project

tracking.• Can even predict how many defects in module with

relative accuracy.

Page 29: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Standard Six Sigma not directly related to software development.

• Developers can't bridge gap between on their own.• Too many competing initiatives - CMMI, ISO9000.• Not enough time to analyze quality.• One size fits all generates resistance.

Page 30: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

The software development companies that are claiming success with Six Sigma are using it to improve the processes within the standards of CMMI and ISO.

Individual Process Organizationalinfrastructure

Six Sigma Identifies how the activities might be improved.

Identifies what activities are used for improvement (DMAIC).

CMMI Identifies what activities are expected in the process.

Identifies how those activities might be implemented.

Page 31: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

• Six Sigma • Definitions• Goals• History• Methods• Roles• Benefits• Criticism• Software Development

Page 32: By: Nick Blank March 1, 2012. Six Sigma Definitions Goals History Methods Roles Benefits Criticism Software Development

[1] Ideal Meadia LLC. i Six Sigma. Retrieved 2/18/2010. <http://www.isixsigma.com/>

[2] Huesing, Tina. “Six Sigma Through The Years”. Motorola, 2008. Retrieved 2/18/2012. <http://6sigmaexperts.com/presentations/Six_Sigma_Through_the_Years.pdf >

[3] Functional Methods. (2004). DMADV (Define, Measure, Analyze, Design, Verify) Roadmap. Retrieved 2/18/2012 <http://www.functionalmethods.com/DMADV%20Roadmap.pdf>

[4] Motorola, Inc. (2007). Motorola Univerisity, Six Sigma in Action. Retrieved 2/18/2012 <http://www.motorola.com/motorolauniversity.jsp>

[5] Al-Qutaish, R. E., & Al-Sarayreh, K. T. (2008). Applying six-sigma concepts to the software engineering: myths and facts. Proceedings of the 7th International Conference on Software Engineering Parallel and Distributed Systems SEPADS08, 178-183. Retrieved from http://portal.acm.org/citation.cfm?id=1416502.1416536