Update how we work to include capacity planning and weight
Why is this change being made?
While trying to bring more visibility to the work our team does, the "how we work" also comes to mind. In FY24 Q4, we began milestone planning and in our efforts to continue milestone planning we must define our teams capacity. Post QE transformation into Test Platform our team has moved away from direct counterpart and become one unison team, Self-Managed Platform.
Our team handles various responsibilities (BAU, general housekeeping), while also working OKRs per quarter. Through capacity planning, we are hopeful to get a better sense of the teams current workload and how to best fit in issues/tasks of different weights that are of higher priority than other issues/tasks.
This MR will be iteration one of capacity planning as we continue to improve this process throughout each milestone and especially as our team members further knowledge share
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 -
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
-