@@ -52,13 +52,13 @@ Our backlog should be prioritized on an ongoing basis. Prioritization will be do
1. Engineering Manager in development provides prioritized `type::maintenance` issues
1.[Test Platform Managers](/handbook/engineering/infrastructure/test-platform/#milestone-planning) provide prioritized `type::bug` issues using the [bug prioritization dashboard](https://10az.online.tableau.com/t/gitlab/views/OpenBugAgeOBA/BugPrioritizationDashboard)
*Note: UX-related work items would be prioritized in accordance with the appropriate sub-types. UX related bugs are included in the automated process (S1/2 and so on), UX-related maintenance items will be included in the EM's prioritized list, Product (feature) UX items will have been included as part of our normal [Product Development Flow](/handbook/product-development/product-development-flow/).*
*Note: UX-related work items would be prioritized in accordance with the appropriate sub-types. UX related bugs are included in the automated process (S1/2 and so on), UX-related maintenance items will be included in the EM's prioritized list, Product (feature) UX items will have been included as part of our normal [Product Development Flow](/handbook/product-development/how-we-work/product-development-flow/).*
The DRIs of these three core areas will work collaboratively to ensure the overall prioritization of the backlog is in alignment with [section direction](https://about.gitlab.com/direction/#devops-stages) or any other necessary product and business needs. If a team is not assigned a Product Designer then there is no UX counterpart needed for prioritization purposes. PMs will prioritize the final plan for a given milestone.
#### Milestone planning and prioritization
Quads should follow the standard milestone planning process as described in our [Product Development Flow](/handbook/product-development/product-development-flow/#build-track). PMs will keep the overall prioritized backlog following the agreed-upon ratios and guidance from their EM, Quality and UX counterparts.
Quads should follow the standard milestone planning process as described in our [Product Development Flow](/handbook/product-development/how-we-work/product-development-flow/#build-track). PMs will keep the overall prioritized backlog following the agreed-upon ratios and guidance from their EM, Quality and UX counterparts.
* Requests expert help from others recognizing that diverse opinions/experience improve the quality of their solution.
* Collaborates and consults with stable counterparts including understanding their roles and responsibilities and focusing on fostering productive working relationships.
* Shows that they are aware of differing priorities between groups.
* Prioritizes work by following [GitLab Priority and Severity label](/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority) guidelines, focusing on high-value activities, completing tasks with the earliest deadlines, and when in doubt, seek clarification regarding the priorities.
* Prioritizes work by following [GitLab Priority and Severity label](/handbook/product-development/how-we-work/issue-triage/#priority) guidelines, focusing on high-value activities, completing tasks with the earliest deadlines, and when in doubt, seek clarification regarding the priorities.
* Balances short term gains and long term benefit with team's help. For example, advocating for technical debt resolution and understanding the opportunity cost in comparison to a quick customer win.
* Creates proposals for their team that clearly defines the problem, offers alternatives, and proposes a solution. These proposals are small in scope, looking to address problems with a small surface area.
* Incorporates [Iteration](/handbook/values/#iteration) in every aspect of your job (examples: development, issue creation, planning, process improvements)
When an issue comes through that is both ~"severity::1" and ~"priority::1", our
[SLO](/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity-slos) requires that it be looked at right away. Other items being worked on should
[SLO](/handbook/product-development/how-we-work/issue-triage/#severity-slos) requires that it be looked at right away. Other items being worked on should
be postponed in favor of any investigations or work for the high
severity/priority issue. When postponing an issue, engineers should leave a comment on the issue with a link to the high severity item that is being prioritized instead. Leaving a comment will help with communication with the cross-functional team and for historical tracking. The exception to this is if another
~"severity::1"/~"priority::1" issue is currently being worked on by an engineer.
Any of the items with a "*" are considered issues driven by the attached [SLO or SLA](/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity) and are expected to be delivered within our stated policy. There are two items that fall into Forced Prioritization:
Any of the items with a "*" are considered issues driven by the attached [SLO or SLA](/handbook/product-development/how-we-work/issue-triage/#severity) and are expected to be delivered within our stated policy. There are two items that fall into Forced Prioritization:
1. Security Issues labeled with `bug::vulnerability` must be delivered according to the stated [SLO](/handbook/security/engaging-with-security/#severity-and-priority-labels-on-security-issues)
1. Issues supporting our product's scale which include `bug::availability` with [specific SLOs](/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#availability) as well as `infradev`, `Corrective Action`, `ci-decomposition::phase*` that follow the stated [`type::bug` SLO](/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity-slos)
1. Issues supporting our product's scale which include `bug::availability` with [specific SLOs](/handbook/product-development/how-we-work/issue-triage/#availability) as well as `infradev`, `Corrective Action`, `ci-decomposition::phase*` that follow the stated [`type::bug` SLO](/handbook/product-development/how-we-work/issue-triage/#severity-slos)
Any issues outside of these labels are to be prioritized using [cross-functional prioritization](/handbook/product/product-processes/cross-functional-prioritization/). Auto-scheduling issues based on automation or triage policies are not forced prioritization. These issues can be renegotiated for milestone delivery and reassigned by the DRI.
