Quality Assurance Policy
Purpose
This policy describes how RODMENA LIMITED assures the quality of the software and the consultancy it delivers. It describes what we actually do, not a certification.
How we work
- Requirements first: every piece of work starts as a written specification (we use the EARS notation), so that what "done" means is agreed before work begins.
- Tracked work: each request is a ticket with acceptance criteria, followed from open to closed, with the evidence of how it was verified recorded on the ticket.
- Automated tests: changes are covered by automated tests, which must pass before release.
- Review: changes are reviewed before release.
- Continuous integration: every change to a product runs through our CI service (ci.rodmena.co.uk) before it can be released.
- Verified in production: after a release we check what is actually being served, not only the source code.
- Customer acceptance: client deliverables are accepted against the specification agreed with the client.
- Learning from defects: when something goes wrong we fix the cause, and record what we learned so it does not happen again.
Complaints
A client who is unhappy with our work can raise it through our requests and complaints route. Every complaint is acknowledged, investigated and answered.
Review
The director owns this policy and reviews it at least annually.
See also our Secure Software Development Policy.