Skip to content

Operations

How the fictional Northwind Driver App is run day to day.

Environments

Environment Purpose Notes
DEV Development Throwaway data; reset often.
SIT System integration testing Interfaces and data integrity confirmed.
UAT User acceptance testing Business users sign off fitness for purpose.
PROD Production / live service Real drivers and real deliveries.

Release stages

Releases move through a fixed set of gates. Each gate must pass before the build moves on.

  1. Build — compile and run unit tests.
  2. Integration test — verify the app against staged back-end services.
  3. Security test — penetration test remediated and re-tested before release.
  4. User acceptance — business users confirm the build is fit for purpose.
  5. Pilot — a small group of drivers runs the build in the field.
  6. Release — the build is promoted to production.

Defect policy

Priority 1 and Priority 2 defects are not accepted into the next stage or into production.

Incident management

Incidents are triaged by priority and tracked to resolution against a target response time.

Priority Definition
P1 Core operations stopped, or a data/privacy breach.
P2 A significant issue with data impacting daily operations.
P3 Medium impact; a workaround is available.
P4 Low or cosmetic impact.