Document New SKU UAT Process

Problem

When new SKU changes are introduced, Fulfillment coordinates with several teams across Deal Desk, Billing, Revenue, Data, etc. to help test changes through User Acceptance Testing (UAT)

As a new member of the groupprovision team, it was challenging to find comprehensive information around how new SKU UAT is conducted here at GitLab and the role of Fulfillment engineers in this process since it is mainly tribal knowledge. While working on https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/12462+, I needed to consult with several different team members to gather this information and form an understanding of the bigger picture.

Proposal

• Create documentation in the CustomersDot developer docs that helps outline the new SKU UAT process
  • Overview of the UAT process
  • Why we perform UAT
  • Cross-functional teams involved
  • Testing scope
  • Roles and responsibilities of Fulfillment in this process
  • Overview of how test data is created and accessed, and the data flow between teams
  • Test environments involved
  • etc.
• Update the Fulfillment engineering onboarding template with a link to this new documentation

Result

Documentation available that helps provide a single source of truth for new SKU UAT