Skip to content

MR: Update Product Catalog Handbook Page

Brian Wong requested to merge brianmwong-main-patch-f263 into main

Why is this change being made?

We are making the following updates to the SKU issue template and need to update the handbook page accordingly:

  1. In the 1. Product Information section, simplified the intake questions by removing question 10, 13, and 14
    • Question 10: Will we allow customers to remove the SKU from their subscription mid-term?
    • Question 13: Will customers sign a SOW (Statement of Work) for this SKU?
    • Question 14: Will reps need the ability to specify a quantity for this SKU when quoting? (Example: X number of licenses, vs a flat fee for the service provided)
    • Justification: These questions were unnecessary/not adding value to the SKU process. We will always need to have the ability to remove SKUs from a subscription mid-term and the other questions are already specified in other parts of the issue template
    • cc @caroline.swanson @jrabbits
  2. In the 1. Product Information section, moved question 7 from the "General Overview/Business Requirements" to "Revenue Recognition Requirements".
    • Question 7: Do we need to create a separate SKU for each for those services?
    • Justification: Leaving this question up to the requestor did not make sense and is often a revenue accounting requirement if multiple instances are supported.
    • cc @msubramanian
  3. In the 1. Product Information section, removed Fang Wang from the "Taxation Requirements" as they are no longer with GitLab
  4. In the 1. Product Information section, added a "Data Requirements" section to assign Sushma N and Israel Weeks for input on the Product Tier, Delivery and Deployment Fields based on the definitions in the GitLab Handbook
  5. In the 4. Management Approval section, replaced David Sakamoto with Sherrod Patching for Customer Success approval
  6. In the 4. Management Approval section, updated James Harrison's approval to be a direct tag instead of using the sales support slack channel
  7. In the 5. Business Technology section, updated table to include the new Central Sandbox 2 Zuora environment<>Lightning Sandbox SFDC environment

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Division: If the update affects your division, share the MR in your division Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Update file product-catalog.md
Edited by Brian Wong

Merge request reports