Group: Runner
The issue tracks the adoption of Next Prioritization Working Group for a specific group.
Each group will have an issue to tag the members of the quad for the group and track actions the group must take to adopt the new cross-functional prioritization process.
Handbook pages that document the new processes
- https://about.gitlab.com/handbook/product-development-flow/cross-functional-prioritization.html
- https://about.gitlab.com/handbook/product-development-flow/cross-functional-dashboard-reviews.html
- https://about.gitlab.com/handbook/engineering/development/#work-prioritization
Who
| Role | GitLab user id |
|---|---|
| Product Manager | @DarrenEastman |
| Engineering development manager(s) | @erushton @samdbeckham |
| UX stable counterpart | @rayana |
| Quality stable counterpart | @jo_shih (@zeffmorgan @alyubenkov for future milestones) |
Steps
Please check off these as they are verified/completed
ASAP
- Tag GitLab user names for the product manager, engineering development manager, UX stable counterpart, and quality stable counterpart for this group in the table above. iI you don't know who this is for a specific role, you may be able to find it on the stages handbook page. If there isn't an assignee for a specific role, please mark it as
N/A - Change name of issue to : "Group (group name)"
By June 17
- Confirm that a dashboard is available in the handbook showing the % of MRs that are bugs vs maintenance vs features. If you don't know where to find this, reference Create Next Prioritization team dashboards in r... (#13294 - closed)
- The dashboards have been reviewed at least once and a review cadence has been created to review and discuss the dashboard monthly with the quad Ref: Cross-Functional Dashboard Reviews
By June 30
- By June 30th at the latest, development engineering managers will provide their product manager counterpart a prioritized list of maintenance work.
- By June 30th at the latest, the group’s quality counterpart will provide product management with a prioritized list of bugs (that aren't yet auto-prioritized). If a group does not have a quality counterpart, the development engineering manager will (continue to) prioritize the bugs.
By July 14 at the latest
- The product manager will use these lists, along with a prioritized list of features, to schedule and assign work to the next milestone
Edited by Elliot Rushton