Dataset entry

Verification & Acceptance: Prove the Change Worked (or Don’t Close It)

ams ams_byte ams-038
Most SAP AMS work fails quietly at the end: changes are ‘done’, but nobody can prove the business is safer or faster.

Attribution

Creator: Dzmitryi Kharlanau (SAP Lead).

Canonical: https://dkharlanau.github.io/datasets/ams/ams-038.json

LinkedIn

JSON (copy / reuse)
{
  "id": "ams-038",
  "title": "Verification & Acceptance: Prove the Change Worked (or Don’t Close It)",
  "hook": "Most SAP AMS work fails quietly at the end: changes are ‘done’, but nobody can prove the business is safer or faster.",
  "idea": "Modern AMS treats verification as a first-class activity. Work is not accepted because it was deployed — it’s accepted because evidence shows the intended outcome actually happened.",
  "sap_acceptance_failures": {
    "what_goes_wrong": [
      "Technical deployment without business verification",
      "Testing done in isolation from real flows",
      "Acceptance based on silence instead of signals",
      "Issues reappearing weeks later as ‘new’ incidents"
    ]
  },
  "verification_layers": {
    "technical": [
      "No new errors or dumps for affected objects",
      "Jobs/interfaces complete within expected time",
      "No rollback signals triggered"
    ],
    "functional": [
      "End-to-end flow succeeds with real data",
      "Known edge cases behave as expected",
      "No regression in related scenarios"
    ],
    "business": [
      "Process owner confirms impact is resolved",
      "KPIs or SLO signals return to green",
      "No new workarounds introduced"
    ]
  },
  "acceptance_rules": [
    "No evidence → no acceptance.",
    "Silence is not acceptance; signals are.",
    "If verification fails, reopen as Problem or Change — not a new ticket.",
    "Acceptance must be time-bound (verify again after N days if risk exists)."
  ],
  "verification_artifacts": {
    "required": [
      "What was verified (scope)",
      "How it was verified (steps or signals)",
      "When verification occurred",
      "Who confirmed it"
    ],
    "nice_to_have": [
      "Before/after comparison",
      "Negative test confirmation",
      "Monitoring screenshot or metric snapshot"
    ]
  },
  "coordination": {
    "who_accepts": [
      "Change Owner (delivery correctness)",
      "Flow Owner (business outcome)",
      "Security/SoD (if access or roles changed)"
    ],
    "handover_after_acceptance": [
      "KB/runbook updated",
      "Monitoring adjusted if needed",
      "Debt register updated (if partial fix)"
    ]
  },
  "automation": {
    "copilot_moves": [
      "Generate a verification checklist based on change type and blast radius.",
      "Pull relevant signals automatically for acceptance evidence.",
      "Detect silent regressions post-acceptance.",
      "Block closure if mandatory evidence is missing."
    ],
    "outputs": [
      "Acceptance-ready evidence pack",
      "Post-change verification report",
      "Regression watchlist"
    ]
  },
  "why_this_reduces_long_term_cost": [
    "Fewer ‘zombie fixes’ that come back later.",
    "Clear accountability for outcomes, not activity.",
    "Higher trust between AMS, business, and vendors."
  ],
  "anti_patterns_to_kill": [
    "Closing work on deployment day",
    "‘No news is good news’ acceptance",
    "Verification done only by the implementer"
  ],
  "metrics_that_keep_it_honest": [
    "Changes accepted with full evidence (%)",
    "Post-acceptance incident rate (30/60 days)",
    "Verification lead time",
    "Reopen rate due to failed acceptance"
  ],
  "design_question": [
    "If this change breaks again next month, can we prove it ever worked?"
  ],
  "meta": {
    "schema": "dkharlanau.dataset.byte",
    "schema_version": "1.1",
    "dataset": "ams",
    "source_project": "cv-ai",
    "source_path": "ams/ams-038.json",
    "generated_at_utc": "2026-02-03T14:33:32+00:00",
    "creator": {
      "name": "Dzmitryi Kharlanau",
      "role": "SAP Lead",
      "website": "https://dkharlanau.github.io",
      "linkedin": "https://www.linkedin.com/in/dkharlanau"
    },
    "attribution": {
      "attribution_required": true,
      "preferred_citation": "Dzmitryi Kharlanau (SAP Lead). Dataset bytes: https://dkharlanau.github.io"
    },
    "license": {
      "name": "",
      "spdx": "",
      "url": ""
    },
    "links": {
      "website": "https://dkharlanau.github.io",
      "linkedin": "https://www.linkedin.com/in/dkharlanau"
    },
    "contact": {
      "preferred": "linkedin",
      "linkedin": "https://www.linkedin.com/in/dkharlanau"
    },
    "canonical_url": "https://dkharlanau.github.io/datasets/ams/ams-038.json",
    "created_at_utc": "2026-02-03T14:33:32+00:00",
    "updated_at_utc": "2026-02-03T15:29:02+00:00",
    "provenance": {
      "source_type": "chat_export_extraction",
      "note": "Extracted and curated by Dzmitryi Kharlanau; enriched for attribution and crawler indexing."
    },
    "entity_type": "ams_byte",
    "entity_subtype": "",
    "summary": "Most SAP AMS work fails quietly at the end: changes are ‘done’, but nobody can prove the business is safer or faster."
  }
}