Slow Down to Speed Up Workshop & Discovery Session Silicon Valley Code Camp October, 2009

Welcome to Agile AeroSpace (first shift) Build some airplanes Do a little cost accounting

Build some airplanes

Do a little cost accounting

Some Questions Was anyone idle during the first shift? What were the results? How much money did you make (or lose)?

Was anyone idle during the first shift?

What were the results?

How much money did you make (or lose)?

Let's Slow it Down a Little (second shift) Go no faster than the slowest operation Do a little more cost accounting

Go no faster than the slowest operation

Do a little more cost accounting

Same Questions Was anyone idle during the second shift? What were the results? How much money did you make (or lose)?

Was anyone idle during the second shift?

What were the results?

How much money did you make (or lose)?

Some Basic Definitions Throughput The rate at which a system generates money through sales . Inventory All the money that a system has invested in purchasing things it intends to sell . Operating Expense All the money a system spends in order to turn inventory into throughput .

How to Stay in Business Throughput Inventory Operating Expense

So What Does All This Have To Do With Developing Software? Software development is not the same as manufacturing

Software Development is About Creating and Sharing Knowledge Knowledge is the Inventory of software development People consume knowledge at their own rate Creating knowledge faster than it can be consumed does not increase throughput

Knowledge is the Inventory of software development

People consume knowledge at their own rate

Creating knowledge faster than it can be consumed does not increase throughput

Questions ?

5 Steps Identify the system's bottlenecks. Decide how to exploit the bottlenecks. Subordinate everything else to the above decision. Elevate the system's bottlenecks. If, in a previous step, a bottleneck has been broken, go back to step 1. (From The Goal, page 301)

Identify the system's bottlenecks.

Decide how to exploit the bottlenecks.

Subordinate everything else to the above decision.

Elevate the system's bottlenecks.

If, in a previous step, a bottleneck has been broken, go back to step 1.