Release late, release rarely

Meanwhile I am looking back to more than 25 years of programming, and more than a decade I spent in a very sensible area where quality (in the sense ofnbsp;zero failures) plays a big role.nbsp;So call me sensible for quality. For long years we (i. e. developers) had hard work to do using simple command lines tools like vi etc., but meanwhile there are great, even free, tools making our lives much easier. So one should think that the freed time was spent into quality. The reverse is the case. The more I look at professional software products, the more I see, sorry to be rude, simply: crap! The question is:nbsp;Why is that? Having some insight into several bigger and smaller stakeholders, including my own participations to some Open Source projects lead by my self, Sun, Oracle, Bull, Microsoft, and some more, and looking at the work we are doing in my company and its affiliates and subsidiaries, gives me some feeling where the root of the evil is located: In the organization of the project. Gee! I can tell you how I hated to attend to thosenbsp;boring, mandatorynbsp;business organization classes at college back in the 90ies. But hey, looking back from now I need to say: Those profs where justnbsp;right! Fullstop. Quality is directly related tonbsp;your project#039;s organization (which is the way you organize people#039;s way of working, not the way younbsp;imagine the r...

Date: December, 29 2010
Url: http://www.java.net/blog/mkarg/archive/2010/12/29/release-late-release-rarely

Others News