Categories

A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

Not pushing the team too hard – a fine balance that can be easy to miss – Part 1

The topic for this post came up from a recent discussion that we started having. The managers of the team were astounded when, at yet another weekend, when members of the team were called for work (since yet another milestone was approaching), almost 90% of the team came up with excuses individually, and finally, the […]

Bug ageing – why it is important to follow in a software project – Part 3

In the previous 2 instances of this post (Bug ageing and software processes), I have been talking about the need to measure how much time it takes for the bugs generated by the QE team to get fixed, and to see whether taking more time for fixing such bugs is seen as a problem. In […]

Bug ageing – why it is important to follow in a software project – Part 2

In the previous post (Bug ageing and software projects), I talked about the concept of bug ageing and why it is important. In this post, I will continue on that topic and write more about this area. One of the biggest problems with bug ageing is that the more time there is between when a […]

Bug ageing – why it is important to follow in a software project

First of all, what is bug ageing ? Well, in a very broad sense, bug ageing is the amount of time that a bug is with a certain person. A bug can follow many different paths during its history – the bug can be with a developer, pending for the bug to be fixed. The […]