David J Anderson's A Kanban System for Software Engineering Workshop October 1, 2009

David Anderson is thought leader in managing effective software team. He is a board member and founder of the APLN and signatory of the project management Declaration of Interdependence. David is one of the originators of Kanban.

Kanban is a new lightweight approach to software development that transfers principles from the Lean Production/Toyota-Production-System to the software development. In this context, two rules are defined:

1. Each process takes work from the previous process (pull principle) in order to avoid overloading.
2. Work in progress is restricted so that no expensive stocks accumulate.

This intensive 2-day Kanban workshop with David J Anderson provides an introduction to Lean, Pull Systems and Kanban and will explain how established industrial engineering theory can apply to software development process.

You will learn how Kanban can be introduced with relatively little effort into existing software development environments and how it works with a strong division of labour. Upon completion of this Kanban workshop, you'll understand how Kanban delivers an useful perspective to consider the entire value chain beyond the pure software development.

LEARN HOW TO:

* An introduction to Lean, Pull Systems and Kanban
* 4 areas of focus to deliver success
* Value Stream Mapping
* Process Flow Tracking
* Implementing different classes of service
* Implementing a culture of continuous improvement (Kaizen)
* How established industrial engineering theory can apply to software development process
* Controlling WIP
* Identifying bottlenecks
* Classifying bottlenecks as capacity constrained resources or non-instant availability resources
* Managing bottlenecks appropriately for improved throughput
* Understanding transaction and coordination costs in a kanban process
* Defining release and input cadence for a kanban system
* Negotiating service level agreements with customers
* Using Metrics and Reporting to drive continuous improvement
* Establishing policies to prevent abuse and gaming of the kanban system