This curriculum spans the design and implementation of organization-wide Lean-Agile workflows, comparable in scope to a multi-phase internal transformation program that integrates portfolio management, cross-team coordination, and systems thinking into everyday project execution.
Module 1: Aligning Lean Principles with Agile Frameworks
- Selecting appropriate Agile frameworks (Scrum, Kanban, SAFe) based on organizational maturity and value stream complexity.
- Mapping Lean waste categories (e.g., overproduction, task switching) to Agile anti-patterns in sprint execution.
- Integrating Lean thinking into Agile ceremonies by streamlining stand-ups to focus on flow blockers.
- Defining value from the customer’s perspective to shape product backlog prioritization in Agile planning.
- Deciding when to apply pull-based workflows (Kanban) versus time-boxed iterations (Scrum) for different project types.
- Establishing cross-functional team structures that reduce handoffs and support end-to-end ownership.
Module 2: Value Stream Mapping for Project Workflows
- Conducting current-state value stream mapping to identify non-value-added time in software delivery pipelines.
- Measuring lead time and cycle time across stages from backlog refinement to production deployment.
- Identifying handoff delays between development, QA, and operations teams in CI/CD workflows.
- Designing future-state value streams with reduced rework loops and faster feedback cycles.
- Using cumulative flow diagrams to visualize work-in-progress (WIP) limits and bottlenecks.
- Validating process improvements by comparing pre- and post-implementation flow metrics.
Module 3: Lean-Agile Portfolio Management
- Implementing weighted shortest job first (WSJF) for prioritizing epics across competing business units.
- Establishing capacity allocation policies to balance feature development, technical debt, and operational work.
- Creating portfolio Kanban systems to visualize and manage funding and initiative flow.
- Deciding how frequently to conduct portfolio backlog refinement with executive stakeholders.
- Integrating financial governance with Lean-Agile planning cycles without introducing waterfall delays.
- Managing dependencies across Agile release trains using solution-level planning events.
Module 4: Optimizing Flow and Reducing Batch Size
- Breaking monolithic user stories into smaller, independently deployable increments.
- Reducing batch size in code commits and deployments to accelerate feedback and reduce integration risk.
- Implementing feature toggles to decouple deployment from release and enable continuous delivery.
- Setting and enforcing WIP limits at team and program levels to prevent overloading.
- Adjusting sprint scope dynamically when flow metrics indicate team capacity constraints.
- Using Little’s Law to diagnose and address causes of extended cycle times.
Module 5: Continuous Improvement in Agile Teams
- Structuring retrospectives to focus on systemic issues rather than individual performance.
- Implementing improvement backlog items with clear ownership and measurable outcomes.
- Using root cause analysis (e.g., 5 Whys) to address recurring sprint impediments.
- Tracking the impact of process changes through leading indicators like team morale and defect escape rate.
- Integrating improvement actions into sprint planning to ensure follow-through.
- Facilitating cross-team kaizen events to address shared workflow inefficiencies.
Module 6: Lean Metrics and Performance Governance
- Selecting outcome-based metrics (e.g., customer satisfaction, time-to-market) over vanity metrics.
- Defining normalized defect density benchmarks across teams with different technology stacks.
- Using control charts to distinguish common cause from special cause variation in delivery performance.
- Reporting flow efficiency to leadership as a proxy for process health and agility.
- Aligning team-level metrics with enterprise objectives without creating misaligned incentives.
- Automating data collection from Jira, CI/CD tools, and monitoring systems to reduce manual reporting.
Module 7: Scaling Lean Practices Across Programs
- Standardizing definitions of done and acceptance criteria across multiple Agile teams.
- Coordinating integration points for loosely coupled teams working on a shared product.
- Resolving conflicts over shared resources using capacity planning and demand management.
- Implementing enterprise Agile planning events (e.g., PI Planning) with remote and hybrid participants.
- Managing technical debt accumulation across programs through shared architecture governance.
- Scaling continuous delivery pipelines to support independent team deployments without regression risk.
Module 8: Change Management and Organizational Adoption
- Identifying early adopters and change champions within business and technical units.
- Designing pilot programs to demonstrate Lean-Agile benefits with minimal organizational disruption.
- Negotiating role changes for traditional project managers transitioning to Agile coaching or facilitation.
- Addressing resistance from middle management concerned about perceived loss of control.
- Aligning HR policies (e.g., performance reviews) with team-based Agile outcomes.
- Embedding Lean-Agile practices into onboarding and leadership development curricula.