Files
call-center/docs/uat

UAT Pilot Package

This folder contains the operational UAT package for Stage 4 pilot acceptance.

Scope Control

  • The frozen MVP pilot scope is defined in docs/gates/mvp-pilot-baseline.md.
  • Out-of-scope requests must be redirected to docs/roadmap/05-wave2-backlog.md.
  • During pilot close-out, only P1 and P2 defects are remediated in MVP.

Workflow

  1. Run preflight before participants join:
    • Existing environment: python scripts/uat_preflight.py --base-url http://<gateway-host>:8080
    • Local auto-start: python scripts/uat_preflight.py --auto-start
  2. Run automated dry-run and generate UAT package:
    • Existing environment: python scripts/uat_dry_run.py --base-url http://<gateway-host>:8080 --update-defect-register
    • Local auto-start: python scripts/uat_dry_run.py --auto-start --update-defect-register
  3. Create/adjust a session protocol from template (or from generated dry-run package):
    • docs/uat/session-template.md
    • Or prepare a full manual bundle:
      • python scripts/uat_manual_prepare.py --environment-url http://<pilot-gateway>:8080
  4. Execute all scenarios:
    • docs/uat/scenario-checklist.md
  5. Register all defects:
    • docs/uat/defect-log-template.csv
  6. Capture sign-off:
    • docs/uat/signoff-template.md
  7. Attach preflight report from:
    • docs/uat/evidence/
  8. After signatures and zero open P1/P2, close Gate 4:
    • Optional validation only:
      • python scripts/finalize_mvp_pilot.py --session-dir docs/uat/evidence/manual_<session-id> --dry-run
    • python scripts/finalize_mvp_pilot.py --session-dir docs/uat/evidence/manual_<session-id>

Triage Rules

  • P1: pilot acceptance is impossible
  • P2: key MVP user journey is broken
  • P3: acceptable with limitation, defer unless it blocks sign-off
  • P4: cosmetic or low-priority backlog item

P3 and P4 findings should be logged and moved to post-MVP backlog instead of stretching the MVP remediation cycle.

Mandatory Evidence Bundle

  • preflight report
  • completed session protocol
  • completed scenario checklist
  • filled defect log
  • signed sign-off sheet
  • updated docs/gates/p1-p2-defects.md

Exit Criteria

  • All mandatory scenarios executed
  • No open P1/P2 defects
  • Signed protocol by business and IT owners