Petri Kainulainen

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 project. The goal of these methods is to ensure

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 individually based on to the requirements. What is the catch?

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 appearance and implementation groups is required to maximize the

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 done in software projects. These thoughts are the

It has been a while after I wrote about my first experiences of Macbook Pro and OS X. During this time I have been getting myself familiar with the keyboard (It has taken me surprisingly long to get used to the different keyboard layout and the “missing keys”) and figuring out what software is worth installing (and what is not). This entry contains