As you probably know already, I consider "new" methods like SCRUM a YAM, a Yet-Another-Method. And there are a lot of YAM's. Like potatoes they are root-vegs and you can find them everywhere in any vegetable shop. Very versatile and you can bbq, bake, smoke, boil, fry, grill or even eat them raw with the right recipes. Some have other bumps and dents but at the end of the day, they all taste more or less alike.
Well, coming back to earth, you know that a YAM, the Yet-Another-Method and not the vegetable, in the Application Development context is a box stuffed with techniques and tools of which probably most of the time more than 80% are "borrowed" from earlier emerged YAM's.
People keep asking me about industrialization with its means and its goals. Where it starts and where it ends. Whether it's a good or a bad thing and of course, what the consequences for our IT profession would be.
Well you know, I just have an opinion about it like anyone else so I don't have a clear scientific underpinned definition of true industrialization of IT but I'll give you a few angles to look at it. The first lines on Wikipedia about industrialization start like this: "Industrialization is the period of social and economic change that transforms a human group from an agrarian society into an industrial one. It is a part of a wider modernization process, where social change and economic development are closely related with technological innovation…”
SMACT-technology (Social, Mobile, Analytics, Cloud, Things) is already so woven in almost everybody's lives, that nobody complains about the drawbacks anymore. Admitted, looking at the numbers of people using it, the advantages of SMACT for the consumer are obvioulsy there. A few examples around those already impressive numbers: