At the conclusion of each project, we will conduct a root cause analysis using the template below. The purpose of these is to identify areas for improvement, as well as wins to make sure to highlight. The team generally works on independent projects and with diverse customer groups, so mutual learning is important to how the Professional Services Engineering team lives up to the GitLab values of Collaboration and Iteration.
Root Cause Analysislabel is applied to the issue
Each root causes analysis meeting should follow (roughly) this agenda here.
All follow-up action items will be assigned to a team/individual before the end of the meeting. If the item is not going to be a top priority leaving the meeting, don't make it a follow up item.