Quality policy
Quality built into every stage of the work
Our quality management system is a set of engineering and management practices that protects the quality of what we deliver throughout the whole workflow, from the first requirement to the final release.
Objectives
What our quality system is for
Four objectives that apply to every project, whatever its size or engagement model.
- 1Define and apply procedures and rules for our development process, based on industry standards and best practice.
- 2Monitor each product's lifecycle to make sure the agreed processes and guidelines are followed.
- 3Verify and validate every product, so it meets your business needs and expectations.
- 4Keep collaboration between everyone on the project team clear and effective.
Approach
A complete approach to quality
Step 1: Quality planning
Before work starts, a quality plan sets out the standards, rules, procedures, guidelines and tools that apply to the project throughout its lifecycle.Step 2: Quality assurance
Established processes evaluate how the project is performing, check that quality standards are being followed and confirm that deliverables match your requirements.Step 3: Quality control
We measure performance trends to find defective code early, and verify that every deliverable is complete, correct and of high quality.
Independent QA
An independent QA department
Quality assurance is its own department, separate from the teams that build. It is made up of skilled QA engineers who join projects full time or on demand.
How many engineers a project gets depends on its size and complexity, and they can move between projects when needed. That flexibility keeps the effort, and your budget, where it should be.
The QA department is responsible for
- Full-cycle QA testing
- Testing at every stage, from the first build to the release.
- Document and code review
- Requirements, designs and code reviewed by someone other than their author.
- Defect tracking
- Every issue logged, prioritized and followed until it's fixed and verified.
- Configuration management
- Versions, environments and releases kept under control, so what was tested is what ships.
- Process monitoring
- Checks that the agreed processes are followed on each project, not just written down.
- Risk management
- Risks identified early, tracked and acted on before they become problems.
Want to start a project?
Tell us what you want to achieve. A strategist reads every request and replies within one business day with next steps, or a straight answer if we aren't the right fit.