Source Code Planning 16.11
Release planning for the Source Code Group
Overview
Key Themes
Category | Theme |
---|---|
Team Capacity
- Total Weight Capacity: TODO
- FE Weight: TODO
- BE Weight: 46
Planning
- Planning Board - For the entire group
- UX Planning Board
- Planning Board - Backend
- Next 1-3 Milestones - Backend
- Planning Board - Frontend
- Next 1-3 Milestones - Frontend
Build Boards
Product manager prepares the planning with proposed issues for the milestone. Engineering reviews and make recommendations based engineering allocation and capacity.
Checklist
Frontend Engineering Manager
-
Get Team Capacities and post them in a comment no later than the 10th of the month -
Propose prioritized list of type::maintenance issues in a comment -
Obtain weights for proposed issues -
Collaborate with product manager to finalize the plan -
Assign Deliverable Items for Milestone -
Add an issue comment if a deliverable should be highlighted in the release post
Backend Engineering Manager
-
Get Team Capacities and post them in a comment no later than the 10th of the month -
Propose prioritized list of type::maintenance issues in a comment -
Obtain weights for proposed issues -
Collaborate with product manager to finalize the plan -
Assign Deliverable Items for Milestone -
Add an issue comment if a deliverable should be highlighted in the release post
Quality Engineer
-
Propose prioritized list of type::bug issues in a comment and request weights from engineering where still necessary
Product Manager
-
Define Key Themes -
Propose prioritized list of type::feature issues in a comment and request weights from engineering where still necessary -
Collaborate with counterparts in engineering to finalize the plan -
Add an issue comment if a deliverable should be highlighted in the release post -
Update the Direction page -
Sign off on final plan for the milestone -
Close the plannning issue
Stable counterparts
-
Technical Writing (@msedlakjakubowski) -
Quality (@jay_mccure)
Edited by Joe Woodward