Remote Agile at GitLab

GitLab operates a unique workflow characterized by monthly releases on the 22nd, featuring major changes and improvements based on community and customer feedback. The company embraces a completely remote and self-organizing structure, where developers work independently without predefined teams or strict adherence to agile methodologies, yet align with agile principles. Issues are created when requests come in, and consensus is reached through open discussions involving relevant parties. Scheduling is flexible, often challenged by capacity issues, and prioritization is guided by a general set of criteria, with particular attention to promised features. Overflow of issues is managed by re-evaluating their relevance and reassigning them as necessary. Developers are empowered to choose their tasks, which fosters openness, independence, and responsibility in decision-making, with updates communicated asynchronously. The workflow emphasizes speed and flexibility over rigid processes, maintaining an open environment that encourages equal contribution from the community and customers, though concerns about scalability persist as the company grows rapidly.

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.