Quality Management

Agile has always taken an uncompromising position in respect to quality. With an integrated quality approach, we have set international benchmarks in quality. We ensure the high quality of delivered software through the entire workflow.

Agile QA Tasks and Objectives
    • Elaboration and implementation of procedures and regulations for software development process based on the industry best practices and standards
    • Project life-cycle monitoring to ensure compliance with established processes and guidelines
    • Project quality verification and validation to ensure its correspondence with the client needs and expectations
    • Identify the requirements to be tested. All test cases shall be derived using the current Project Specification.
    • Establishment of an effective collaboration of all production participants
Independent QA Department

Agile’s QA department is an independent subdivision. Our QA team consists of skilled QA engineers and experienced testers that are involved into the projects on a dedicated or as-needed basis. QA engineers’ allocation depends on the project size and complexity. If it is required they can be easily switched from one project to another. Such flexibility let optimize project efforts and correspondingly the overall project budget. QA team is free from any pressure from the development team.

Key Processes
    • Full-Life-cycle QA Testing
    • Document and Code Reviews
    • Defect Reporting & Tracking
    • Configuration Management
    • Process Monitoring
    • Risk Management
Simultaneous Development and QA

Agile conducts quality assurance procedures throughout the full software lifecycle. QA team members are involved at all project iterations. Lead QA Analyst is allocated from the initial stage of the project and involved into initial business analysis and requirements specification. This simultaneous interaction of the development and QA teams ensures a better understanding of the project scope and the client’s business objectives. Typical QA lifecycle includes the following phases:

    • Initiation and Planning — the responsible QA person studies the project specification, starts test plan elaboration and plan assignment of the QA team members for specific tasks
    • First Review — initial testing of first development deliverables. The project test plan and test items refining (if necessary)
    • Second Review — Start second phase testing of build deliverables.
    • Iteration Audits — on-going testing of intermediate iterations builds
    • Final Verification and Validation — the final product thorough testing to ensure the final quality and readiness for deployment
QA process may include different test types to ensure increased QA depth:
    • Functional and Regression Testing
    • GUI and Usability Testing
    • Smoke and Sanity Testing
    • Accessibility Testing
    • Compatibility Testing
    • Load & Performance Testing
    • Stress Testing
    • Installation/Configuration Testing
    • System/Integration Testing
    • Security Testing
    • Internationalization/Localization Testing
    • User Acceptance Testing (UAT)