What is concurrent engineering? Concurrent engineering is when activities are paralleled that could be sequenced. Concurrent engineering can help us deliver the product earlier since we have compressed the schedule by overlapping the various development activities.  There are certain risks associated with this way of working. To be successful and not incur massive rework, it […]

Recently, on twitter, I had an occasion to express my discontent for the word Pragmatic.  My spontaneous outburst so amazed me that I decided to explore this further.  The definition on dictionary.com[1] is: Of or pertaining to a practical point of view or practical considerations Philosophy of or pertaining to pragmatism Of or pertaining to […]

By Kim Robertson and Jon M. Quigley Leveraged Innovation Logistics Mike and Akio had been invited to one of the Genesis Test Equipment logistic repair depot by Lina Hendrik, the facility manager to discuss an idea she had regarding retrofit of a discontinued product line still widely used in an automotive niche market segment. As […]

The project organization should use the Configuration Management process to script the project and product growth – instead of just the version control. In this way the product content is adjusted formally from the learning that should have happened in the prior work.

The olden days… A long time ago (seemingly) I graduated from university with my engineering degree.  I was lucky, my first job was with a small company and I performed many roles as it applied to developing their new product line.  The product was an embedded strand process control unit. This unit would control older […]

Models are not new, and neither models in the employ of product development. Product development has always had some basis in discovery and always will. If everything had such a high degree of certainty, likely the product or endeavor has already been done. Developing new things ceaselessly brings questions. To be effective, we want to answer these questions as quickly and as certainly as possible.

In conventional project management, it is called the white book. In agile, it is known as the retrospective. Both the retrospective and the white book serve the same purpose that is to learn from the past and improve the future. Though the objectives may be similar the manner and perhaps the efficacy are quite different.