One interesting idiosyncrasy of the software development industry is that the open source movement has created a number of development tools, which can be used to develop computer software free of charge. In some cases, this has been even used to justify the selection of a technology X over a competing technology Y. Even though […] Read more

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