Through Early Testing to High Quality

In many organizations, testing, regarded as quality verification, begins once code has already been completed. However, many studies have shown that errors found in requirements are the leading cause of project failures, defects and rework. Even though many companies use some methods of requirements management and some forms of software quality testing, most of them cannot (or do not) link these items together.

While searching for an application life-cycle management (ALM) methodology that might give us an answer to these problems, Requirements-Based Testing (RBT) emerged as a possible solution. Why? Because RBT provides a set of quality assurance activities and management tools that enable getting requirements right from the outset. Thus, it improves the efficiency and communication between developers and testers.

This presentation is about lessons learned while introducing requirements-based testing methodology, in order to put the project under the control and deliver applications on time, whithin a planned budget and with a satisfied client.

Predrag Skokovic, Execom, Serbia

Predrag is a Test Manager at EXECOM. With more than 10 years of experience in IT business, he is one of the most skilled company leaders. Currently he leads testing team on international projects.

Predrag is a regular speaker at international conferences and a guest speaker at the University of Novi Sad.

His professional fields of interest are test process improvement and automated testing.