Integration of tools and methods of working are highly appreciated but cause the usual dangers of complexity. In a world of continuous improvement this is in fact the last thing you would want. The ultimate goal should be “Standardize to free energies” (for the real challenges) and this implicates a high degree of simplicity to keep things flexible. After all, you would want to exchange one accelerator for another without a very difficult reintegration project.
Secondly, there is something contradictorily about a standard method for Software Development projects. Wasn't it true that a project should deliver something unique? And shouldn't a uniqe result not be developed by a unique approach? After all, the plan is called "Plan-of-approach". If it was all standard, it would have been called it differently. Well, I admit that there are other names too. Anyway, in RUP this is addressed by introducing a Process Engineer to make a Development Case. That's why RUP actually is not a method at all, but a framework which should be projected onto the unique situation.
In a dark spot of the universe finally the last planet is conquered. The hiding and only left IT-professional with a "not-invented-here" syndrome (and a hangdog look) was captured by the authorities. For so many years we have suffered from this nasty virus which showed up the minute the second programmer started to help the first one. The very first computer had the virus built in by giving the opportunity to people to make everything they wanted with just their imagination. No additional raw material, energy or tools. And within that imagination, everything can be improved. Always. Even it is not very different or worse, not very authentic. Like good old Spock used to say: "Not really logical, but quite human".
At last we can avoid the chance that the evil influence of this decease keeps us into fear slowing us down in our developments. Re-using our intellectual capital will make it evolve to a higher platform making this virtue its own reward.
Mankind will sigh of relief. Finally we have enough time, money and energy to face our real challenges for growth. Economically, intellectually and spiritually . . . . . . .
Today there is a certain appetite to use agile methods again for software development. The promise of being faster, smarter, cheaper of course no one wants to miss. But in fact there is already a long history of doing projects the agile way. And I don’t mean that the more “classic” method of not using a method at all, is agile too . Well known Dutch thoughtleaders like Ron Tolido and Sander Hoogendoorn already wrote some books about agile software development quite a few years ago. Other professionals like Birgit Klomps and Tommes Snels became experts in workgroups and softskills, may be the major pillars of agile projects. In fact, a number service providers, just like my own employer, already had project centers with agile development as one of their key spearheads. I'm still happy a was heading one of them in those days.
The profession of Information Technology is at the beginning of its next phase: true industrialization. And true industrialization is a lot more then offshoring, transfering work to low-labourcost countries, alone. It's also about standardization, automation and re-use but what's even more important, about a reproducable and predictable process of designing, producing and implementing software. Although some are still a bit reserved and may be even on the defensive, the bar is already high and now even pushed further due to the current economic slowdown. The demand is a lot more value for less money,within a shorter time frame. Productivity is the keyword but in fact it has many faces. Time and money are not always interchangeable anymore mostly due toavailability of current high technology standards. And on top of that, producing software efficient is not the same as producing effective.
Suppose you have an issue with your family. This evening the family is going to be together for their annual event and you've decided to write them a letter. It has to be a sensible and sensitive story, say 1 page of about 50 to 60 lines. You have only one chance. It has to be good. Waiting for another year is probably too much for an already fragile relationship. You have around 5 hours left.
Integration of tools and methods of working are highly appreciated but cause the usual dangers of complexity. In a world of continuous improvement this is in fact the last thing you would want. The ultimate goal should be “Standardize to free energies” (for the real challenges
) and this implicates a high degree of simplicity to keep things flexible. After all, you would want to exchange one accelerator for another without a very difficult reintegration project.
. Well, I admit that there are other names too. Anyway, in RUP this is addressed by introducing a Process Engineer to make a Development Case. That's why RUP actually is not a method at all, but a framework which should be projected onto the unique situation.
Stardate 34298.6 – Captain’s Log – 
The profession of Information Technology is at the beginning of its next phase: true 
Suppose you have an issue with your family. This evening the family is going to be together for their annual event and you've decided to write them a letter. It has to be a sensible and sensitive story, say 1 page of about 50 to 60 lines. You have only one chance. It has to be good. Waiting for another year is probably too much for an already fragile relationship. You have around 5 hours left. 
