Skip to content

Draft: Update file scale-operating-rhythm.md

Klara Audren requested to merge WIP into main

Why is this change being made?

Using the previous document CSE: Qualifications/Scope Document for CSE Engagement I have tidied up and/or included within the handbook

  • How to create a CSE request (updated)
  • Who can create CSE Requests (updated)
  • What qualifies and what does not qualify as a CSE request (new)
  • How to engage CSE's when a client requires multiple CSE cases (new)

The reason why I have added the new paragraph on what constitute a CSE request is because there appears to be a lack of guidelines currently within the handbook as to what is a CSE request and what isnt, which can lead to some confusion from account owners.

I have also combined both the 'CSE Engagement Request Process' and the 'Requesting CSE Engagement (Account Owners only - AEs, SAEs)' as these paragraph were essentially repeating themselves.

With those changes the handbook now clearly defines who's responsible for creating and managing cases

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
    • 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
Edited by Klara Audren

Merge request reports