Code Review Product Design 15.5 Planning

Work planning for the Product Designers in the Code Review Group, including work outside the stage group's deliverables, like Pajamas contributions or UX OKRs. See Product Designer's priorities.

🗺 Product Design milestone board

Also see the Code Review release board for work specific to the stage group, especially the UX, UX research, and UI text lists.

Work outside board

Optional: Use this table for work that's not in the milestone board (e.g. OKRs, epics)

Name/link	Designer	Notes	Weight
FY23-Q3 Create:Code Review OKR: Create 5 “plann... (#13031 - closed)	Annabel and Pedro

❗ Top priorities

List the top one or two priorities for each designer

Name/link	Designer	Notes
Internal concept testing for Comments tab and m... (ux-research#1848 - closed)	Annabel and Pedro

⚖ Weights

Estimated weights

Business days in milestone: 19

	Annabel	Pedro
Average*	7	6
Planned days off	1	11
Working days	18	8
Estimated**	7	3

*: Average of weights done in the last 3 milestones
Normalize weights for each milestone: (<Done weight>/<Working days>) × <Business days in milestone>
Average: <Sum of normalized weights> ÷ 3

**: (<Average> ÷ <Business days in milestone>) × <Working days>

	Annabel (planned)	Annabel (unplanned)	Annabel (done)	Pedro (planned)	Pedro (unplanned)	Pedro (done)
For Code Review	7 (88%)	0	5	6 (86%)	0	6
For other priorities	1 (12%)	0	0	1 (10%)	0	0
Total	8	0	5 (63%)	7	0	6 (86%)

At milestone start

Screenshot of issue board/list at milestone start

Annabel	Pedro

At milestone end

• Annabel's closed issues
• Pedro's closed issues

Checklist

• Before the 18th (milestone start):
  • Refine the issues already in this milestone for correct label hygiene.
  • Check/update past milestones for wayward issues.
  • Add items to “work outside board” table if applicable.
  • Assign FE and BE Deliverable issues that will require design support.
  • Weight work.
    • See guidance. Use ~design-weight::X label if issue is shared with counterparts.
  • Reach out to engineers to clarify assigned issues, if needed.
• On the 18th (milestone start): Add screenshot(s) of milestone board.
• On/after M+1 17th (milestone end): Review planned vs done.