This curriculum spans the design and implementation of multi-workshop value stream initiatives, advisory-level governance frameworks, and organization-wide process transformations typical of sustained Lean-Agile change programs.
Module 1: Aligning Lean Principles with Agile Frameworks
- Decide whether to adopt Kanban, Scrum, or a hybrid model based on team structure, delivery cadence, and organizational maturity.
- Map value streams across product development to identify non-value-adding activities in current Agile workflows.
- Integrate Lean thinking into sprint planning by eliminating backlog items that do not directly contribute to customer outcomes.
- Balance Agile responsiveness with Lean efficiency when prioritizing technical debt reduction versus feature delivery.
- Establish cross-functional team accountability for flow efficiency rather than individual utilization metrics.
- Modify Definition of Done to include Lean criteria such as waste reduction and cycle time impact.
Module 2: Value Stream Mapping in Agile Delivery
- Conduct time-based value stream analysis to quantify delays between backlog refinement and production deployment.
- Identify handoff bottlenecks between product owners, developers, testers, and operations in CI/CD pipelines.
- Implement visual management boards that reflect actual workflow stages instead of idealized Agile phases.
- Use cumulative flow diagrams to detect work-in-progress (WIP) accumulation and adjust sprint capacity accordingly.
- Engage stakeholders in value stream workshops to align on process improvements with measurable lead time targets.
- Track and report on value-added time ratio to justify investments in automation or staffing changes.
Module 3: Managing Work-in-Progress and Flow Efficiency
- Set explicit WIP limits at the team and program levels based on historical throughput and staffing constraints.
- Enforce WIP discipline during sprint execution by blocking new task initiation when limits are reached.
- Revise sprint goals when WIP constraints expose unrealistic scope commitments.
- Monitor flow efficiency metrics (value-added time vs. total lead time) to evaluate process health beyond velocity.
- Address context switching by coordinating dependencies across teams through synchronized planning events.
- Adjust team composition or skill distribution to reduce handoffs and improve flow continuity.
Module 4: Lean Backlog Prioritization and Demand Management
- Apply Weighted Shortest Job First (WSJF) to prioritize backlog items based on cost of delay and job size.
- Reject or defer low-value requests from stakeholders by referencing validated customer impact data.
- Implement demand filtering mechanisms to prevent ad-hoc work from disrupting sprint commitments.
- Negotiate scope reductions with product owners to maintain flow stability during high-priority escalations.
- Introduce economic framing in backlog refinement sessions to align technical and business priorities.
- Track opportunity cost of delayed features to recalibrate prioritization rules over time.
Module 5: Continuous Improvement Through Lean-Agile Retrospectives
- Structure retrospectives around flow metrics such as cycle time, blockage frequency, and rework rate.
- Convert retrospective action items into measurable experiments with defined success criteria and timeboxes.
- Assign ownership of improvement actions to specific team members with accountability for implementation.
- Integrate root cause analysis techniques like 5 Whys into retrospectives to address systemic delays.
- Track the impact of process changes on lead time and team capacity over multiple sprints.
- Escalate recurring impediments to portfolio-level forums when team-level actions are insufficient.
Module 6: Lean Governance and Metrics for Agile Programs
- Select outcome-based metrics (e.g., lead time, escape defects) over vanity metrics like story points completed.
- Align executive dashboards with Lean-Agile KPIs that reflect flow, quality, and value delivery.
- Define tolerance thresholds for cycle time variation to trigger process review interventions.
- Audit compliance with Lean practices during Agile program reviews without reverting to command-and-control.
- Standardize metric collection across teams while allowing context-specific interpretation.
- Balance transparency with psychological safety by anonymizing team-level data in cross-program comparisons.
Module 7: Scaling Lean Practices Across Agile Portfolios
- Coordinate WIP limits across multiple Agile Release Trains to prevent system-level bottlenecks.
- Align portfolio epics with Lean objectives such as time-to-market reduction or operational cost savings.
- Implement enterprise value stream offices to oversee cross-program flow optimization initiatives.
- Negotiate funding models that support flow efficiency over project-based budget allocations.
- Resolve dependency conflicts between teams by facilitating joint planning with shared Lean goals.
- Adapt Lean-Agile frameworks during mergers or restructuring to maintain process continuity.
Module 8: Sustaining Lean-Agile Transformation
- Rotate Lean champions across teams to prevent siloed knowledge and promote shared ownership.
- Embed Lean coaching into team routines rather than relying on periodic external facilitation.
- Revise performance evaluation criteria to reward flow efficiency and systems thinking.
- Monitor regression to batch-and-queue behaviors during periods of organizational stress or leadership change.
- Update training materials annually to reflect evolving team challenges and Lean adaptations.
- Conduct quarterly value stream health checks to assess long-term adherence to Lean principles.