GitLab Next

Currently, we have async retrospectives once per month, aligned with the milestone cut-off. With a change in process, we will be less reliant on the milestone cycle, and we could retrospect at any point. However, since we are already introducing change in our process, I want to start and be more critical about introducing more change just for the sake of it.

From my perspective, the two things that seem the most difficult about our current retrospective process are:

1. A month is a long time to remember things
2. We take two weeks to complete a retrospective

And these aspects work really well:

1. Async nature means that there is time to think about the comments that people make
2. Serves as a monthly record of what we accomplished and what we thought about that

I would like to hear people's thoughts about our retrospectives. (I guess that means we are retrospecting on our retrospectives 🙂) Should we keep the current format? Is there anything that seems broken or ineffective about the current process? Are there any changes we should make?

/cc @geo-team