Comments on: Why the Toyota Product Development System is a thing of the past http://codemonkeyism.com/why-the-toyota-product-development-system-is-a-thing-of-the-past/ Sat, 13 Mar 2010 16:12:40 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: TPS « The Data Warehouse Pages http://codemonkeyism.com/why-the-toyota-product-development-system-is-a-thing-of-the-past/comment-page-1/#comment-237573 TPS « The Data Warehouse Pages Fri, 31 Jul 2009 11:56:43 +0000 http://www.codemonkeyism.com/?p=773#comment-237573 [...] Thanks to a posting at codemonkeyism.com I bought Taiichi Ohnos book about the Toyota Production System. Originally published in 1978 it [...] [...] Thanks to a posting at codemonkeyism.com I bought Taiichi Ohnos book about the Toyota Production System. Originally published in 1978 it [...]

]]> By: Rayk http://codemonkeyism.com/why-the-toyota-product-development-system-is-a-thing-of-the-past/comment-page-1/#comment-235664 Rayk Sun, 12 Jul 2009 20:16:41 +0000 http://www.codemonkeyism.com/?p=773#comment-235664 No suggestion but a warm thank you for that posting. It may resolve the problem I have with interlinking Scrum idead with my Data Warehouse world, which is beside commo software development too (IMHO). What's yours? Regards Rayk No suggestion but a warm thank you for that posting. It may resolve the problem I have with interlinking Scrum idead with my Data Warehouse world, which is beside commo software development too (IMHO). What’s yours?

Regards
Rayk

]]> By: Jeff anderson http://codemonkeyism.com/why-the-toyota-product-development-system-is-a-thing-of-the-past/comment-page-1/#comment-235652 Jeff anderson Sun, 12 Jul 2009 16:38:25 +0000 http://www.codemonkeyism.com/?p=773#comment-235652 I like the thinking behind most of the article but I disagree with the distinction about when to use agile I have had most of my recent experience in legacy integration and service development (soa) style projects The value of agile and lean, while used differently on web and integration projects, are the same 1 reduce waste through small implemenaton cycles that provide enough feedback to continually optimize the solution ad te approach 2 increase quality through signals and automation 3 focus on workers and adaptable processes I could go on but I think you know about all the finer points of agile /lean the point being (IMHO) is that agile in some respect has value to any style of software development program, at least int experience I like the thinking behind most of the article but I disagree with the distinction about when to use agile

I have had most of my recent experience in legacy integration and service development (soa) style projects

The value of agile and lean, while used differently on web and integration projects, are the same

1 reduce waste through small implemenaton cycles that provide enough feedback to continually optimize the solution ad te approach

2 increase quality through signals and automation

3 focus on workers and adaptable processes

I could go on but I think you know about all the finer points of agile /lean

the point being (IMHO) is that agile in some respect has value to any style of software development program, at least int experience

]]> By: stephan http://codemonkeyism.com/why-the-toyota-product-development-system-is-a-thing-of-the-past/comment-page-1/#comment-234360 stephan Tue, 30 Jun 2009 18:16:32 +0000 http://www.codemonkeyism.com/?p=773#comment-234360 @Sensei of Flow: "Dr Allen Ward in his outstanding book “Lean Product and Process Development” observes that the role of Product Development is NOT to develop products (how strange is that), but to create the *operational values streams* (aka manufacturing, production value streams - for car companies at least) through which products can be made, sold, delivered, marketed, supported, etc." Good insight, perhaps it helps with my learning about the role of product development. The books seems hard to get here in Germany :-/ "Also, the TOC (Theory of Constraints) literature has many [...]" Any book suggestions? Cheers Stephan @Sensei of Flow:

“Dr Allen Ward in his outstanding book “Lean Product and Process Development” observes that the role of Product Development is NOT to develop products (how strange is that), but to create the *operational values streams* (aka manufacturing, production value streams – for car companies at least) through which products can be made, sold, delivered, marketed, supported, etc.”

Good insight, perhaps it helps with my learning about the role of product development. The books seems hard to get here in Germany :-/

“Also, the TOC (Theory of Constraints) literature has many [...]”

Any book suggestions?

Cheers
Stephan

]]> By: Daily Links for Tuesday, June 30th, 2009 http://codemonkeyism.com/why-the-toyota-product-development-system-is-a-thing-of-the-past/comment-page-1/#comment-234332 Daily Links for Tuesday, June 30th, 2009 Tue, 30 Jun 2009 11:38:07 +0000 http://www.codemonkeyism.com/?p=773#comment-234332 [...] Why the Toyota Product Development System is a thing of the past | Code Monkeyism [...] [...] Why the Toyota Product Development System is a thing of the past | Code Monkeyism [...]

]]> By: Flowchainsensei http://codemonkeyism.com/why-the-toyota-product-development-system-is-a-thing-of-the-past/comment-page-1/#comment-234255 Flowchainsensei Mon, 29 Jun 2009 11:23:25 +0000 http://www.codemonkeyism.com/?p=773#comment-234255 Insightful post! Helps draw some distinctions between product design/development (such as TPDS) and production (manufacturing / TPS). Dr Allen Ward in his outstanding book "Lean Product and Process Development" observes that the role of Product Development is NOT to develop products (how strange is that), but to create the *operational values streams* (aka manufacturing, production value streams - for car companies at least) through which products can be made, sold, delivered, marketed, supported, etc. Also, the TOC (Theory of Constraints) literature has many examples of make-to-order businesses (furniture, software, etc) and productive ways to organise those (with pull, flow, cadence and limited wip featuring highly). HTH Cheers FlowchainSensei Insightful post! Helps draw some distinctions between product design/development (such as TPDS) and production (manufacturing / TPS).

Dr Allen Ward in his outstanding book “Lean Product and Process Development” observes that the role of Product Development is NOT to develop products (how strange is that), but to create the *operational values streams* (aka manufacturing, production value streams – for car companies at least) through which products can be made, sold, delivered, marketed, supported, etc.

Also, the TOC (Theory of Constraints) literature has many examples of make-to-order businesses (furniture, software, etc) and productive ways to organise those (with pull, flow, cadence and limited wip featuring highly).

HTH

Cheers
FlowchainSensei

]]>