Because our services are defined and evaluated on test results.  Quality assurance, and quality control is a leitmotiv within every step of our development cycle.  We also offer this service independently from the actual development.  Starting up-front from the requirements, we define the test plan and test cases to be applied to the software deliverable(s).  It gives you an independent view on the actual quality of the development done, wheter in-house or outsourced.  Actual tester profiles are not easy to find, on the market nowadays.  Skelia offers a service which solves this issue as well as the variation of workload linked to IT deliverables cycle.
 

This service is based on our complete project life cycle delivery. It is tightly linked to the requirements qualification phase. 

Within the complete life cycle delivery we use the quality assurance to validate the deliverables against the requirements produced with our customer, and this qualification is part of the contract delivery.

We also offer this service as a separate bundle, the development being done internally by the customer or outsourced to another company.  To ensure a smooth  and efficient process, QA work starts right from the beginning of the project defining the rules of the game and making sure every actor agree with them.  We value QA work not by finding bugs or issues but by avoiding them at the first stage as it is more efficient in terms of time and money.  It brings some difficulty to measure our efficiency but in short if the development matches your needs and you have not heard about us then our work was very efficient.

Because avoiding is always better than repairing, we collaborate closely with business users to actually understand correctly the requirements and define test cases together with them.  This first phase often brings many changes within the requirements and raises business issues  just by bringing real every day test cases and showing how they should be handled based on the requirements.  These test cases are made public to the business community for review, and to the developers as test cases and the definition of the expected results can help them to better understand business requirements.  Results of these test cases are used for evaluating the software delivered. 

We then focus on building our test cases and automating them as much as possible, so that the developers can see the results as early possible in their development process. 

Changes are a normal part of business nowadays.  The market is evolving fast and changes have to be supported.   These changes have a cost, but again, the earlier they are identified the more efficiently they can be managed.  Change management is part of our methodology having worked already in fast evolving markets.