Time is in short supply. If you want to convince the programmer to spend her time fixing your bug, you may have to sell her on it. (Your bug? How can it be your bug? The programmer made it, not you, right? It's the programmer's bug. Well, yes, but you found it so now it's yours too.) Sales revolves around two fundamental objectives: motivate the buyer (make her WANT to fix the bug); and overcome objections (get past her excuses and reasons for not fixing the bug). This presentation shows you how. (This presentation is available in PowerPoint and PDF format. Please read the usage and licensing information that precedes the content.)

This is a list of important things to review before and verify during a software release cycle. You may use it as-is or customize it for your situation.

Risk management must be fully integrated into all the development and maintenance processes for systems. It involves more than applying risk assessment methods to identify and evaluate system risks. To explain this broad approach to risk management, this paper discusses the way in which Requirements Driven Management (RDM) methods contribute to handling risks.

Defect counts are often considered as measurements of product quality. However, the most important defect count in that respect is by definition unknown; the number of undiscovered errors. Defect counts can be used as indicators of process quality. In doing so, one should avoid assuming simple causal relations. Defect counts can provide useful information but have to be presented with care.