Business & Technical Alignment

Extract how the service really works — rules, exceptions, dependencies — through scoping workshops, then document it and validate design and content feasibility before any implementation begins.

Gate to advance

BRD reviewed and approved by both MTCIT and SP; UI template coverage and content compliance confirmed.

Output produced

Approved Business Requirements Document, validated design/content feasibility, and a shared understanding of integration expectations.

Full checklist

Business & Technical Alignment (7)
Business & Technical Alignment
Task Owner
Conduct GUP technical onboarding session

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om) & SP
Establish OGN connectivity between GUP test and staging environments and SP non-production environment(s)

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om) & SP
Provide details on services' flow and statuses

Accountable: SP

Responsible: SP
Prepare GUP Event Processing test cases

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om)
Prepare business-specific test cases including positive, negative and edge cases

Accountable: SP

Responsible: SP
Prepare BRD (covering configuration on GUP side and implementation requirements on SP side)

Accountable: MTCIT (Gov.om)

Responsible: MTCIT (Gov.om)
Review and approve BRD

Accountable: SP

Responsible: SP