Document Inner-Org borrows
Why is this change being made?
Our current borrow request process and template is quite involved and requires approvals at all levels. The process is very well documented and many of the steps and approvals have been documented for valid reasons in the past, but this process is not always followed because it is quite involved for organizations who work closely together and are already familiar with the process.
This change seeks to document the case where engineering, product, and UX leadership are able to align quickly on the need for a borrow and the identified impact because they are already working so closely together. As an example, this issue was orchestrated over Slack by asking the PM/EM from 1 group in a stage if they could have support from the PM/EM in another group from the same stage.
This change DOES NOT address the need for accurate tracking and reporting. In order to make sure we are appropriately documenting that the request occurred and what the impact was, I am also requesting modifications to the borrow request templates:
- Update borrow request template (gitlab-com/Product!894)
- Update realignment template to match borrow tem... (gitlab-com/Product!895 - merged)
CHANGEME
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
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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 - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- Document Inner-Org borrows