GitLab Next

I've asked Cynthia to run a retrospective in my absence with those who had MRs due on May 31st for our Docs OKR initiative.

I look forward to the results! (also retros for support are "new" and not "normalized" so a google doc with comments from a discussion or even comments on this issue are enough for me but if we do something more formal I'm open to it.

Purpose

Get feedback from all team members involved in the joint Support-Docs OKR.

Instructions

I'd like to run this async since we have a lot of timezones involved. However, if anyone wants to do a sync chat, please let me know and I'll set one or two up.

Each question is a separate comment

1. Please answer each question in the appropriate thread (if at all possible).
2. For anything not covered, please start a new thread with a heading using the below format.
3. Once complete, feel free to remove yourself from the list of assignees.
4. If you can, add highlights to the summary sections below.

## Topic not covered

comment

Summary

Keep doing

1. Template that outlines work and is easy to follow: #2403 (comment 356135556)
2. Connect Support IC to TW IC #2403 (comment 357221122)
3. Encouraging messages and reminders (though also see improvements section)
   • Slack messages can easily get lost. Reminder on issues themselves #2403 (comment 368387292)
   • Multi-modal communication. Most effective were on the issues #2403 (comment 381915610)

Improvements or Actionables

1. For any existing issues, ensure assignee is pinged and notified of addition to epic and due date with copy of template to outline expectations. #2403 (comment 355796364) & #2403 (comment 373452332)
2. Ways to set reminders for those who want it? Currently the GitLab issue sends a due date reminder 2 days prior, but that's it. #2403 (comment 356135556)
3. And/or to above point, buddy/peer reviewer: #2403 (comment 362326448) ; or sessions #2403 (comment 372689303)
4. Clearer expectations and outcomes. Tickets can be a "rabbit hole"
   • #2403 (comment 362326448)
   • #2403 (comment 357675346)
5. Clearer who is tracking, what, where #2403 (comment 369285132) plus a lot of Slack messages ; that is: have a clear process and timeline outlined such as who gets assigned, setting the MR to close the issue, etc. #2403 (comment 373452332)
6. Tracking "completion" at 1 MR, but in cases can become very large. How do we keep to our small MR/iteration value? #2403 (comment 357513504)