How we use GitLab to automate our monthly retrospectives

An Engineering Manager at GitLab describes their innovative use of GitLab for conducting asynchronous retrospectives with their widely distributed team, using GitLab issues to facilitate participation across various time zones. To streamline the process, they automated retrospective issue creation through the async-retrospectives project, employing scheduled pipelines to create and update issues each month, thus allowing team members to contribute thoughts while still working on releases. This approach overcomes time zone challenges and enables easy reference to specific issues through linkable comments, although it lacks the fluidity of verbal discussions and slows team bonding, which are better facilitated by video calls. Despite these drawbacks, the asynchronous retrospectives have been positively received, eliminating time zone disadvantages and allowing for broader adoption across other teams, and the company remains committed to this practice while exploring further improvements.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.