In my previous article called When Business Dictates Technology Selections, I wrote about arguments, which are used by management to overrule the technology selections made by technical staff. I also tried to describe, why I feel that managers should have control over technology selections. I have to admit that I was not doing a very […] Read more

In my previous article called: Quality Management of Software Projects, Part 2: Preemptive Strike, I described the quality management actions, which reduce or eliminate quality problems of a software project, when taken before the project is started. This entry describes the quality assurance methods, which should be used during the implementation phase of a software […] Read more

A few days ago I found myself in the middle of an argument concerning the best build tool for Java projects. Somewhere during the discussion, I realized that there is no tool, which is best in every possible situation. Naturally, this leads into a conclusion that the best tool for the job must be selected […] Read more

In my previous article, I introduced a definition for software quality, and described the challenges caused by a conflict of interest between different stakeholders. As promised, this article will describe preemptive measures, which reduces or eliminates quality problems of a software project, when taken before the project is actually "started". Cooperation between the members of […] Read more

As reported by Computer Business Review Online, the results of the latest Standish Group report are devastating. According to the Standish Group, the number of last year's software project failures were the highest in five years. This makes me wonder, whether there is something essentially wrong with the way project management and quality management is […] Read more