High-Tech Yuga

**01 — Scope Creep: The Never-Ending Feature Factory (+120% over budget)** Uncontrolled feature additions buried the project. PM fixed it with a scope freeze, a Change Control Board, and Agile sprints. **02 — Poor Requirements: Building the Wrong Product (9 months wasted)** Requirements were gathered from an executive, not real users. PM ran user story workshops, prototyping cycles, and introduced a Requirements Traceability Matrix. **03 — Communication Breakdown: The Siloed Dev Team Disaster (3 modules rebuilt)** Three teams built incompatible systems. PM added weekly cross-team syncs, API wikis, and Architecture Decision Records (ADRs). **04 — Unrealistic Deadlines: The Death March Launch (5 engineers resigned)** A 90-day promise caused burnout and mass resignations. PM renegotiated a phased MVP plan backed by velocity data and capped team hours. **05 — No Risk Management: The Third-Party Collapse ($800K unplanned cost)** A vendor acquisition killed a critical API with no backup plan...

Here are 10 senior project manager interview questions with strong sample answers: --- **1. How do you manage competing priorities across multiple projects?** *Answer:* I use a combination of stakeholder alignment and structured prioritization frameworks like MoSCoW or weighted scoring. I start by mapping dependencies and deadlines, then facilitate a conversation with sponsors to align on trade-offs. I maintain a live priority register and revisit it in weekly stand-ups so the team always knows what matters most. --- **2. Describe a project that failed. What did you learn?** *Answer:* On a CRM migration project, we underestimated the data cleansing effort, which pushed us six weeks past deadline. I learned to build dedicated discovery sprints before committing to timelines, and to involve data owners earlier. Since then, I've made pre-project risk workshops standard practice. --- **3. How do you handle a stakeholder who constantly changes scope?** *Answer:* I address this through a...

📘 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...

 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 (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...

  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 ...