Line C · Run
Delivery standards
These standards apply to every engagement. They are written so you can check them yourself — ask at any point to see the evidence.
Standards board
Show standards for:
- Every change is reviewed by a second developer for correctness and readability before merging.
- Automated tests cover business rules and run on every change.
- Formatting and linting are enforced by tooling in continuous integration.
- Dependencies are justified in writing and kept up to date.
- Accessibility target: WCAG 2.2 AA, checked with automated tools and manual keyboard and screen-reader passes.
- All states designed: empty, loading, error and success.
- Plain-language labels tested with users before release.
- Releases in working hours with a written rollback plan.
- Secrets never in code; credentials rotated at handover.
- Personal data minimised and documented in a data map.
- Run-book maintained for deployment, backup and restore.
Definition of done
An increment is done when it works as described in its plain-English definition, has passed review, has tests for its rules, has updated documentation, and has been accepted by you in a preview environment. Not before.
Communication
- Single contact
- One named person responsible for your project.
- Written summaries
- After each review session, what changed, what is next, what is blocked.
- Cost visibility
- Ranges with stated assumptions; changes flagged before they are spent.