In traditional software development, final tests are planned in advance. During the test period, test and troubleshooting phases alternate until the finished product is finally ready for installation and use. Agile software projects run differently and challenge this step-by-step approach. Combining classical (software) test management with the requirements of an agile organisation is a methodical challenge, but also holds many opportunities.
It sounds simple, yet, it is of central importance: Software that functions without any error is good, as software errors cost time and money. That applies to standard software, but of course also to custom applications such as those used at many companies in day to day business. Through automated tests, it is possible to continuously measure and assure software quality. Undesired side effects of software changes can be directly identified and avoided through automated tests.
To those who deal with IT quality management, the questions „what is IT quality, actually, where and how is it measured, and where is it created?" very quickly arise.
According to the IEC 2371 standard, quality is the correspondence between the observed properties and the previously defined requirements of an observation unit. In the case of IT quality, the observation unit typically either is an IT component (server, switch, router, etc.) or an IT service.
Read more … IT quality improvement through release management?
Just like the call for order, safety, and planning, the call for quality in IT is always topical. This applies when large changes are ahead as well as when realignments and problems occur in normal operations. Each and every major change is followed by a consolidation, be it after a merger, a spin-off, an insourcing or outsourcing, or after periods of severe cost reduction. The next step is the call for an increase or reestablishment of quality.
Read more … Bringing costs and quality into the right balance with IT service improvement programs
