Now back to Software Engineering. One of my French bosses said last year in a dark voice:"Let me tell you one thing. When I talk about industrialization, I mean India. Full stop!". Well, I think that is a little short-sighted and I can only hope it was meant as a short term "strategy" to get off-shoring going against the general opinion (not in the least in France ). A major change like implementing offshoring, touches a lot of people. Focussing step by step on clear intermediate results helps to get the big award in the more long term. So in this case, for the time being, I agree

But of course industrialization can be al lot more and most of the time a combination of measures like:

• Indeed off-shoring: transfering work to low-labourcost countries reduces the overall costs (even if it's less efficient due to more communication and overhead)
• Standardization of processes: when more people are involved or even when you work always alone, when activities re-occur, doing things the same way over and over again makes it at least more simple. 
• Automation: when activities can be done by machines or software generating (intermediate) deliverables
• Re-use: assembling with earlier built components and frameworks.
• . . . and a lot more like continuous improvement etc. etc.

It depends on what kind of productivity improvement u really want. One could argue that work becomes more easy, less paid for, dull, uninteresting. Yes, thats true, when u still want to produce the stuff u did! But what about designing and building industrialized processes? Or moving up in the value chain? Create more functionality for the client with more business value? Or focus more on the productivity improvement of the end-user? There is only one drawback. U have to change

Be first to comment this article

Write Comment
Name:
Comment:
Code:*