Comments on: A Kanban System for Sustaining Engineering http://leansoftwareengineering.com/2007/06/26/a-kanban-system-for-sustaining-engineering/ Essays on the Continuous Delivery of High Quality Information Systems Wed, 07 Jul 2010 10:00:18 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Corey http://leansoftwareengineering.com/2007/06/26/a-kanban-system-for-sustaining-engineering/comment-page-1/#comment-80 Corey Thu, 16 Aug 2007 03:45:09 +0000 http://leansoftwareengineering.com/2007/06/26/a-kanban-system-for-sustaining-engineering/#comment-80 Yes, you will certainly see these kinds of concepts show up in domains where <em>throughput</em>, <em>latency</em>, and <em>buffering</em> are first-class design considerations, namely telecommunications systems. Designs that feature pipeline or streaming architectures will also share many conceptual similarities to lean production systems. Remember that it was mostly telecom folks that came up with all of this queuing theory business in the first place! Do a web search on kanban+petri+net and you'll get some fascinating hits. Yes, you will certainly see these kinds of concepts show up in domains where throughput, latency, and buffering are first-class design considerations, namely telecommunications systems. Designs that feature pipeline or streaming architectures will also share many conceptual similarities to lean production systems. Remember that it was mostly telecom folks that came up with all of this queuing theory business in the first place!

Do a web search on kanban+petri+net and you’ll get some fascinating hits.

]]> By: Kevin http://leansoftwareengineering.com/2007/06/26/a-kanban-system-for-sustaining-engineering/comment-page-1/#comment-79 Kevin Wed, 15 Aug 2007 21:03:50 +0000 http://leansoftwareengineering.com/2007/06/26/a-kanban-system-for-sustaining-engineering/#comment-79 Do you know of any efforts to apply "lean" concepts (single piece flow, setup/change over reduction, elimination of Non-Value add,...) to actual application design? As more systems are "electronifying" paper transactional systems, I have seen many systems built to process large batches of items through a sequence of processes. The same total throughput improvements that were seen in manufacuring and then transactional processes should be able to be realized in IT, but I haven't seen anything on it. Do you know of any efforts to apply “lean” concepts (single piece flow, setup/change over reduction, elimination of Non-Value add,…) to actual application design? As more systems are “electronifying” paper transactional systems, I have seen many systems built to process large batches of items through a sequence of processes. The same total throughput improvements that were seen in manufacuring and then transactional processes should be able to be realized in IT, but I haven’t seen anything on it.

]]>