docs(sdlc): audit storytelling for PM and SA only

sdlc/ISO29110-audit-prep.md

@@ -35,4 +35,4 @@
 | Open defects at acceptance | Test Report: TC-UN04.006, TC-UN08.002, TC-UN11.001, TC-UN12.001, TC-UN12.004 failed, TC-UN13.002–003 not tested; Correction Register ISS-029–032; Acceptance Report conditions; Minutes 24 Aug actions | "The run found four high-severity defects. We recorded them, told the sponsor, and acceptance was conditional on fixing them under corrective maintenance." Be ready to show the fix plan and its status. Do not claim they were fixed before 24 Aug |
 | UAT ran alongside the system test | Validation Results (test order row); Minutes of Meeting 10 Aug | "The entry criterion said UAT after 100% pass. The sponsor approved running both in 10–14 Aug at the 10 Aug meeting, and the deviation is recorded in Validation Results." |
 | Risks never re-rated | Software Project Plan R1–R8; risk table in every Progress Status Record | Pick 1–2 risks that actually occurred (R1 → Rack/Bin decision; R7 → evidence prepared before UAT) and show where they were handled. Do not change ratings in the records now |
-| Interviews must match the documents | One rehearsal session with the three people | Developer: a fixed defect (ISS-002 → commit `92d116f` → TC-UN04.002) and an open one (ISS-030 → TC-UN08.002, GL posting outside the document transaction). QA: run TC-UN04.002 and show the TC-UN08.002 failure. PM: trace CR13:001 → SR09:003 → UN08.002 → TC-UN08.002 → Failed → ISS-030 → acceptance condition |
+| Interviews must match the documents (only PM and SA attend) | One rehearsal with PM (ApS) and SA (NoC), using ISO29110-audit-storytelling.md | SA: a fixed defect (ISS-002 → commit `92d116f` → TC-UN04.002) and an open one (ISS-030 → TC-UN08.002, GL posting outside the document transaction), quoting the developer's and QA's records by name. PM: trace CR13:001 → TC-UN08.002 → Failed → ISS-030 → acceptance condition. Questions on work done by others: answer from the record or say you will check with the owner |