During the discussion I proposed cycle time as one of the areas in which public software can make a contribution. One of the common definitions of cycle time is the time it takes to execute a process from start to finish. Developing a product, assembling an automobile engine, cooking a gourmet dish, or adding a new disk to a system all have a process associated with them.
Processes are simply the steps or actions taken to transform inputs to outputs.
Sometimes, these processes are defined, articulated, and documented in great detail, while others simply exist in our conscious mind. As computer professionals, we are process-driven every day. I also pointed out that dealing with short cycle times or even reducing them is a significant issue, especially in the computer arena. The theory is that by reducing cycle times, we can bring products to market faster, improve quality, and boost productivity. Makes sense in theory, but doing it in practice is next to impossible unless you take a serious look at the processes and subprocesses involved.