High-Tech Yuga

Posts

Horizon planning Agile Pgm

📘 Horizon Planning in Agile PgM Horizon Planning in Agile Programme Management is a way of planning at different levels of detail over time, accepting uncertainty and enabling change—while still maintaining control and alignment to the programme vision. In simple terms: > Plan in detail only what is near, and keep the future flexible. --- 🔭 The Three Horizons (most commonly used) Horizon 1 – Near Term (Detailed Planning) Covers short-term delivery High level of certainty Capabilities to be enabled soon Detailed planning is appropriate Projects and tranches are clearly defined 👉 “Only those capabilities to be enabled in the short term can be planned in detail.” --- Horizon 2 – Medium Term (Outline Planning) Covers upcoming capabilities Moderate uncertainty Planned at high level Priorities may change based on: Early benefits realised Lessons learned Changes in business strategy 👉 Focus is on options, sequencing, and dependencies, not detail. --- Horizon 3 – Long Term (Vision-Level...

Teams in Lean Six Sigma

Below is a clear, structured explanation of Teams in Lean / Lean Six Sigma , written in a training-ready and interview-ready style. Teams in Lean & Lean Six Sigma Lean success depends less on tools and more on people . A well-structured team with the right sponsorship turns improvement ideas into sustained results . 1️⃣ The Team & The Team Sponsor 🔹 The Lean Team A Lean Team is a cross-functional group responsible for analyzing, improving, and controlling a process. Typical Lean Team Members Process Owner Frontline employees Subject Matter Experts (SMEs) Lean / Six Sigma Facilitator Data or Quality representative 📌 Key principle: People who do the work must help improve the work . 🔹 The Team Sponsor The Team Sponsor is a senior leader who owns the business outcome of the project. Responsibilities of the Sponsor Provides direction and alignment Removes organizational roadblocks Allocates resources Approves scope changes Ensures results are sustained 📌 Sponsors d...

The Kaizen Event

The Kaizen Event (Rapid Improvement Event) in Lean What is a Kaizen Event? A Kaizen Event is a short, focused, team-based improvement effort —typically 3 to 5 days —designed to achieve rapid, measurable improvements in a specific process. Kaizen means continuous improvement . A Kaizen Event is improvement at high speed . Why Organizations Use Kaizen Events Deliver quick wins Reduce waste (Lean focus) Improve quality, cost, delivery, and safety Engage frontline employees Turn analysis into immediate action When to Use a Kaizen Event Use a Kaizen Event when: The problem is well-defined The process is localized Solutions are known or testable Leadership support is available Rapid improvement is needed ❌ Not ideal for highly complex, cross-enterprise problems (use DMAIC instead). Typical Duration & Team Duration: 3–5 days Team size: 6–10 members Team makeup: Process owner Frontline operators Subject matter experts Lean facilitator Management sponsor Kaizen Event Phases (Da...

Using 5 Whys and Fishbone (Ishikawa) Diagram - Root Cause Analysis (RCA) in Lean Six Sigma

Root Cause Analysis (RCA) in Lean Six Sigma Using 5 Whys and Fishbone (Ishikawa) Diagram What is Root Cause Analysis (RCA)? Root Cause Analysis is a structured problem-solving approach used in Lean Six Sigma to identify the real cause of a problem—not just its symptoms. Goal: Fix the problem once and permanently , not repeatedly. RCA is mainly used in the Analyze phase of DMAIC . Why RCA is Critical in Lean Six Sigma Prevents recurring defects Avoids “quick fixes” Reduces waste and rework Enables sustainable improvement Supports data-driven decisions Two Most Powerful RCA Tools Lean Six Sigma commonly uses: 5 Whys Fishbone (Cause-and-Effect) Diagram They are often used together . 1️⃣ 5 Whys Technique What is 5 Whys? The 5 Whys is a simple questioning technique where you repeatedly ask “Why?” until the root cause is revealed. 📌 Usually 5 times—but it can be 3 or 7 , depending on the problem. 5 Whys – Example Problem Statement ❌ Customer received wrong invoice Why? Answer ...

Yield, DPMO & Process Sigma in Lean Six Sigma

1️⃣ Yield What is Yield ? Yield measures the percentage of outputs that are defect-free . Yield answers: How much did we get right the first time? Formula Yield (%) = Good Units Total Units × 100 \textbf{Yield (\%)} = \frac{\text{Good Units}}{\text{Total Units}} \times 100 Yield (%) = Total Units Good Units × 100 Example Units processed = 1,000 Defective units = 50 Good units = 950 Yield = 950 1000 × 100 = 95 % \text{Yield} = \frac{950}{1000} \times 100 = 95\% Yield = 1000 950 × 100 = 95% ✅ 95% Yield ❌ Still means 50 customers unhappy 2️⃣ DPMO (Defects Per Million Opportunities) What is DPMO ? DPMO measures how many defects would occur per one million opportunities . DPMO answers: How bad is the process when scaled up? Formula DPMO = Number of Defects Units × Opportunities per Unit × 1,000,000 \textbf{DPMO} = \frac{\text{Number of Defects}} {\text{Units} \times \text{Opportunities per Unit}...

DPMO in Lean Six Sigma (Defects Per Million Opportunities)

What is DPMO? DPMO (Defects Per Million Opportunities) is a key Lean Six Sigma metric that measures process quality by estimating how many defects would occur if there were one million chances for defects. It allows fair comparison between processes with different sizes and complexity . DPMO – Simple Definition DPMO tells us how often a process fails, normalized to one million opportunities. Lower DPMO = Better quality Why DPMO is Important Standard quality metric across industries Links process performance to Sigma Level Helps prioritize improvement projects Makes defects measurable and comparable DPMO Formula DPMO = Number of Defects Number of Units × Opportunities per Unit × 1,000,000 \textbf{DPMO} = \frac{\text{Number of Defects}} {\text{Number of Units} \times \text{Opportunities per Unit}} \times 1{,}000{,}000 DPMO = Number of Units × Opportunities per Unit Number of Defects × 1 , 0...