Retrospective: 11.5 Retrospective
(It's turtles all the way down.)
So just like last time (#3254 (closed)), I'd like to take some time to discuss what went well with the 11.5 retrospective and how we think we can improve. I don't have as definite a list of suggestions this time, but here are the thoughts I left the call with:
- The agenda felt a bit lighter, and a lot got populated close towards the retrospective date. There were holidays and we're in the middle of experience factor review and I appreciate there is a lot going on, but I'm wondering if an issue like #3016 (closed) helped us stay on track better for 11.4. If so, maybe I should make that a standard part of the process.
- Similarly, we still had some duplication between teams (probably because there wasn't a lot of time to compare notes), in spite of agreeing to try to weed that out. Should we add an explicit step (say, on the 22nd) to go through and edit the document?
- The timing felt really rushed and I had to cut us off at the end of the "What went well" and "What went wrong" sections, but it turned out we very much needed all 18 minutes for the discussion section so I feel like we should preserve the timing moving forward. How can we set better expectations with folks early in those sections that they need to move quickly? I also don't want people to feel like they can "hide" at the bottom of the agenda, so to speak, or like they're likely to get missed in the call because they happened to be one of the last people to add to the list.
Any other thoughts?
/cc @gitlab-com/backend-managers @sarrahvesselov @timzallmann @meks