Quality Gates

Two gates. No exceptions.

Every build passes through the PRD gate before sprint start and the Engineering & QA gate before handover. Both use the same scoring model: 0-5 per category, weighted total, hard minimums.

PRD Quality Gate

Owner: Omar (PI Studio ProductOps Lead)|Approver: Atoum (Director of Product Innovation)

Ensures every validated idea entering a sprint is build-ready, testable, and measurable. If a PRD fails, it goes back to the author with precise fixes.

Pass

80+ with no critical category below minimum

Conditional

70–79 - sprint starts, fixes due within 48 hours

Fail

Below 70 or missing any critical category minimum

Critical Minimums

CategoryMinimum
Problem & users3 / 5
Scope & requirements3 / 5
Acceptance criteria3 / 5
Dependencies & risks2 / 5
Success metrics & analytics2 / 5

What We Reject

  • No clear user or job-to-be-done
  • Vague scope - ‘make it better’ without specifics
  • No acceptance criteria - can’t test, can’t sign off
  • Missing dependencies - surprises mid-sprint
  • No success metrics - can’t judge if it worked

Workflow

1

Author submits Context + PRD in PI Studio.

2

Omar reviews and scores within 1 business day (same day for S sprints).

3

If FAIL: return with exact gaps + links to Golden PRD examples; resubmit required.

4

If CONDITIONAL PASS: sprint starts with a 48-hour fix deadline; changes tracked in PI Studio.

5

If PASS: sprint can start; PRD is version-locked unless a formal scope change is approved.

PRD Submission Checklist

  • 1Title + owner + subsidiary (EMX/NXN/FINTX/EDC) + target users
  • 2One-paragraph problem statement + objective
  • 3In scope / out of scope
  • 4Functional requirements list with flows and edge cases
  • 5NFRs (at least performance + security + localization if relevant)
  • 6Acceptance criteria per major feature
  • 7Dependencies/integrations + data required
  • 8Risks + assumptions
  • 9Success metrics + analytics events (even if rough)
  • 10UX references (mock, example, or notes)

Engineering & QA Gate

Owner: Emre (Technical Delivery Lead)|Approver: Atoum (Director of Product Innovation)

Ensures code and integrations are verifiable, reliable, and handover-ready. Reduces defect escapes, prevents regressions, and gives IT confidence at handover.

Pass

80+ with no critical category below minimum

Conditional

70–79 - ships with agreed fixes in 48 hours

Fail

Below 70 or missing any critical category minimum

Critical Minimums

CategoryMinimum
Functional correctness & acceptance criteria3 / 5
API contract & data validation3 / 5 (if applicable)
Security hygiene2 / 5
Test evidence & regression2 / 5
Operational readiness (logging/errors/config)2 / 5

What We Reject

  • Acceptance criteria not met with evidence
  • No smoke test or regression evidence
  • Secrets committed or silent failures
  • API contracts don’t match implementation
  • No task brief link or PR description

Workflow

1

Offshore delivers via PRs; Emre runs code reviews + QA validation.

2

Atoum integrates into the product experience; Emre verifies end-to-end flows.

3

Emre scores against the Engineering & QA rubric.

4

If FAIL or CONDITIONAL: specific fixes required before handover can proceed.

5

If PASS: Emre signs off engineering/QA readiness and supports IT packaging.

Merge Checklist

  • 1Task brief link (PI Studio/Jira) + acceptance criteria referenced
  • 2PR includes clear description + screenshots/logs (where applicable)
  • 3API endpoints documented and tested (Postman/Swagger/collection link)
  • 4No secrets committed; configuration via env/Key Vault
  • 5Error handling implemented (no silent failures)
  • 6Smoke test executed and evidence attached
  • 7Regression considered: impacted areas listed + checked