Expecting to read about our quality statement you probably want to know how we are dealing with ISO certification and such. Well in that case we are in the process of ISO certification and hope to complete this early 2008.

 

 

But basically what quality means to us is a satisfied client, nothing more and nothing less, for whom we have been able to deliver a solution that meets the business requirements at reduced costs. Therefore we rather present our viewpoints on how we manage the quality of our projects, rather than how good we are.

 

 

We spend a great deal of time and efforts to gather and create the most accurate and complete requirements because poor requirements can cause a lot of damage to any project. And we ask our clients to sign for the results. During development, the teams constantly analyze the quality of their work and every team member has a personal responsibility for the successful completion of the entire project.

 

Perform risk analysis

 

Risk always goes with any software development project. We always analyze the risks before the start of each project to ensure we can deliver successfully. That’s why we never forget to analyze and act upon beforehand:

Peer reviews

 

Our quality management procedures use the simple but time -proven principle that two heads think and see better than one.  Our approach includes peer reviews of the project process and deliverables at all stages during the development life cycle. Also, the quality of the results delivered during a project is a major item in our personal performance appraisal system.

 

 

With every release, we perform a detailed analysis of the results and compare them with the expected outcomes. In this analysis, we take into account the feedback from clients - complaints, recommendations, suggestions, approvals – all these are carefully recorded and analyzed so to be included in our plans for continuously improving quality management practices.