QA & Compliance Training Guide (Tinggit Platform)¶

Audience: QA, Security, Compliance
Purpose: Explain how quality, validation, and auditability are enforced using Redmine

• Table of contents
• QA & Compliance Training Guide (Tinggit Platform)
  • 1. Your Role in the Process
  • 2. QA During the Sprint
  • 3. Definition of Done Enforcement
  • 4. Sprint Close Validation
  • 5. Release Validation
  • 6. Audit Execution
  • 7. Compliance & Exceptions
  • 8. Common QA & Compliance Pitfalls
  • 9. Final Reminder

---

1. Your Role in the Process¶

QA & Compliance owns:

• Definition of Done validation
• Test verification
• Audit readiness
• Release validation

You do NOT:

• Redefine scope
• Change sprint commitments
• Adjust metrics

---

2. QA During the Sprint¶

QA activities include:

• Validating Acceptance Criteria
• Executing test cases
• Logging defects early

Sprint bugs:

• Must be fixed within the sprint
• Block story completion

---

3. Definition of Done Enforcement¶

A story is DONE only if:

• All tests pass
• No open sprint bugs
• Acceptance Criteria met
• Evidence is available

Stories failing DoD must not be accepted.

---

4. Sprint Close Validation¶

Before sprint close, QA must verify:

• Completed In Sprint is correctly set
• Spillover items are justified
• No hidden unfinished work exists

QA acts as a quality gate, not a bottleneck.

Authoritative reference: Sprint Close Process

---

5. Release Validation¶

Before a release is closed:

• Verify all release issues are Done
• Confirm QA sign-off
• Ensure release notes are accurate
• Validate deployment references exist

Authoritative reference: Release Management Process

---

6. Audit Execution¶

Audits rely on:

• Saved queries
• Sprint history fields
• Issue history
• Wiki documentation

Audits must be reproducible without explanation.

Authoritative reference: Sprint History, Metrics & Audit

---

7. Compliance & Exceptions¶

For compliance-driven urgency:

• Ensure traceability
• Ensure documentation
• Preserve history

Emergency never means undocumented.

Authoritative reference: Edge Case & Exception Handling

---

8. Common QA & Compliance Pitfalls¶

• Allowing “almost done” stories
• Skipping documentation
• Approving releases under pressure
• Fixing data instead of process

---

9. Final Reminder¶

bq. Quality is enforced by discipline, not heroics.

If data cannot be audited later, it is not done.