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



Labels:

Comments

Post a Comment

Popular posts from this blog

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more

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...
Post a Comment
Read more

Product Manager vs Product Owner

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company. This usually happens by delivering and optimizing product features. Product Manager Product Owner The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap. The product owner is responsible for maximizing the value of the product by creating and managing the product backlog. This person creates user stories for the development team and communicates the voice of the customer in the Scrum process.      Product Manager and Product Owner's work on below vacuum. Product manager focus on: Business Strategy Long term Product Vision Long term Product Strategy Product Roadmap Alignment with Product Owner Product owner focus on: Release Plan (Product Backlog ie: ...
Post a Comment
Read more