Optimizing workflow for
overall throughput

One of those things that "everybody knows" (but nonetheless turns out not to be so) is that if everyone on a team works at their own top capacity, producing as much as they individually can, then the team is at its most productive.

The problem with the above scenario may lie in how we define productivity, which turns out to mean more than just "producing things." Increasing productivity actually has to do with achieving greater overall throughput for your entire development organization, not just for individual team members.

If you think of your development process as a series of dependent operations, you'll have a bottleneck somewhere that limits the rate of production for the entire process. Identification and exploitation of that bottleneck can make the difference between being productive and being wasteful.

A workshop covering optimizing workflow will contain simulations and interactive discussions addressing the following issues: