Knowledge Group 13.3 Planning (Aug 22) ★★★★★
Release planning for the Knowledge Group
Kickoff video: https://youtu.be/PqhohXe1gMw
Main board, all issues
Boards with team and/or feature filters
Expand for Workflow Board links
Product specific filtered boards: Priority of development is set in workflow::ready for development, FIFO
- 13.3 Board: Product Workflow :: Direction
- 13.3 Board: Product Workflow :: Design Management
- 13.3 Board: Product Workflow :: Wiki
- 13.3 Issue List :: Direction
Engineering team capacity boards If multiple teams, Weight is total. Ex: 2 = frontend-weight1 + backend-weight1
Product links
- 13.3 Shared Calendar Product Development Dates
- 13.3 Release Issue TBD
- GitLab 13.3 Kickoff - Create:Knowledge - YouTube TBD
Team specific notes and capacity
UX
- Use the product workflow board above
- Items assigned to @mnearants and @katokpara will be listed here in the workflowdesign and workflowsolution validation columns. We are still figuring out how to report specifically on the ones we work on ahead here.
- Rolling Board - workflow::design by Milestone
Frontend (Capacity: 13)
Frontend 13.3: Deliverable / Stretch Board
Please see the FE Board for this release
Backend (Capacity: 15)
Backend 13.3: Deliverable / Stretch Board
Please see the BE Board for this release
--
Product process checklist
Notes to self, and to help me document my process for new PM's as they join. I typically work through these boards and issues, in the order listed below grooming the issues.
Boards
- Create groups for milestone - make sure every issue in the milestone has the correct group assigned
- knowledge Deliverables / Stretch / NPR for milestone - quick view of what is/isn't deliverable, pretty much everything non-deliverable should be removed from the milestone by kick off to prevent confusion that it will be implemented
- knowledge BE / FE / Discovery for milestone - make sure very issue has either BE, or FE, or both assigned
- Create groups for HackerOne - make sure every HackerOne security issues has the correct group assigned
- Bugs
Lists
- Security issues sorted by due date - make sure all security issues with an upcoming due date are assigned to meet our security SLA
- Bugs
Checklist
-
Groom the issues already assigned to the current milestone for correct label hygiene -
Check/update past milestones for wayward issues -
Check/update relevant category visions (Design Management, Wiki) -
Write release post draft for each Direction item -
Add direction items -
Add security items -
Add bugs -
Carefully check ~promised items for customers are scheduled or well communicated
Edited by Christen Dybenko