Skip to main content

Lean vs Six Sigma

Lean:

✓ Originated from Toyota 

✓ The Toyota Production System (TPS) is at the heart of Lean 

✓ The Lean methodology focuses on eliminating waste and smoothing the process flow 

✓ Lean is not about cutting costs. It is about removing waste without sacrificing quality


Waste is whatever slows the delivery process down

  • Reworking
  • Doing things customer doesn't want
  • Piles of materials not being worked on
  • Customers Queuing

Six Sigma:

 ✓ Developed by Motorola 

✓ To improve processes by reducing variation and defects 

✓ Many (but not all) of the tools are statistical in nature and 6 Sigma emphasises taking action based on fact rather than opinion or common belief 

✓ The ‘Sigma’ (σ) rating of a process can be used as an indicator of how many defective parts a process produces 

✓ 6 Sigma equates to 3.4 defects for each million opportunities (DPMO)





How they complements each other?


Key Principles:

General Topics:

How to make customer happy? (Voice of Customer - VOC)

1) Minimum variation

2) Quick delivery (Short Lead Time)

3) Reasonable Cost


 Six Sigma Belts:


The role of yellow belt:

✓ Understands the terminology and overall Lean 6 Sigma process 

✓ Is aware of the major tools and techniques embraced by Lean 6 Sigma 

✓ Understands the underlying philosophy of Lean and 6 Sigma 

✓ Acts as a team member under the direction of a Green Belt or Black Belt



Comments

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .