1 / 32

Raytheon Six Sigma (R6 ) ASEE Meeting 4 December 2001

Raytheon Six Sigma (R6 ) ASEE Meeting 4 December 2001. 1-1. Software Metrics Example.

pilar
Télécharger la présentation

Raytheon Six Sigma (R6 ) ASEE Meeting 4 December 2001

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Raytheon Six Sigma (R6) ASEE Meeting4 December 2001 1-1

  2. Software Metrics Example The software engineering community has been placing a great deal of emphasis lately on metrics and their use in software development. The following metrics are probably among the most valuable for a software project: The Pizza Metric How : Count the number of pizza boxes in the lab. What: Measures the amount of schedule under-estimation. If people are spending enough after-hours time working on the project that they need to have meals delivered to the office, then there has obviously been a mis-estimation somewhere. © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  3. Software Metric Example The software engineering community has been placing a great deal of emphasis lately on metrics and their use in software development. The following metrics are probably among the most valuable for a software project: The Aspirin Metric How: Maintain a centrally-located aspirin bottle for use by the team. At the beginning and end of each month, count the number of aspirin remaining in the bottle. What: Measures stress suffered by the team during the project. This most likely indicates poor project design in the early phases, which causes over-expenditure of effort later on. In the early phases, high aspirin-usage probably indicates that the product's goals or other parameters were poorly defined. © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  4. Agenda • R6 Overview • R6 Process • R6 Principles • R6 Roles & Responsibilities • R6 Software Example • Questions & Answers • R 1-4

  5. Raytheon Six Sigma (R6) Overview 1-5

  6. Raytheon Six Sigma – Definition: Raytheon Six Sigma is a Knowledge Based Process we will use to Transform Our Culture in order to Maximize Customer Value and Grow Our Business © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  7. A Historical Perspective on Six Sigma? • Motorola: Six Sigma Producibility Analysis • Ability to reproduce units of product identically andwithout waste • Raytheon: Six Sigma Umbrella (per Dan Burnham) • Philosophy of continuous improvement • Defect reduction and cycle time improvements in all business processes and products © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  8. Raytheon 6 Sigma Approach Motorola 6 Sigma Approach Raytheon Six Sigma versus Traditional Six Sigma • The classical 6 Sigma approach, utilized by Motorola, has its underpinnings in Hardware design and manufacture. • The Raytheon 6 Sigma Approach is based on benchmarking with Allied Signal and General Electric and is more broad in scope – • Includes all processes and functions • Integrates Proven Philosophiesand a Number of Continuous Improvement Techniquesand Tools • Supported by a full time Six Sigma Expert Network • Leads to a Culture Change © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  9. Alignment Leadership Involvement Raytheon Six Sigma . . . An Integrated Business Strategy It defines our culture — How we will work © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  10. A Continuum of Opportunity • Everyone • Common Sense • Empowerment Simple Complex • Specialists • Some Tools • Some Training and experience • Experts • Multi-disciplined tool set • Lengthy training and experience BureaucracyBusting © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  11. Knowledge Based Management • Ask the right questions • Act based on facts, not opinions • Get data, use data • Make it visual • Have a closed loop process • Capture lessons, share them widely In God we trust, all others bring DATA! © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  12. R6 Process 1-12

  13. Visualize Achieve Commit Improve Prioritize Characterize R6s Process Visualize the Future Celebrate & Plan for the Future Commit to Change Determine Improvement Opportunities Design & Implement Changes © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001 Define Current State

  14. Visualize — Imagine the Future Create a vision of the future with a clear and pressing need for change. Align sponsorship throughout the business to maximize our benefits. © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  15. Tool Chest Survey Questions Assessment Models Change Management Techniques Quality Function Deployment (QFD) Tools Balanced Scorecard Analysis Tools Value Stream Analysis Catchball Benchmarking Vision of the Future Need for Change Strategy Accountable Sponsor Visualize – IPO Inputs Process Outputs • 1) Assess the current state. • 2) Visualize alternate future states “blue sky” with stakeholders. • 3) Converge to a common vision & validate (create need & generate excitement). • 4) Draw the mental image that excites people and creates a need for change that demonstrates it. • 5) Align and validate throughout the value stream: • Customer • Employees • Suppliers • Shareholders • 6) Develop strategy (1st steps): • Identify Sponsor / Change Agent Current State Clear & pressing needfor change Stakeholder demand Customer perceptions& Desires Market position& pressures Aspirations, Values, Goals © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  16. Commit – Commit to Change Develop a committed sponsor and team aligned with the vision, accountable and energized to make change. © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  17. Tool Chest Team Building Exercises Raytheon Six Sigma Training Internal/External Benchmarking Data Strategic Vision/Mission Customer & employee surveys Competitive market analysis information Internal Financial Data Reality Tree Win/Win Negotiation Example Case studies Commit – IPO Inputs Process Outputs 1) Sponsor personalizes vision, agrees that there’s a need, accepts the strategy & commits to change. 2) Sponsor characterizes a multifunctional team & captures resources. 3) Sponsor shares current reality & future vision with the team. 4) Team personalizes vision by exploring, understanding & accepting what’s in it for them & their organization. 5) Team education in Raytheon Six-Sigma Process. 6) Team validates need to change & translates vision into goals & objectives. 7) Team identifies target areas & shares need to change with them. Vision of the Future Need for Change Strategy Accountable Sponsor Committed Sponsor Committed, aligned &knowledgeable team Identified & InformedTarget Areas Defined Goals &Objectives © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  18. Prioritize – Determine Improvement Priorities Using facts and data, discover improvement opportunities, readiness and resources. Define goals and high level action plans. Commit resources to focused improvement project(s) in order to realize significant results. © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  19. Tool Chest Reality Trees & Fishbone Diagrams Quality Function Deployment (QFD) Pareto Charts Process Flow Charts & Spaghetti Charts Financial forecasting & Cost estimating models Market analysis (customer care-abouts) 5 Why’s Affinity Diagrams Normal Group Technique Common sense Theory of Constraints Prioritize – IPO Inputs Outputs Process • 1) Understand Value Stream. • 2) Perform Assessment(s). • 3) Identify opportunities/high-leverage points: • Encourage discovery • Find interdependencies • Identify root causes • 4) Estimate expected results and prioritize opportunities. • 5) Document improvement plan. • 6) Obtain commitment to support plan (Contract for Change). Committed Sponsor Committed, aligned & knowledgeable team Identified & InformedTarget Areas Defined Goals &Objectives Prioritized list of improvement projects Contract for change Transferred Knowledge © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  20. Characterize – Define Existing Process and Plan Improvements Understand and document current state performance & translate the current state opportunities into a plan for improvement. © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  21. Tool Chest Form Team: Team building Raytheon Six-Sigma Training Contracting Validate the Problem: Pareto 7 Problem Solving Tools Raytheon Six-Sigma Process Plan the Approach: Planning Tools Brainstorming Reality Trees Affinity Diagrams Characterize the Process: Change Readiness Evaluations Theory of Constraints (TOC) 7 Problem Solving Tools Process Flow Diagrams & Spaghetti Charts Capacity Analysis ANOVA, SPC, Takt, 5S Metrics & Information Systems Determine the Implementation Plan: Resource Loading ROI / Benefit analysis Tools Planning Tools Brainstorming Communicate the Implementation Plan: Message Mapping Presentation & Interpersonal Communication Skills Influence w/o authority Characterize – IPO Process Inputs Outputs Allocated Resources Characterized Process Documented Expectations with expected Benefits & Improvements Approved Project Plan Transferred Knowledge 1) Form Team. 2) Validate the Problem. 3) Plan the Approach. 4) Understand (Characterize) the Process. 5) Determine the Improvement Plan. 6) Communicate the Improvement Plan. Prioritized list ofImprovement Projects Contract for Change Transferred Knowledge © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  22. Improve – Design and Implement Improvements Design and implement integrated improvements and control systems to maximize value. © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  23. Tool Chest Statistics: DOE, SPC Waste Reduction: JIT Level Schedules Workplace Organization Visual Controls Error Proofing Set-up Reduction DTC Tolerancing: Tolerance Allocation Defect Reduction: Performance, Process, Pareto Problem Solving: Brainstorming Cause / Effect Scattergram FMEA Manufacturability: DFMA Defect Budgeting PCAT Change Management Techniques. Improve – IPO Process Inputs Outputs Allocated Resources Characterized Process Documented Expectations with expected Benefits & Improvements Approved Project Plan Transferred Knowledge [Use appropriate tools based on project for each step]: 1) Identify Resources… train/educateas necessary. 2) Detail Action Plan and Schedule. 3) Pull in required Tools. 4) Design the solution. 5) Execute the Plan / Implement. 6) Monitor changes. 7) Implement Controls. 8) Measure Results. Management &Control Systems Improved Process Performance Transferred Knowledge © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  24. Achieve – Celebrate Achievements, Build for Tomorrow Deliver measurable results that change the way people think and act, create knowledge, build momentum for continuous improvement, celebrate success, and get people excited about doing Raytheon Six Sigma repeatedly. © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  25. Tool Chest Knowledge Management System (transfer) New Financial/ Accounting Systems Change Management Tools Control Charts Organizational Development Employee Satisfaction Monitoring Systems Communication Systems Data Analysis Tools Achieve– IPO Process Inputs Outputs • Embedded New Process • Delivered Resultsto the Organization • Documented Success: • Case Study • Lessons Learned • Next Steps • Recognition & Rewards • Captured & SharedKnowledge • Expanded R6sCommunity 1) Define responsibilities to support & enable process. 2) Train, education & communicate newprocess. 3) Measure and compare results and expectations… take appropriate action. 4) Create Success Summary. 5) Reward,& recognize change agent team. 6) Capture & Share knowledge. 7) Monitor and analyze process for Continuous Improvement Opportunities. Management &Control Systems Improved Process Performance TransferredKnowledge © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  26. R6 Principles 4-1 1-26

  27. Raytheon Six Sigma – Principles • Specify value in the eyes of the customer • Identify value stream; eliminate waste and variation • Make value flow at pull of the customer • Involve, align & empower employees • Continuously improve knowledge in pursuit of perfection 4- © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  28. The Sixth Sigma I see waste, it’s everywhere. People are creating it and they don’t even know they’re doing it. © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  29. R6 - Roles & Responsibilities • Champions • Senior leaders who plan and execute the deployment in their organizations • Master Experts • Fully-trained, highly-experienced, full-time leaders responsible for planning, training, mentoring, and results • Experts • Fully-trained, full-time experts who lead improvement teams, work complex projects across the business, and mentor Specialists • Specialists • Trained for applying skills to projects in their job areas © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  30. Case for Action Project: TRACER S/W Location: Plano, TX Software effort is critical path on the program Customer (U.S. Army) views software as top risk on the program “Software development is behind schedule” SPI = .79 CPI = .61 Software schedule showing 64 days negative float to contract delivery Software team struggles to over come 13-month delay in defining requirements © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  31. Project: TRACER S/W Location: Plano, TX The team achieved its goal to streamline the process, reduce cycle time, and free up valuable engineering effort to enable the incorporation of $720K cost avoidance. After determining the planned S/W build incorporation on TRACER was at risk, this team visualizedthe need for a shared program purpose and use of Critical Chain Program Management. • The team met daily in the All Hands Planning meetings to communicate status and barriers. They saw progress in completing tasks improved by: • Use of Visuals of the SCI Inchstones • Establishment of the Run Rules for Critical Chain • Implementation of Constraint Management • Better communication and transitioning SCI folks to support task in need. The team committed to use R6 Sigma and CCPM to identify key issues and barriers. Looking at the currentstate of the program, the team prioritizedmaking improvements in the various Software Configuration Items (SCIs). R6 Sigma applications - Use of Visuals, Run Rules, Critical Chain, and Constraint Management tools were implemented. Work on SCI IC&C was stopped due to variability in requirements. • After characterizing these processes, the team found they could make • significant gains by focusing on : Improving Program Communications • Prioritization of the SCIs - InfoDev, EEOS, and IC&C • Streamlining the SCI process and include the hardware dependencies in the work flow © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

  32. Results (as of April 2001) • SPI = .95 CPI = .73 • $720K cost avoidance in software implementation stage • Software schedule reduced to 24 days negative float • Prime customer no longer considers Raytheon software as top risk item on the program • Customer says “Raytheon software is now under control” • Prompted rest of program and prime to apply Critical Chain • Spawned 6 Sigma Specialist project for “Out of the Box Rewards” as incentives to meet schedule Entire team is focused on Critical Chain © 2000, Raytheon Company. All Rights Reserved. ST, 1 March 2001

More Related