Blog of a Boston-based IT Consultant

<iteration 1>

The Just-In-Time philosophy minimizes waste. Championed by Toyota, the JIT approach aims to not only optimize process, but simultaneously reveal and strengthen weak links in the chain of process.

Polymorphic Process is something I made up just in time to write this (the phrase, anyhow). I am not sure that it makes sense. However, if you get what I mean, it is good enough and I didn’t think too hard about it. There was no waste here. Most authors would edit as they go. However, this is an exercise in singular iteration. Thereby, it is not an iteration at all. It is polymorphic process, manifested as I began typing or perhaps… as I began thinking that I would write tonight.

But that is not where Polymorphic Process stops. It doesn’t stop. It doesn’t start except for when we choose to call something Initiation. When is Just-In-Time? When are Processes and SubProcesses Initiated in a Polymorphic Process model?

Yeah. Then.

So what does this mean? In software development, you can think in terms of linear progress (and even particular ones, with particular names and certifications and cool initials to put in your Outlook signature), or you can think amorphously. Both will work. One requires faith, like church. The other requires faith, like Atheism.

I love this stuff. Sometimes. When I write these posts, I love it Just-In-Time. I realize that I lack discipline when I go three months without writing. The water in my little ocean has evaporated and the rocks are showing. So I dive in, because what else can you do but get involved, and I employ a polymorphic process.

Awkward endings are part of the game.

</ iteration 1>

Best,

Josh

Project Management | RSS 2.0 | Comment it , or trackback this post.