Q3FY2022 KR3: Expand technical writing weights experiment to 50% team member volunteers for one quarter
Issue Description
Part of the FY22-Q3 UX Department OKR: Balance tech writer workload by improving the planning and estimation process for feature docs
To help with capacity planning and to better ensure we're more proactive than reactive in how we focus on our work, we're experimenting with implementing a consistent planning/review process that includes a lightweight system of weights for issues and MRs. Hopefully this can help us ensure we're setting reasonable expectations for our stakeholders regarding our efforts, and allow us to focus on more proactive efforts.
Expand technical writing weights experiment to 50% team member volunteers for one quarter, incorporating weights into both issue planning and MR reporting.
-
2 - 3 volunteers participating from AMER/APAC (@cnorris) -
2 - 3 volunteers participating from EMEA (@dianalogan)
Information and instructions for volunteers (draft - in progress)
Beginning of the milestone
- Meet with your manager to review issues with documentation labels from your groups for the upcoming milestone. Make a best effort attempt to apply a tw-weight label to the issues.
- Add a links to this issue (or a separate tracking issue) for any searches, filters, or boards where the issues and weights are visible. You can also use a Google Doc to provide a summary view of the info (example from Product Design).
- Review and estimate non-feature issue work expected during the milestone. Add weights to issues/MRs if they exist, or capture the estimated weight in your separate planning issue or Google Doc.
- Note any events or items that may prevent feature/OKR/backlog work, including planned vacation, conferences, training. Capture in your issue, Google Doc, or share with your manager.
Throughout the milestone
- Apply
tw-weight
to any MRs you work on or review.
End of the milestone
- Meet with your manager to review the gathered data.
We'll do mini-reviews and sharing of insights at the end of each milestone, and a wider review at the end of the quarter.