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

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

4 T's - Technology, Time, Teamwork, Transparency

 1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished.  3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...
Post a Comment
Read more