Quality Assurance Policy
Purpose
This policy describes how RODMENA LIMITED assures the quality of the software and consultancy it delivers. It describes what we actually do and is not a certification.
How we work
- Requirements first: work starts as a written specification in the EARS notation, and what "done" means is agreed before the work begins.
- Tracked work: each request is a ticket with acceptance criteria, followed from open to closed, with a record on the ticket of how it was verified.
- Automated tests: changes are covered by automated tests, which must pass before release.
- Review: changes are reviewed before release.
- Continuous integration: changes to our products run through our CI service (ci.rodmena.co.uk) before they can be released.
- Verified in production: after a release we check what is actually being served as well as 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, to stop it happening again.
Complaints
A client who is unhappy with our work can raise it through our requests and complaints route. We acknowledge, investigate and answer every complaint.
Review
The director owns this policy and reviews it at least annually.
See also our Secure Software Development Policy.