How do we handle engineering-led issues that don't belong to one team?

The GitLab engineering team faces challenges in managing technical debt and cross-vertical issues due to its semi-siloed structure, where teams are focused on specific product areas without a clear point of responsibility for overarching tasks. This problem was highlighted in a recent discussion about prioritizing such issues, which lack a dedicated team after the dissolution of the former Platform team. Interviews with DevOps engineers reveal widespread frustration with reactive work and a lack of coordination between teams, which is exacerbated by the absence of a designated owner for technical debt-related tasks. A study of cross-functional teams suggests that creating a Portfolio Governance Team (PGT) with an end-to-end accountable leader could mitigate these issues. GitLab is considering establishing a dedicated team to handle cross-vertical tasks, though there is also a call for Product Managers and Engineering Managers to better align their priorities to address these challenges effectively.

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.