AMMEON – AL003: Getting Lean through Kanban
In this 2 day course, we delve into why Kanban works so well both as a work management and change management approach. We look at the benefits of Kanban compared to plan-driven approaches, particularly in complex environments with a lot of churn. We examine some of the theoretical foundations for empirical control methods, and the economic realities of software development and operations that make Kanban so compelling.
This is followed by a deep dive of Kanban practices and tools, including Value Stream Mapping, Visualization of Work Flow, Metrics (e.g. Lead Time & CFD), Limiting WIP, Managing Flow and Attaining Pull, Work Item Types, Classes of Service, Explicit Policies and Feedback Loops. This training course has an additional onsite coaching session with an experienced consultant to assist with implementing your new acquired skills into your workplace.
The course will include exercises to illustrate important concepts and a comprehensive Kanban simulation game to allow attendees experience concepts such as pull and flow first hand.
Who Should Attend
- Transformation Agents, Agile and Lean Champions
- Project Managers
- Developers, Testers, Analysts and other roles contributing to software development and IT operations.
Introducton to Agile & Lean
– Principles of Agile and Lean Software Development
– What is Kanban?
– Benefits of Agile and Lean Development
When to Use Kanban – SW Development; IT Operations
Key Concepts in Kanban – Variability, Cost of Delay, Theory of Constraints
Kanban Core Practices
What is a kanban system?
Demand Analysis – Defining customer-valued work items (deliverables)
What are the types of work you do?
What are the patterns of demand for your teams?
Kanban Boards (manual and electronic)
The Mechanics of a Kanban Board
Daily StandUps, Backlog Refinement, Operational Reviews
Cost of Delay
Service Level Agreements
Allocating Capacity to Classes of Service
Time is Money – the Costs of Queues
Cycle Time vs. Utilisation, Productivity & Efficiency
Settng WIP limits for smooth flow and short cycle time
Evidence Based Planning
Incremental Delivery – Prioritisation for Early Value
Input (Prioritisation) and Output (Release) Cadences
Identifying bottlenecks: Capacity constrained and Non-instant availability resources
Idenitifying the 7+1 Lean Wastes
Improving throughout through Theory of Constraints
WIP – Cumulative Flow Diagrams
Open Issues and Blocked Work Items
Gameplay – Each Team uses WIP Limits, Explicit Policies, Work Prioritisation, Classes of Service, Metrics and other Kanban practices to optimise the work flow through their Kanban system.
Simulation De-Brief – What did we learn?