Cross-functional prioritization page
Why is this change being made?
Tracking #13340 (closed) we are adding new handbook content around our Cross-functional Prioritization
methodology.
Pages added/modified and review apps
- Creates a new Cross-Functional Prioritization page detailing how DRIs should prioritize their respective work types (feature, maintenance, bugs) and how the PM should plan the milestone.
- Engineering page - replace Engineering Allocation section with responsibilities of EM and QEM, linking to the new page above.
- Development page - Adds to Cross-functional Collaboration section with information on EM work type prioritization and planning
Author Checklist
-
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.
-
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
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Wayne Haber