Quality Assurance

Intechno had built its processes on solid quality management foundations based on global standards and recommended practices and in accordance with ISO27001 and CMMI procedures; and also based on professionalism, collected opinions and suggestions from prospects and clients, professional critics and evaluators on a smaller scope.

These quality concepts married and implemented have positively affected all departments of our organization ranging from marketing and Sales, Customer Service, Project Management and Delivery, Human resource, Research & Development, and our overall management.

Our Quality Assurance process is integrated in the IRDM (Intechno's Rapid Development Methodology) and absorbed in the Agile FDD, XP and Scrum methodologies we practice. Quality management is an exclusive stage between our Project management procedures and it supersedes the project management process. This essential process on development has its stages being.

1. Quality Plan

We lay out a plan depending on the kind of project in question. We determine what scope of quality assurance we need. For example, the quality assurance resources needed to be invested on this project. This plan also includes communication model enhanced by our collaborative project management culture.

2. Quality Assurance Framework

A frame work is then drawn to guide the practices through the whole project. This framework determined by nature of project and usually positively affects objectives in Accordance to Requirements, coding standards, interface theme and quality, Critical features and functions (to be done first), Response time, User-friendliness, documentation standard and many more depending on the nature of the project.

3. Quality Control measures

This level defines how to achieve the set quality according to the framework. We also assign who reports what and under what circumstances. These measures are followed consistently through respective stages of the project till delivery, to ensure that all QA tasks are followed in all stages of the project.

4. Corrective Guidelines

In this level, we identify what should be done if there ever be an out-of-step error, to reassure the quality in that particular task. Corrective steps to reassure quality also connote that these steps do not affect the project delivery timeframe.

5. Testing Type Definition

Different projects include different kinds of tests. For example, a web project may include "browser compatibility test" while a desktop project may not. This stage defines what kinds of tests apply to the project at hand. And also defines test.

6. Testing Checklist

Testing checklists define what tests we do in the appropriate stages where tests are needed in the projects. For example functional testing defines a list of objects and functions the system must have. Also on interface, user-friendliness is analysed with this list.

7. Evaluation Checklist

This stage is a list of economic and commercial values that the system must fulfill, handled by our professional business analysts, QA and project managers to ensure that the system objectives are married with economic objectives to create a balanced list of all relevant elements of business value. Our evaluation checklists include Business benefit Evaluation, Requirement vs. Outcome Evaluation, Commercial viability, and so on.

8. IP security and Project confidentiality measures

We plan the assurance of security throughout the project development process. These measures will affect source code, documentation, system architechture and confidential client information and many more project elements. The IP protection applies to packaging and delivery stages. Please read more about our IP protection.

We believe that quality is the only element that creates satisfaction. Satisfaction is the element that creates partners and boosts our profile. We have as our mission and endless quest to maintain quality process in every project of every nature of services.